Are you daft, ignorant, or am I *completely* missing something.
Rust is compiled. And memory management with the borrow checker is front and center even *moreso* than C and C++.
Unless you are specifically teaching a Unix class, an IDE is really the only good way to get a useful programming environment on Windows. You know, Windows, that funny OS that runs on 99% of the x86 laptops that students now have.
Using Eclipse, for example, allows all of the students access to JUnit and CVS via a consistent interface.
The biggest shock for most of my students was automated testing. Projects had a base set of tests that ran automated up until the deadline. After the deadline, I would run an extra set of tests to make sure that they were solving the problem rather than just writing to my tests.
All students had to do was check correct code into the CVS repository and the automated testing system would take over from there and produce a web page with the test results. Of course, creating correct code was always the trick...
... and it can't be faster than binaries that went through and optimizing compiler.
Not true.
A static compiler can only make optimizations which are a universal improvement. A JIT can make optimizations based upon usage patterns of the specific invocation (OS, memory system, disk access, input data, etc.) which might not hold for all invocations of the program.
Slashdot Mirror
Are you daft, ignorant, or am I *completely* missing something. Rust is compiled. And memory management with the borrow checker is front and center even *moreso* than C and C++.
Unless you are specifically teaching a Unix class, an IDE is really the only good way to get a useful programming environment on Windows. You know, Windows, that funny OS that runs on 99% of the x86 laptops that students now have.
Using Eclipse, for example, allows all of the students access to JUnit and CVS via a consistent interface.
The biggest shock for most of my students was automated testing. Projects had a base set of tests that ran automated up until the deadline. After the deadline, I would run an extra set of tests to make sure that they were solving the problem rather than just writing to my tests.
All students had to do was check correct code into the CVS repository and the automated testing system would take over from there and produce a web page with the test results. Of course, creating correct code was always the trick ...