Live data from Hacker News

From Rust to Ruby

xlii.space

21–30 of 108 posts

Re: From Rust to Ruby

#21
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…

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.

Re: From Rust to Ruby

#22

Idk why people are shitting on you. So many LLM haters on here. It’s changed the game completely and some people just don’t want to accept it. I think this is cool. Verbosity of languages is important when it comes to coding with AI. I’ve found Go to be a happy medium.

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

Re: From Rust to Ruby

#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.

Re: From Rust to Ruby

#25

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

It’s short term happiness at best, and at the expense of every other possible architectural characteristic (maintainability, performance, reliability, scalability, you name it).

Re: From Rust to Ruby

#26
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…

[deleted]

Re: From Rust to Ruby

#27
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.

dbg! Is your friend

Re: From Rust to Ruby

#28
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.

Hell with lombok it’s not even uncommon to have entire classes with no defined functions at all. shudder

Re: From Rust to Ruby

#30
I'm sometimes amazed by project sizes, a 30k line codebase is small? I'm aware that the ceiling is high but 30k lines of code can encode so much information and behavioural nuance.

Maybe this is just my backend/network focus with Golang though. Scaling beyond 10-15k lines of code always was quite intimidating as it is usually where I lose the ability to just keep a model of the codebase fully in my head.

Post reply on HN