sorry for the bluntness, but you should have probably thought twice before hitting the send to Hacker News button, i didn't find this in any way interesting and i am definitively not a LLM hater
From Rust to Ruby
91–100 of 108 posts
Re: From Rust to Ruby
#92Trigger alert - While it is good to signal your 900+ IQ to the peasants around you,many many smart and talented developers don't like rust so much so that they'll prefer writing their own programming language and their own compiler over writing single line of Rust. Jai and Odin come to mind with Jonathan Blow and Ginger Bill. Many many more folks that are capable of (and have) written widely used beautiful libraries…
The Rust community is as far from a "macho club" as it can possibly be.
Re: From Rust to Ruby
#93I always check hn comments before viewing the article . The comments alone saved me lot of time for not viewing the article
Re: From Rust to Ruby
#94Earlier quoted context omitted.
you sound jealous :)
That's an assumption. How do you infer that from written text? I can not infer that. To me it is super-strange that one uses AI to come to the conclusion that language x is better than language y. In the past people spent some time using both languages for a while, before reaching any conclusion. With AI it seems insta-gratification or insta-evaluation now. I am beginning to see why Google ruined its search engine fo…
My experience tells me. You are disagreeing with me, but you don't give negative vibes in your comment. The other comment sounded too negative:
> > >
It could have been worded neutrally and still convey the same points of disagreement. Interestingly, look at their other comments, they are all contentious.
I was also experimenting psychologically, to see what reactions I would get.
Re: From Rust to Ruby
#95Earlier 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 won't be as harsh because I have years of experience in Rails and didn't develop harsh feelings against it but moving from Rust/Go/Zig/TypeScript (which I used lately) to Ruby ain't smooth ride. Discoverability is much worse, LSPs aren't super helpful. Using Dash (documentation app) helps a ton. Still some names are confusing after switch (took a minute to recall that 'filter' is actually 'select' in Ruby). I won't…
filter is also just filter in ruby - aliased as select (and find_all) on Enumerable.
Re: From Rust to Ruby
#96Earlier quoted context omitted.
I would advice reading the "efficient rails" book, which explains a lot about how to debug RoR apps.
The fact that you have to read a book and break out a debugger to do the equivalent of "find all" in any other languages should tell you something right? My experience is exactly the same as Milch's. I've tried to fix stuff in Gitlab but given up when I couldn't even find where it things are defined. That can happen in other languages, e.g. Rust or C where macros are used. But it's pretty much the exception there whe…
Exactly. Sure, I can go read a book and learn about Rails. If I wanted to be a Rails specialist I probably would, but I don't want to be a Rails specialist. And like you said, other languages can do this too, but I haven't really found it to be too much of an issue. I remember one time where I had to break out whatever the rustc flag is that just produces the code with expanded macros, but that's it.
Re: From Rust to Ruby
#97Earlier quoted context omitted.
I won't be as harsh because I have years of experience in Rails and didn't develop harsh feelings against it but moving from Rust/Go/Zig/TypeScript (which I used lately) to Ruby ain't smooth ride. Discoverability is much worse, LSPs aren't super helpful. Using Dash (documentation app) helps a ton. Still some names are confusing after switch (took a minute to recall that 'filter' is actually 'select' in Ruby). I won't…
filter is also just filter in ruby - aliased as select (and find_all) on Enumerable.
facepalms
Weird that searching for it didn't yield any results, though I stand corrected. However it seems that select is the actual "root" of documentation. Filter sends to find_all, find_all sends to filter or select.
Re: From Rust to Ruby
#98Claude works in Rails apps extremely well. As the author of this blog points points out, Ruby allows you to get a ton done with minimal coding. Also, Rails uses convention over configuration, making Rails apps even terser.
One hypothesis for the effectiveness of Claude writing Rails apps is its token efficiency.
I ran across this project awhile back that attempts to measure and compare the token efficiency across projects, and Rails does really well:
Re: From Rust to Ruby
#99> I have no idea if it works or not because I haven’t yet tried running it.
This should have been disclosed in the first paragraph
Re: From Rust to Ruby
#100I'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]