4 ms·
I think JavaScript is at its most useful within the bounds of a single threaded event loop, personally. Cool project and props for Node module interop, but I p
by lucasyvas 4y ago
I think JavaScript is at its most useful within the bounds of a single threaded event loop, personally.
Cool project and props for Node module interop, but I personally can't see why I'd use this.
If you want to go more parallel/concurrent, there are already great languages to choose from! Unless you're of the mindset that everything that can be done with JavaScript will be done with JavaScript :)
- Scarbutt 4y agobut I personally can't see why I'd use this. For webapps, it means using one language/ecosystem instead of two.
- deleted 4y ago[deleted]
- beebeepka 4y agoAahaaa... What about already existing projects or front-ends? Nobody should use workers because there are other languages out there and also because lucasyvas said so with a playful smile
- 0x445442 4y agoThis! The single threaded event loop is a great model for UI development but it’s a train wreck for handling http requests. I’ve spent the last year adding features to and fixing bugs on various micro services written in Java where the authors decided to use the new shiny reactive frameworks in attempt to turn Java into NodeJS. On a number of occasions I’ve been in meetings where the original authors got lost in their on maze Just Single madness. The worst part is these were “Staff Engineers” who I know never did any type of analysis/engineering to show these frameworks provided any type of advantage over the more traditional threaded frameworks when considering runtime performance, resource requirements, understandability and maintainability.