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

Building GitHub with Ruby on Rails

github.blog

Post reply on HN
Print view View original

221–230 of 332 posts

Re: Building GitHub with Ruby on Rails

#221

Post by ackfoobar »

rajamaka wrote: post #60
KyeRussell wrote: post #54

Earlier quoted context omitted.

Amen. Until recently, I was exclusively working with Django for 5+ years. I definitely fell into the trap of making the ORM for granted. Had a brief foray into the JS world and despite plenty of slick-looking projects with fancy pants websites, nothing remotely compares.

What JS based ORMs did you use that you weren't a fan of?

Slightly related, I'm not used to using ORMs. Spoiled by jooq from the JVM world, writing SQL with the query builder in TypeORM was a terrible experience.

Re: Building GitHub with Ruby on Rails

#222

Post by winrid »

rajamaka wrote: post #60
KyeRussell wrote: post #54

Earlier quoted context omitted.

Amen. Until recently, I was exclusively working with Django for 5+ years. I definitely fell into the trap of making the ORM for granted. Had a brief foray into the JS world and despite plenty of slick-looking projects with fancy pants websites, nothing remotely compares.

What JS based ORMs did you use that you weren't a fan of?

The thing is - even if someone creates an amazing ORM for Node, I doubt I'd use it. I am tired and done with async everything. No more NodeJS for business logic.

Now, if someone could create a Django-like ORM for Java or Rust, then we're talking. Hibernate and Diesel are nowhere near Django's ORM in terms of productivity and "it just works" factor. Go's GORM looks pretty good but haven't tried it. jooq does not look as easy to use or setup, and the workflow is entirely different.

Re: Building GitHub with Ruby on Rails

#223

Post by sickcodebruh »

gedy wrote: post #206
sickcodebruh wrote: post #196

Earlier quoted context omitted.

I started my professional career with Rails 8 years ago and deeply miss aspects of it. It uses lines of code so efficiently, letting you go from zero to product with outrageous speed. Everything is a solved problem. Ruby as a language is so expressive, so beautifully ergonomic, so easy to read. It's such a joy. But the view layer has not aged well. After years of working with a focus on React and TypeScript, I can't…

> But the view layer has not aged well. Agreed - In my opinion, Rails messaging/soft marketing could be a lot better about how it's great for a data driven backend, whatever the frontend/UI. I know there's things like API mode and webpacker, but this all seems very secondary and begrudging at times. Maybe I listen too much to what DHH says, but definitely think the Rails view stuff should be what's secondary. It's a…

I dunno, I think that there are a lot of products and developers who need the view to be as important as the backend, and it would be a shame for Rails to stop trying to woo them. Rails is making a big push for Hotwire (https://hotwired.dev/) and on paper, it certainly looks like a very Rails-y way of doing views. Elixir users seem obsessed with LiveView and this seems cut from the same cloth, so maybe it’s the answer? But for it to be compelling for folks like me, it needs to be a bit more React-y: components with well-defined, type-safe interfaces, unidirectional data flow.

Re: Building GitHub with Ruby on Rails

#224

Post by silasb »

sickcodebruh wrote: post #196
upmostly wrote: post #3

I absolutely love Rails. I'll always remember back in 2010 catching the train to Waterloo station in London and seeing a huge sign overlooking the train tracks that read something like "We Need Rails Developers". Rails was such a huge part of my professional career. Now, 13 years later and I'm deep in the JavaScript ecosystem and have been for 8 years. The most exciting thing to come out of this ecosystem recently is…

I started my professional career with Rails 8 years ago and deeply miss aspects of it. It uses lines of code so efficiently, letting you go from zero to product with outrageous speed. Everything is a solved problem. Ruby as a language is so expressive, so beautifully ergonomic, so easy to read. It's such a joy. But the view layer has not aged well. After years of working with a focus on React and TypeScript, I can't…

ViewComponent, from Github makes writing views much better, but it's far from perfect.

Re: Building GitHub with Ruby on Rails

#225

Post by hocuspocus »

ksec wrote: post #199

And as I have said before but worth repeating again, Rails is perhaps the only open source framework that is being battle tested in development at scale. It may not be the fastest ( or in fact quite slow ), but I dont think you could find similar testing being done and Deployed at the scale of Github on any other framework. I wonder if Eileen Uchitelle will bring this practice to Shopify as well? Edit: It seems [1] S…

> but I dont think you could find similar testing being done and Deployed at the scale of Github on any other framework.

?!

There's at least Spring.

Re: Building GitHub with Ruby on Rails

#227

Post by didip »

I must be the only person on Hacker News who dislike Ruby.

It simply has too much magic and doesn't offer enough abilities (unlike Elixir or any Scheme variant) to justify the dynamic type nature.

Go and Rust are perfect for me (and maybe Zig?). They covered everything I need.

Re: Building GitHub with Ruby on Rails

#228

Post by kayodelycaon »

WirelessGigabit wrote: post #209
samwillis wrote: post #9

GitHub running off the main branch is fascinating, and initially sounds mad, but makes so much sense. Assuming they have very high test coverage, running against mainline Rails isn't really any different to having the fork they had before, but they have more influence on future development. It must also be a massive boon for the Rails ecosystem to have such a large property running off the head. Doesn't anyone know o…

You MUST have an insane amount of test coverage to trust something like this to Ruby. I'm new to Ruby, with 13 yoe as a SW engineer. Personally, I find it a very hard language to master. Writing tests often feels like I'm settings variables left and right without seeing them being used in the current context. But that then happens to be part of the let() way in rspec. Now you might say: why use rspec? I inherited thi…

I’m a long time Ruby and Rails developer. I know how the magic works from reading source code.

A lot of stuff uses method_missing and define_method. There’s also instance_eval, which is used to create DSLs like rspec. Once you know what they do, stuff makes a lot more sense.

Re: Building GitHub with Ruby on Rails

#229

Post by willlma »

ok123456 wrote: post #219
winrid wrote: post #215

Earlier quoted context omitted.

Maybe some day Ruby will get type hinting. I'm loving it in Python. In terms of the "I wrote a block somewhere and it broke when executed for the first time two weeks later" - don't do that in a scripting language. Use the REPL to build/test the block. That's the trade off - instead of a compiler you get a fast REPL - use it! :)

it already does

Please say more. What's your setup?

Re: Building GitHub with Ruby on Rails

#230

Post by hocuspocus »

cutler wrote: post #118

I dunno. I lived through Internet Explorer, SCO and Linux patent lawsuit days so I reckon it's only a matter of time before Github goes ASP.Net.

A friend at GH was already writing mostly C# and Go before he moved to engineer manager 2+ years ago, so I believe it's already ongoing. Also he absolutely hated having to jump into components in RoR before Codespaces was available internally.
Post reply on HN