3 ms·
Devices thrive through native, strongly typed, compiled languages, because both are fast and need each other to make each other happy. Programmers thrive thro
by gesman 13y ago
Devices thrive through native, strongly typed, compiled languages, because both are fast and need each other to make each other happy.
Programmers thrive through interpreted languages because it is fast to learn and allows boss and his programmers to craft something quickly to show up for their effort.
- dragonwriter 13y agoAs ahoge points out, interpreted/compiled is an implementation detail. OTOH, you might have a point if you replaced the first category with "strongly, statically typed" and the latter category with "weakly and/or dynamically typed". On the third hand, maybe not -- with its type inference, Haskell (and, IME, even Scala, with its much more limited type inference) allow crafting working code with speed comparable to, e.g., Python. Perhaps its not strong/static typing that slows down the dev process so much as implementations of such systems that require lots of ritualistic incantations to the type system.
- ahoge 13y ago> interpreted languages Being interpreted is an implementation detail. For example, V8 (Chrome's JS engine) doesn't have an interpreter. It compiles to (quick and dirty) machine code right off the bat. Later, the "hot" parts are compiled to better more optimized machine code. There are also several C interpreters.