4 ms·
Very, very few places will let you not use a framework nowadays. There is a ton of cargo culting around JS frameworks and coding vanilla is pretty much heresy l
by abraxas 4y ago
Very, very few places will let you not use a framework nowadays. There is a ton of cargo culting around JS frameworks and coding vanilla is pretty much heresy land these days. Personal projects? Go for it. Commercial apps built for your employer? Good luck with that. Not only will you be raked over the coals for "reinventing the wheel" you'll also be blamed for any stumble along the way, whether it's related to using vanilla or not.
> if you want some war stories from your granddad, have you heard of jQuery ? :D
Bah, whippernsapper! I cut my baby web teeth on CGI and spent the bulk of it in Struts and JSF. Remember THOSE?
- tomcam 4y agoNo I don’t. I was too busy programming ENIAC using patch cables. Grace Hopper once made a snide remark about it after lunch. She smelled like corned beef hash.
- xwolfi 4y agoI was "born" after Struts was "obsolete" (so I had my honeymoon phase with Spring/Hibernate until I fixed so many mistakes in companies I decided using smaller surface tools and closer to the metal queries would actually save time) and never touched JSF :D CGI for me is prehistory loool. However, employers dont need to be involved in choosing a framework or not. You ll notice that usually its the little bees building their resumes that bemoan non stop about migrating from react to vue or vue to react :D I never heard a sales guy tell me: WHAT, it works fine, is cheap to maintain and has no stupid 10k levels dependency graph in npm ? I ll stop making money on this until you completely "standardize" it into a moving sand on npm. And dont forget a pipeline of 3 transpilers, you wouldnt want to write in a browser-native language, caveman. I do use requireJS to split in nice files and import easily though I admit.