Building GitHub with Ruby on Rails • Hacker News Board

Re: Building GitHub with Ruby on Rails

#151

Post by shortrounddev » Fri, Apr 07, 2023, 1:41 PM UTC

that_guy_iain wrote: post #91

rimliu wrote: post #83

Earlier quoted context omitted.

JS is not only for frontend anymore. Alas.

Yea and new backend frameworks pop up every day. Wait, they don't. They were clearly talking about frontend frameworks.

I've seen quite a few backend frameworks, but they're usually all based on express

Re: Building GitHub with Ruby on Rails

#152

Post by tyre » Fri, Apr 07, 2023, 1:44 PM UTC

re-thc wrote: post #77

wg0 wrote: post #41

Earlier quoted context omitted.

I have yet to see a tech stack that's not locked up into a framework version. That's more because of our engineering culture. The cost of NOT upgrading outweighs by a huge margin than keeping building on top. And yes, have seen Django shops locked into 0.9x release patched right into the core and running for a very long time, impossible to upgrade and all the horror stories. EDIT: Added Django

> That's more because of our engineering culture. The cost of NOT upgrading outweighs by a huge margin than keeping building on top. The cost of not upgrading is always the worst option. It's just that those making the decisions might not have the same stakes. It has nothing to do with technology and happens in every situation. Often you're just not even aware of what these costs are because you're wired to work arou…

nothing is always.

Consider moving to an SOA. Rather than upgrading a monolith when the engineering team knows that it’ll gradually have pieces pulled out of it, use that effort on the migration.

Re: Building GitHub with Ruby on Rails

#153

Post by shortrounddev » Fri, Apr 07, 2023, 1:45 PM UTC

Alifatisk wrote: post #128

AeroNotix wrote: post #76

Earlier quoted context omitted.

Building for scale from day 0 is a recipe for disaster. You should've seen that coming.

You suggest people should refactor later on when needed?

There comes an inflection point in a startup when you have to move from MVP to scale, and there are two different kinds of tech and two kinds of people for each stage

Re: Building GitHub with Ruby on Rails

#154

Post by nobleach » Fri, Apr 07, 2023, 1:46 PM UTC

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.

I lived through Microsoft purchasing Hotmail and trying repeatedly to migrate it from FreeBSD to IIS/Windows2000. We may have a good 20 years.

Re: Building GitHub with Ruby on Rails

#155

Post by Jarred » Fri, Apr 07, 2023, 1:47 PM UTC

pjmlp wrote: post #59

z3t4 wrote: post #55

Earlier quoted context omitted.

Except for the JS language itself where every proposed suggestion is implemented.

Errr, tail calls.

JavaScriptCore has tail calls

Re: Building GitHub with Ruby on Rails

#156

Post by nomilk » Fri, Apr 07, 2023, 1:49 PM UTC

AlchemistCamp wrote: post #136

wlll wrote: post #58

Earlier quoted context omitted.

As a counterpoint I have yet to see one that is locked in my 15 years working with Rails.

Github itself used to be. They ran a custom fork of Rails 2.3 for years rather than go through the pain of upgrading to Rails 3. By the time they finally did, Rails had already moved on. It took Github a full eight years to get caught up after that fateful decision in 2010 to hold off on Rails 3.

What were the sticking points that made the 2.3 -> 3 upgrade so tough?

Re: Building GitHub with Ruby on Rails

#157

Post by TheRealDunkirk » Fri, Apr 07, 2023, 1:51 PM UTC

I've been using Rails and GitHub since the first 2.x days. I have been expecting an announcement that they are switching to .NET since Microsoft bought them. I'm guessing it's too big of a bite, even for Microsoft, thank Ada. I love being able to point recalcitrant policy makers at my company at GitHub as an example of a top web app -- the context for which they already know very well -- being a Rails monolith.

I'd love to see their Gemfile.

Re: Building GitHub with Ruby on Rails

#158

Post by pjmlp » Fri, Apr 07, 2023, 1:54 PM UTC

Jarred wrote: post #155

pjmlp wrote: post #59

Earlier quoted context omitted.

Errr, tail calls.

JavaScriptCore has tail calls

Nothing that one can rely on for portable code.

Re: Building GitHub with Ruby on Rails

#159

Post by TheRealDunkirk » Fri, Apr 07, 2023, 1:55 PM UTC

MiraiY wrote: post #15

meanwhile, i have to work on a rails 3.2 app with ruby 2.2

This is fine, until someone comes along and asks can we "just" do ? Someone tried to foist a Laravel app on me, to update it with some new functionality. It was so old, I had to setup a Linux box with manually-downloaded versions of PHP and the framework. Not being familiar with Laravel, I needed lots of docs and examples. They were impossible to find, and it turns out Laravel from that long ago doesn't work very much like today's version. You're in luck here, because Rails 3 works pretty much the same way as 6 and 7.

Re: Building GitHub with Ruby on Rails

#160

Post by skeeter2020 » Fri, Apr 07, 2023, 1:59 PM UTC

dagorenouf wrote: post #61

I built my startup 4 years ago with a combination of react + aws + gatsby + hasura. I thought this would be great for performance and scale. Fast forward to today, I spend at least 2x as much time to code a feature than if I had just stuck with a simple rails stack, and the scale I imagined never happened. Now rebuilding everything with rails so I can ship faster and focus on growing the product, not making engineeri…

doubling down on premature optimization and chasing the new hotness with a ground-up rebuild... I hope that works out.