3 ms·
As a full-time Node.js dev, I agree with your decision! Too much time is wasted on compatibility problems. I'd almost say it was easier when we just had browser
by mattwad 3y ago
As a full-time Node.js dev, I agree with your decision! Too much time is wasted on compatibility problems. I'd almost say it was easier when we just had browsers to deal with. At least you could just drop in jQuery and call it a day.
- ralmidani 3y agoYes, jQuery is often derided as outdated, but it worked quite well for a very long time, with minimal hassle for developers. In fact, I was working full-time on static Elixir/Phoenix pages with jQuery sprinkled on top as late as 2022… it felt a bit clunky but it worked as advertised and wasn’t frustrating in any significant way.
- kbrannigan 3y agoI still use JQuery because of all the syntactic sugar and shortcuts.
- firecall 3y agoMe too, I prefer the API. At the end of the day I’m delivering reliable and productive solutions for my clients, and they don’t care what the tech is. However the Django API, GraphQL with React front end stack I’ve inherited is an frustratingly flakey to use and a nightmare to develop :-/ It’s so bad I’m regretting all my life choices that led me to this point LOL
- mikecaulley 3y agoI’m curious to hear what are some of the most frustrating points developing with Django, React, and GraphQL.
- patrick91 3y agosame here, maybe we can improve things!
- OhHiMarkos 3y agoI mean, a whole sea of WordPress developers still use JQuery. It's still out there and thriving.