4 ms·
Node because dynamic typing is easier to work with and it's nearly as fast as a compiled language. I'd just recommend to avoid npm.
by mabynogy 9y ago
Node because dynamic typing is easier to work with and it's nearly as fast as a compiled language. I'd just recommend to avoid npm.
- filleduchaos 9y agoJavaScript in the context of Node is a (just-in-time) compiled language. And compilation in and of itself is not a magical conferrer of speed or resource efficiency, and there is a wide range of performance among compiled languages. A shitty compiler will produce shitty machine code. And while V8 is an amazing project, there's the mild inconvenience of JS/Node not even approaching languages like C, C++ or Rust in speed or memory efficiency.
- mabynogy 9y agoIt is faster in real life when you include compiletimes.
- filleduchaos 9y agoI mean, if you want to go right ahead and admit that you have so few users/your users use your product so little that build time is a significant metric for you vs runtime performance costs, I won't stop you
- mabynogy 9y agoJavascript is one the most used language. Even HN uses it a bit.
- bwbw223 9y agoHow is dynamic typing easier? It makes it way easier to introduce bugs- Recently I was working on a timer (for speedsolving Rubik's cubes) and I had accidentally had tried to format an already formatted time for user display, so all that was shown was `undefined` for times over a minute. It was hard to uncover, because the calls were in seperate parts of the codebase, and I wasn't able to make the field/formatter only allow numbers because of the nature of Javascript.
- mabynogy 9y agoIt is known by studies. People are more comfortable and productive with dynamically typed languages. The most productive language is smalltalk.
- scarface74 9y agoHave these "studies" taken into account maintainability? There is a whole class of bugs that won't happen with a statically typed language. There also a whole class of automatic refactors that you can do with statically typed languages.
- mabynogy 9y agoIt's about productivity not correctness.
- scarface74 9y agoHow can you be "productive" writing code that isn't "correct"? That's the worse type of developer - the one who does "negative work". Negative work is when someone does work so badly that it takes more time to correct their errors than it would have for them not to do the work at all.
- mabynogy 9y agoYou're talking about you and your opinions. For a given task, random programmers are quicker at achieving the goal with dynamic programming languages. That's why scripting languages are popular. They are also easier to learn.
- scarface74 9y agoHow could it be a "goal" to have incorrect code?