3 ms·
JS held a lot of appeal for me - coming from the Java world - because you didn't need a lot of tooling but basically a text editor and a browser. Add a handful
by iSnow 10y ago
JS held a lot of appeal for me - coming from the Java world - because you didn't need a lot of tooling but basically a text editor and a browser. Add a handful of libraries and I started liking that goofy little language.
Of course that setup still works, but if you want to do anything a bit more advanced, you descend into a living hell that feels as complicated an impenetrable as J2EE did. As clunky as the JCP is, in the last years it helped create a couple of sane standards from existing implementations. I just wish there was something similar in JS world.
- z3t4 10y agoI also like that all you need is a simple editor and a browser or NodeJS or both. I think the problem is going from writing static or server rendered HTML into making a web/js app, you try to reuse the design patterns from server HTML rendering, witch is like using the wrong side of a hammer. If you write a web/JS-rendered app all the HTML you need is <script src="main.js"></script>