this post was submitted on 11 Dec 2023
72 points (97.4% liked)
Programming
17484 readers
175 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 [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
No, because the current practices have shifted from writing html+css+js in the classic style to using JavaScript frontend frameworks like vue, react, angular, svelte... Which offer a lot of features that would jQyery give you but also removed the need for some of them.
The paradigm has shifted and I don't think jQuery is used anymore (atleast not for new projects).
To explain this a bit further, the main difference between older jQuery-based projects and newer (React|Vue|Angular|Svelte)-based projects is imperative vs. declarative programming.
It used to be that you give commands (e.g. "when the user clicks this button, change that label content and add CSS classes to these elements"). Very quick to add something small, but also hard to grow and maintain well. It's easy to forget a command in some code paths.
Nowadays you declare state, and define how your UI is derived from that. This means you don't give commands to change things, instead you change data and your UI is updated automatically. This makes it much easier to understand a component, and allows for maintainable growth.