4 ms·
> But I never found good use of it outside of small projects. Any serious business work becomes very painful to maintain and stay on top of for bigger projects.
by DarkWiiPlayer 7y ago
> But I never found good use of it outside of small projects. Any serious business work becomes very painful to maintain and stay on top of for bigger projects.
That statement reminds me a lot of the conclusion I came to on a reddit post[1] a while ago, where I compared Rubys fibers¹ to Luas coroutines, more specifically, how many of them could viably be used concurrently:
> Conclusion: Ruby is awesome; just don't use it for anything serious.
¹ Note that after Ruby 2.7 was recently released with a supposedly improved coroutine implementation, I repeated the benchmark and did see a slight improvement in execution time (no change in the maximum number of coroutines), but it was still orders of magnitude slower than even the PUC Rio implementation of Lua.
[1] https://www.reddit.com/r/lua/comments/cgqfch/lua_coroutines_vs_ruby_fibers_benchmark/ https://www.reddit.com/r/lua/comments/cgqfch/lua_coroutines_...
- pdimitar 7y ago> Conclusion: Ruby is awesome; just don't use it for anything serious. LOL! Funnily put. This did offend some in this here mini thread but I indeed gradually -- with business and personal usage -- came to that conclusion by myself. Nowadays I am pretty hopelessly hooked to Elixir. Parallelism and concurrency basically solved, extremely fast for a dynamic language, FP, compile-time macros (so basically code generation without the boilerplate source code), several very solid and customisable frameworks (web/API/GraphQL, DB data mapper), predictable lag even under extreme load, and I am just in love. Now only thing left is Rust to emulate the BEAM's runtime. :) If we were to have a vote for a language with which you replace a slightly more complex bash/zsh scripts however, I'd vote for Ruby. It's very terse, it's fast enough (without Rails I mean) and it mostly reads well. Or I dunno, maybe Tcl/Tk or OCaml.