Live data from Hacker News

From Rust to Ruby

xlii.space

101–108 of 108 posts

Re: From Rust to Ruby

#101
post #24

I do wonder if it'll ever be possible to get Rust tests to feel as nice to write as, say, test suites in Python or Ruby. I might just be missing a lot of helpers, but a part of me really wants to use a test metalanguage that (for example) RC's everything, gives me implicit casts from strings to what ever type I need, and a bunch of other stuff. I've always found Rust object buildup to be pretty annoying.

[dead]

Re: From Rust to Ruby

#102
post #46

Earlier quoted context omitted.

If you replaced "AI" with "a developer" in this article, it might make more sense why it's being dunked on. It would be an article about someone telling someone to do something, and then when the work was done they were happy with the result. It's just a bit of a nothing all round

> and then when the work was done they were happy with the result It's worse than that -- they don't even know the result! They never tried to run it!

oh yeah - in this case the result is that the code was smaller and they were happy with that. correctness was not a criteria

Re: From Rust to Ruby

#103
post #18

I'm not sure any language + framework prioritizes developer happiness as much as Ruby on Rails.

I don't think I've ever been unhappier than working on a Rails project. See a bug on the site - something is rendering incorrectly. grep to find the view. Great, there's a method that is being called to render the buggy section. Grep for the method name - 0 hits. Amazing, it's something that is synthesized somewhere and I have no idea where. Guess I'll stop what I'm doing and read docs for an hour. If you do nothing…

The worst part is communicating to the Ruby on Rails community that they have a problem with DX or that Rails is not really the top choice anymore for new startups. It's a cult of DHH. I am still mostly part of the Rails ghetto; it's paying my bills, but after gaining more experience during my computer science master's degree with statically typed languages, I clearly see the pitfalls of Ruby.

People often miss the difference between simple and easy. Yes, Ruby is easy, but it's not simple, and it will make you suffer a lot if you get to a complex app. The debugging sessions in Rails are a nightmare. Meanwhile Ruby community is acting like religion, it's almost impossible to convert people from Ruby to other languages, they don't see the language as tool, but as part of their identity

Re: From Rust to Ruby

#104
post #18

Earlier quoted context omitted.

I don't think I've ever been unhappier than working on a Rails project. See a bug on the site - something is rendering incorrectly. grep to find the view. Great, there's a method that is being called to render the buggy section. Grep for the method name - 0 hits. Amazing, it's something that is synthesized somewhere and I have no idea where. Guess I'll stop what I'm doing and read docs for an hour. If you do nothing…

I’ve had similar experiences with Spring Boot Java applications. Methods in stack traces that don’t exist in source code but are magicked into existence by annotations.

Spring Boot is very similiar to Rails. That's what was surprising to me, when I was forced to use it at uni. The annotations magic brings all the PTSD of method missing from Ruby

Re: From Rust to Ruby

#105
post #42

Earlier quoted context omitted.

Honest question: what’s an example of a fully-featured web framework that makes upgrading a “large & old” application painless? In my experience, upgrading an underlying framework that a piece of complex software depends upon without breaking everything pretty much always requires time & good test coverage.

Type safety would fix 99% of the issues I've had upgrading Rails.

things that people in Ruby community don't like to hear for $1000

Re: From Rust to Ruby

#106
post #18

Earlier quoted context omitted.

I don't think I've ever been unhappier than working on a Rails project. See a bug on the site - something is rendering incorrectly. grep to find the view. Great, there's a method that is being called to render the buggy section. Grep for the method name - 0 hits. Amazing, it's something that is synthesized somewhere and I have no idea where. Guess I'll stop what I'm doing and read docs for an hour. If you do nothing…

The worst part is communicating to the Ruby on Rails community that they have a problem with DX or that Rails is not really the top choice anymore for new startups. It's a cult of DHH. I am still mostly part of the Rails ghetto; it's paying my bills, but after gaining more experience during my computer science master's degree with statically typed languages, I clearly see the pitfalls of Ruby. People often miss the d…

Maybe I'm just not tapped into the community but I've been a ruby developer going on 6 years now and I find debugging ruby apps no better or worse than any other languages I've worked with over the years. It's fairly easy to instrument ruby much like all the other dynamic languages (python3, js, etc) but with better ergonomics. My main qualm with ruby is their reliance on external type files for type annotations. What a terrible idea. Should have just done inline optional types like python3 or typescript.

Re: From Rust to Ruby

#107
post #89

This defies belief. “I wanted to scratch a technical itch. My local AI completed the job in 30 minutes. I never pressed Start to see if it works, but I did write a blog post about it…”

2016 check out my new JavaScript Library! 2026 check out the work I didn't write! 2036 how I've written 200 lines in this ancient Latin called C

2037 using humans to accelerate your token throughput by a fellow LLM (the 7th method will surprise you)

Re: From Rust to Ruby

#108
post #42

Earlier quoted context omitted.

Honest question: what’s an example of a fully-featured web framework that makes upgrading a “large & old” application painless? In my experience, upgrading an underlying framework that a piece of complex software depends upon without breaking everything pretty much always requires time & good test coverage.

Type safety would fix 99% of the issues I've had upgrading Rails.

Yes, typing would obviate the need for the sorts of extensive unit testing I'm talking about here. I feel that. Luckily, the frontier LLMs (especially Claude) have gotten _really_ good at writing Rspec...
Post reply on HN