4 ms·
If it's so bad, you're welcome to write your applications in vanilla JavaScript, with no shims, in flat files without modules calling 1998 era DOM APIs. There'
by zero_shift 4y ago
If it's so bad, you're welcome to write your applications in vanilla JavaScript, with no shims, in flat files without modules calling 1998 era DOM APIs.
There's a reason most people don't, however.
- throwaway892238 4y agodeveloper see javascript think "looks frozen yogurt came out wrong end, but can do job". end up building castle of wrong end frozen yogurt. some say better than no castle. grug say why building with no-no soft serve in first place. (grug know answer: more shiny rock)
- zero_shift 4y agoPlease stop the grugposting, it is impossible to read.
- throwaway892238 4y agoyou in thread for grug story! no like, no read!
- zero_shift 4y agoMade me smile, have my upvote
- beckingz 4y agoalways be grugposting
- pelagicAustral 4y agoAverage js zealot.
- recursive 4y agoVanilla js has modules though. You don't need a build step to use modern APIs.
- throwaway9d6ef 4y agoMeh, grug just <script src="/js/mithril.js"></script> and ES6 at past job. Way less headache not needing build crap, just one blub maven Spring repository. Big ball of whatever may be seen as bad practice, but is honestly no worse than "best practices". Maybe not best for resume oriented development. Guess I had the luxury of only needing to support one browser.