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

11–20 of 332 posts

Re: Building GitHub with Ruby on Rails

#11

Post by ravloony »

New_California wrote: post #7
holistio wrote: post #2

We are also running on Rails - and loving it, too. However, incorporating this methodology into our workflow would be both a lot of work to set up and also a lot of work to keep running. There certainly is a size threshold under which this is clearly an overkill and we are under that threshold. Yet, if this could be turned into a product, a clean integration, a command I need to run... would definitely use it (and pa…

On the contrary, it is so much easier to upgrade a small app every week or so because you have little to test and probability of breaking changes affecting you is minimal. You should be upgrading all the time since day one, adding necessary infrastructure gradually as your app grows.

Absolutely. I was leading a team a while ago and I instituted this practice to good effect.

Conversely, I was called by a company that I had built an app for previously. They had not upgraded the framework it was built with (Laravel), and ended up offering me consulting days to jump several versions. The irony is that the job ended up being quick and easy to do.

Re: Building GitHub with Ruby on Rails

#12

Post by jstummbillig »

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…

Have a look at AdonisJS.

It's in a somewhat weird spot: On the one hand it is mature and has amazing DX/UX going for it, with a lot of very thoughtful tooling. On the other, for some reason, it has always remained niche with just a couple of core developers, even though it's now nearing version 6 and at least 8 years of releases. I do not know why that is the case. It's a beautifully written full stack framework, taking having inspiration from both Rails and Laravel and in the world of web TS, it should get a lot more attention than it does.

Maybe it's just the weird name :^)

Re: Building GitHub with Ruby on Rails

#13

Post by riffraff »

New_California wrote: post #7
holistio wrote: post #2

We are also running on Rails - and loving it, too. However, incorporating this methodology into our workflow would be both a lot of work to set up and also a lot of work to keep running. There certainly is a size threshold under which this is clearly an overkill and we are under that threshold. Yet, if this could be turned into a product, a clean integration, a command I need to run... would definitely use it (and pa…

On the contrary, it is so much easier to upgrade a small app every week or so because you have little to test and probability of breaking changes affecting you is minimal. You should be upgrading all the time since day one, adding necessary infrastructure gradually as your app grows.

You need to have the right infrastructure/organizational maturity tho.

For example in many organizations partial deployments don't exist and rollback is not easy, so having a "once a quarter we test everything and bump" is less traumatic and expensive than handling minor breakages every week.

You can invest into that infrastructure/maturity but it may not be the best use of your time and money if you don't even know that your company will exist next year.

Re: Building GitHub with Ruby on Rails

#14

Post by jonwinstanley »

ravloony wrote: post #11
New_California wrote: post #7

Earlier quoted context omitted.

On the contrary, it is so much easier to upgrade a small app every week or so because you have little to test and probability of breaking changes affecting you is minimal. You should be upgrading all the time since day one, adding necessary infrastructure gradually as your app grows.

Absolutely. I was leading a team a while ago and I instituted this practice to good effect. Conversely, I was called by a company that I had built an app for previously. They had not upgraded the framework it was built with (Laravel), and ended up offering me consulting days to jump several versions. The irony is that the job ended up being quick and easy to do.

Yes, Laravel does a good job of making upgrades relatively simple

Re: Building GitHub with Ruby on Rails

#19

Post by winrid »

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…

I imagine it wouldn't be too hard, since Django only has one dependency - Django itself (NodeJS developers weep).

Is rails the same way dependency wise?

Re: Building GitHub with Ruby on Rails

#20

Post by cageface »

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…

With the focus on server side rendering Nextjs 13 feels a lot more like Rails too. Other frameworks like Remix & Sveltekit seem to be heading this way too.
Post reply on HN