3 ms·
While it is probably not a very good idea to use this to code, it reminds me of something DHH once said about Ruby. I don’t have the quote, but he said that he
by leodriesch 5y ago
While it is probably not a very good idea to use this to code, it reminds me of something DHH once said about Ruby.
I don’t have the quote, but he said that he just loves the language because it is so fun to write for him, despite it not being the optimal language. And this alone makes him get into flow much more easily and therefore be more productive.
This alone has made me gain interest in learning Ruby. It might be slower than lots of languages out there, but backend computing power is often not the main bottleneck in your stack. Developer velocity is probably much more important when it comes to producing great software and moving fast.
- exdsq 5y agoThere are cool tools to be more efficient using factory workers such as https://github.com/contribsys/faktory_worker_ruby https://github.com/contribsys/faktory_worker_ruby I'm keen to pick up ruby too!
- setpatchaddress 5y agoKind of a tangent, but Ruby-is-slow was always contextual. Ruby was always hugely faster than complex bash scripts for the same task. If you value launch time, Python (at least through 2.x) was always slower from a cold launch compared with Ruby.
- bcrosby95 5y agoThis is how I look at vim. I don't think typing speed really matters for development. But I just find it so fun to see how much I can target exactly the chunk of code I want to change. It turns coding itself into a game.