Building Fast Interpreters in Rust

Re:Building Fast Interpreters in Rust by chris_st on Monday March 04, 2019 @04:14PM (#19305582)

Many years ago, I switched from working on a C++ project to one using Java. I was amazed how fast the Java compiled!

The downside: I used to use the "waiting for the compiler" time to think about what I'd written, consider alternatives, think about refactoring, etc.

Suddenly I had to block out time for that :-)

[ Parent | on HN ]

Re:Building Fast Interpreters in Rust by sitkack on Tuesday March 05, 2019 @10:48AM (#19311267)

In seriousness, maybe part of the power of C++ is how it forces the programmer to slow down, be more methodical and concentrate more. A language that is faster and looser, could also burn out the programmer faster and encourage shallower thought patterns.

I know that when I am trying to find a bug (any bug, it could be logical or data) that I am slowing down a simulation of the interaction of components in my head. This helps one understand all of the abstractions and evolutions of processes within the program. Maybe that very act is the power of C++.

[ Parent | on HN ]

Re:Building Fast Interpreters in Rust by malkia on Monday March 04, 2019 @10:49PM (#19307941)

My "gentle" java introduction came by using GWT (java -> javascript). Also we had just one module, so it took quite a long time tom compile :)

At least most of the unit tests were run under java - e.g. the "business" (ui) logic.

[ Parent | on HN ]