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

From Rust to Ruby

xlii.space

Post reply on HN
Print view View original

11–20 of 108 posts

Re: From Rust to Ruby

#12

Post by honeybadger223 »

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.

Re: From Rust to Ruby

#13

Post by JSR_FDED »

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…”

Re: From Rust to Ruby

#14

Post by eager_learner »

daemin wrote: post #3

At first I thought this would be an interesting article, but as soon as they mentioned using an LLM to do the conversion I lost all interest. It's like saying "I wanted this done so I got my underling to do it, here is my story...". Like why would I bother to read it then, as it was clearly not you doing the conversion or putting any thought into it.

you sound jealous :)

Re: From Rust to Ruby

#15

Post by digitaltrees »

I built a set of gems (propel_rails) that takes the already terse Ruby on Rails code to the next extreme. It generates a set of top level classes like an API controller and some concerns that then create a full restful resource (model, controller, serializer, unit and e2e tests) with 0 boilerplate code. The controller ends up being only a list of all permitted attributes the api will accept because the restful actions are automatically generated. It’s a bit hard to fully describe but the meta programming power of Ruby really does make amazing things easy.

Re: From Rust to Ruby

#17

Post by nine_k »

digitaltrees wrote: post #15

I built a set of gems (propel_rails) that takes the already terse Ruby on Rails code to the next extreme. It generates a set of top level classes like an API controller and some concerns that then create a full restful resource (model, controller, serializer, unit and e2e tests) with 0 boilerplate code. The controller ends up being only a list of all permitted attributes the api will accept because the restful action…

This sounds like CRUD, distilled.

I suppose it works in terms of your domain model?

Re: From Rust to Ruby

#18

Post by milch »

october8140 wrote: post #4

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 but use Rails all day, sure, but the whole convention over configuration thing is such a huge anti pattern to me.

Re: From Rust to Ruby

#19

Post by craigmcnamara »

milch wrote: post #18
october8140 wrote: post #4

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…

method(:name).source is your friend
Post reply on HN