Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Hehe, good one!

Oh, you're serious? :D



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.


developer 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)


Please stop the grugposting, it is impossible to read.


you in thread for grug story! no like, no read!


Made me smile, have my upvote


always be grugposting


Meh, 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.


Vanilla js has modules though. You don't need a build step to use modern APIs.


Average js zealot.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: