3 ms·
> Don't just go with inertia. Well. Inertia is powerful: A new project I start in jQuery today? Next to 100% chance I can pick up a dev who has seen jQuery, ev
by mschuster91 9y ago
> Don't just go with inertia.
Well. Inertia is powerful: A new project I start in jQuery today? Next to 100% chance I can pick up a dev who has seen jQuery, even in three or four years. Worldwide.
A new project I start in AngularJS or whatever is the current fad? Good luck if the framework hasn't done yet another BC break or hasn't vanished into oblivion by then.
- jrs95 9y agoAt this point, I think React seems popular and stable enough that there's not much of a point in going with jQuery for the sake of stability/popularity. And there's still a huge pool of people with AngularJS 1.x experience, too. What's more important, in my opinion, is what tools are going to be easiest for you and/or your current team to get stuff done.
- payne92 9y agoOP's note and my comment are about considering the option of no framework. Instead of choosing JQuery (on inertia) or the current fad, consider just using current base language features and best practices. It might be a better choice. As a bonus, to your point, you're then far less worried about finding future devs with your library/framework-specific experience.
- jbergens 9y agoI've seen jquery code that looked like spaghetti, it was very hard to read or change even if you knew jquery. This is the problem that most libraries and frameworks tries to fix. I think react has succeeded.