3 ms·
> nodejs because everyone is using nodejs and your language is now banned it's not surprising there's noticeable performance differences, it was certainly predi
by snaky 8y ago
> nodejs because everyone is using nodejs and your language is now banned it's not surprising there's noticeable performance differences, it was certainly predicated early on but they where to caught up trying to be google and using the popular language to hire as many people as possible
I wonder how typical is this nowadays in IT companies and departments all around the world.
- xkcd-sucks 8y agoAt least somewhat. I'm aware of a nodejs script that is basically packed up with the node runtime and run on Windows as a "native application," which interacts with the filesystem, windows registry, and more. The packer is years old and nobody knows how it works. It is everything you expect of such a program. From both a user and developer perspective. It is deployed on very expensive, very important equipment in pharma labs and hospitals.
- dotancohen 8y agoThis is less uncommon than people like to admit. I've seen, and in some cased directly involved with, code written by an inexperienced (giving benefit of doubt here) developer whose position was replaced twice over, that runs critical systems on big-money (but not life-threatening) equipment and business systems. No documentation, no tests, even one that relies on a known platform bug to never be fixed (not kidding). Nobody knows how it works, and there is no time go go through it and clean it up (business decision). I've even stated in writing on one system that I refuse to receive "emergency" calls on holidays, weekends, or nights to fix a particular system if it ever goes down at that time. Management refusal to plan ahead or heed warnings does not constitute an emergency on my part.