Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ruby 3.4.0

ruby-lang.org

Post reply on HN
Print view View original

21–30 of 282 posts

Re: Ruby 3.4.0

#21

Post by briandear »

thdhhghgbhy wrote: post #12

Why did NodeJS take off on the backend while Rails was still popular? I'll never understand it.

Because of the JavaScript Everywhere crowd. When you have a hammer, everything looks like a problem for JavaScript.

Re: Ruby 3.4.0

#22

Post by t-writescode »

FBISurveillance wrote: post #20
tuananh wrote: post #10

Shopify strategy aka the story of YJIT If I cannot refactor my services, I shall refactor Ruby instead.

Since when contributing back to the community is considered a bad faith move?

That's certainly not what I get out of what they said.

Shopify has introduced a bunch of very nice improvements to the usability of the Ruby language and their introductions have been seen in a very positive light.

Also, I'm pretty sure both Shopify for Ruby and Facebook for their custom PHP stuff are both considered good moves.

Re: Ruby 3.4.0

#24

Post by FBISurveillance »

t-writescode wrote: post #15
shortrounddev2 wrote: post #7

What does ruby do well that other languages don't? What is the niche it's trying to fill?

Rails has some very, very good features that make standing up a CRUD app with an administrative backend _very easy_. It's also got a bunch of semi-functional-programming paradigms throughout that make life quite a bit easier when you get used to using them. Honestly, if it had types by default and across all / most of its packages easily (no. Sorbet + Rails is pain, or at least was last I tried), I'd probably recomme…

I love Rails and spent a good chunk of my career using it - and I'd recommend it more if only the frontend story wasn't that bumpy over the years with all the variations of asset pipelines.

I wish the TypeScript/React integration was easier. Say what you will but there's no way you can achieve interactivity and convenience of React (et al) UIs with Turbo/Hotwire in a meaningful time.

Re: Ruby 3.4.0

#25

Post by mtkd »

dragonwriter wrote: post #19

Already outdated: https://www.ruby-lang.org/en/news/2024/12/25/ruby-3-4-1-rele...

I had just hit this issue (3.4.0 showing as 3.4.0dev in rbenv) and am having a coffee before looking at what is going on -- thanks for posting

Re: Ruby 3.4.0

#26

Post by capitol_ »

pests wrote: post #6
PittleyDunkin wrote: post #3

Earlier quoted context omitted.

I'm pretty sure the only reason people ever used parser generators is that it allows a language that vaguely resembles the formal description of the target language. I always found them very confusing to write, confusing to debug, and much less efficient than writing your own. It's actually pretty straightforward once you get the tokenization and lookahead working.

Agreed. Parser generators are a magic black box. Parsing is not too difficult, there is some actual computer science in some spots, but I think parsing should be a core complacency of a programming language to unlock full potential.

A very very long list of CVEs disagrees with that parsers are "not too difficult".

Re: Ruby 3.4.0

#28

Post by continuational »

speleding wrote: post #11
shortrounddev2 wrote: post #7

What does ruby do well that other languages don't? What is the niche it's trying to fill?

It's the language with the highest ratio of (useful work / LOC), so it's the least verbose language. This makes it very suitable to write and understand complex scripts, because the reduced boilerplate means less cognitive overhead for the programmer. As a result, experienced programmers can be extremely productive with it. The well-known Rails framework uses this to great effect, however, some people argue that the…

Experienced teams love magic?

Re: Ruby 3.4.0

#29

Post by block_dagger »

FBISurveillance wrote: post #24
t-writescode wrote: post #15

Earlier quoted context omitted.

Rails has some very, very good features that make standing up a CRUD app with an administrative backend _very easy_. It's also got a bunch of semi-functional-programming paradigms throughout that make life quite a bit easier when you get used to using them. Honestly, if it had types by default and across all / most of its packages easily (no. Sorbet + Rails is pain, or at least was last I tried), I'd probably recomme…

I love Rails and spent a good chunk of my career using it - and I'd recommend it more if only the frontend story wasn't that bumpy over the years with all the variations of asset pipelines. I wish the TypeScript/React integration was easier. Say what you will but there's no way you can achieve interactivity and convenience of React (et al) UIs with Turbo/Hotwire in a meaningful time.

Try React on Rails [1]. I’ve found it to be a very pleasant development experience.

[1] https://github.com/shakacode/react_on_rails

Post reply on HN