4 ms·
I fully agree with you, but I still start projects in Ruby. Why? Because returns from startups are exponential and the interest rate is higher than the intere
by 3pt14159 9y ago
I fully agree with you, but I still start projects in Ruby.
Why?
Because returns from startups are exponential and the interest rate is higher than the interest rate on the technical debt.
It's why compiled is a great choice for an established corporation with a well defined need and a large user base, while interpreted is better for most other business contexts, especially with tools like Numpy.
- perfmode 9y agoHave you seen helix? Ruby-Rust interop: https://usehelix.com/ https://usehelix.com/
- 3pt14159 9y agoYeah, but I've been doing this stuff for a while now. I used to do it in C and then in Nim (unlike Go until about a year or two ago, Nim could always compile shared objects, so using it through the ruby FFI was pretty straight forward. I've also done some stuff in Cython and just communicated through the database to my Rails app. I'm still not sure what the best way of doing things is. I tend to think that Rust is going to be the programming language of tomorrows operating system, but I'm not sure if it is going to get the wide library support of something like Cython, since the scientific community isn't as fractured as the software community. Tools like graph-tool / scipy / etc are hard to live without.