> Multiple large clusters of servers distributed across the world, capable of serving over 75 million requests per minute That doesn't say anything at all sadly. Ruby people seem to be sensitive when someone asks them about performance, my last question about that was downvoted heavily here. I don't know any Ruby, I know how much Go can handle with the stdlib, a single non-parameterized route, returning "hello world"…
Ruby 3.2’s YJIT is Production-Ready
121–130 of 304 posts
Re: Ruby 3.2’s YJIT is Production-Ready
#122You love to see the continued investment in this language. I've been using Ruby for about a decade and I'm still enjoying writing code in it. I hope the language continues to improve and the community stays vibrant. I can remember about 8 years ago someone telling me how they were worried Ruby (and Rails) was dying. At this point the community could dry up and I think I'd still stick with it.
Re: Ruby 3.2’s YJIT is Production-Ready
#123I use Ruby and Chef at work (MAANG). For side projects, I use Rails 7 to get things going and replace components selectively with native extensions and separate processes. It's all about productivity, especially when small, because performance is rarely an issue.
Re: Ruby 3.2’s YJIT is Production-Ready
#124Glad to see Ruby still going strong it will forever be the 1st programming language I actually loved working with, and the combination of it with Rails was amazing. Had to move to the other side (Typescript, Django) but I think unless ChatGPT will write all the code 10 years from now - Rails and Ruby will still be there, providing teams with a lot of power and a lot of fun.
Re: Ruby 3.2’s YJIT is Production-Ready
#125It shows that Ruby still has life left in it yet. The language itself is wonderful, there's a great ecosystem of tooling but the performance was always lagging. Hopefully some of this makes it a choice for people once more over other more esoteric languages. My only concern here would be the time and sunk cost fallacy of someone like a Shopify working on a Ruby JIT. It reminds me of when Facebook was working on the H…
[deleted]
Re: Ruby 3.2’s YJIT is Production-Ready
#126I'm still a shameless ruby fanboy at heart. To be fair, its almost all devops type tasks but there is something about that language that just clicks with me, and while I def have to use python more than ruby, I still love ruby.
Re: Ruby 3.2’s YJIT is Production-Ready
#127You love to see the continued investment in this language. I've been using Ruby for about a decade and I'm still enjoying writing code in it. I hope the language continues to improve and the community stays vibrant. I can remember about 8 years ago someone telling me how they were worried Ruby (and Rails) was dying. At this point the community could dry up and I think I'd still stick with it.
[deleted]
Re: Ruby 3.2’s YJIT is Production-Ready
#128I'm so grateful for these geniuses working tirelessly on improving the language and runtime, and it allows me to just add an argument and magically my code runs faster. It's been fascinating following Maxime working on Yjit.
Re: Ruby 3.2’s YJIT is Production-Ready
#129> Multiple large clusters of servers distributed across the world, capable of serving over 75 million requests per minute That doesn't say anything at all sadly. Ruby people seem to be sensitive when someone asks them about performance, my last question about that was downvoted heavily here. I don't know any Ruby, I know how much Go can handle with the stdlib, a single non-parameterized route, returning "hello world"…
Re: Ruby 3.2’s YJIT is Production-Ready
#130Man that is a terrible graph. Why use tiny fonts and smush them together, them make the image small as well. I wish I could read the charts...