4 ms·
because enterprises run huge and old systems performing critical functions, these systems get modified around the edges (small extensions, bugfixes, performance
by mxschumacher 6y ago
because enterprises run huge and old systems performing critical functions, these systems get modified around the edges (small extensions, bugfixes, performance tuning), not completely re-written.
To justify switching the stack (at gigantic expense in training and engineering), a vastly superior technology would have to present itself. I don't think switching from Java to Node would make a big difference for the bottom line.
- anon73044 6y ago>because enterprises run huge and old systems performing critical functions, these systems get modified around the edges (small extensions, bugfixes, performance tuning), not completely re-written. Not every enterprise runs a single huge monolithic app or codebase.
- fendy3002 6y agoAs a daily typescript developer coming from C#, I don't think TS will replace Java / C# even with it's typing system. For daily CRUD simple system, sure. For more complex operation I still vouch for C#. I don't know why, just feel like that, maybe stricter typing system and more verbose language is giving me more confidence.
- murukesh_s 6y agoit's baffling that at least even after a decade, no major adoption of Node.js ecosystem happened in enterprise. At least we expected new projects to migrate to Node.js but it did not happen yet. I believe the Node.js is yet to have large backing that Java had in it's early days which made things like JDBC and JMS and associated drivers from almost all vendors. Node.js feels like a not so solid, light-weight, scripting language in comparison.