I think that many a time people begin a project coding in a far-far-far too-low level programming-language: they’re solving the wrong problem!
Build your prototype in a high level language, get the model/architecture correct … and THEN begin replacing the slow bits with faster languages…
To me that seems right.
Haskell to begin-with, & when it solves ALL of the problem, correctly … THEN you begin converting stuff to Crab-lang/Rust…
When you’re still bashing 'round, trying to discover the form of the underlying problems in your problem … that’s the wrong time to be doing low-level stuff, to my eyes…
I get the sentiment, but I think Rust does a pretty decent job even in the prototyping phase. I’ll run snippets in Python or Lua, but that’s mostly for data mangling, like generating code from a data format or preparing test data.
I think that many a time people begin a project coding in a far-far-far too-low level programming-language: they’re solving the wrong problem!
Build your prototype in a high level language, get the model/architecture correct … and THEN begin replacing the slow bits with faster languages…
To me that seems right.
Haskell to begin-with, & when it solves ALL of the problem, correctly … THEN you begin converting stuff to Crab-lang/Rust…
When you’re still bashing 'round, trying to discover the form of the underlying problems in your problem … that’s the wrong time to be doing low-level stuff, to my eyes…
_ /\ _
I get the sentiment, but I think Rust does a pretty decent job even in the prototyping phase. I’ll run snippets in Python or Lua, but that’s mostly for data mangling, like generating code from a data format or preparing test data.
So far it works pretty well.