this post was submitted on 03 May 2025
10 points (91.7% liked)
Programming
19957 readers
207 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
MDN is great, especially for finding current best practice, but I've always found their material much more useful for reference once I'm already familiar with the general usage of whatever I'm trying to use. I often find it difficult to get to grips with something new just with MDN.
I usually go read W3Schools first. It's mostly a bit out of date, but not so much that it's useless, and I find the tutorials much easier to digest. Once I'm comfortable with the basics, I switch to MDN to get up to speed.
And OP, it sounds like you're already wary of this, but don't let yourself be tricked into using a hodge-podge of libraries for every little thing. A lot of JS programmers will tell you that you "need" some library or other to provide a function that you can often replicate with just two or three lines of raw JS, if you know what you're doing.
I think the JS library addiction stems from the bad old days of browser incompatibility, when almost everything had to be wrapped in layers of complex compatibility shims.