I get your point but it's a case of right tool for the job. Every copy of Ruby now includes YJIT written in Rust because Rust is the right tool for that task.
It's easy to forget though that number of lines of code required to do something is also a valid metric and Ruby beats Rust on that.
So if you're shipping CRUD web apps that might be a more important metric than say memory usage or CPU time.
Different job, different tool. More people want to ship web apps than write their own JITs.
It's easy to forget though that number of lines of code required to do something is also a valid metric and Ruby beats Rust on that.
So if you're shipping CRUD web apps that might be a more important metric than say memory usage or CPU time.
Different job, different tool. More people want to ship web apps than write their own JITs.
Engineering is the art of trade offs.