meanwhile, i have to work on a rails 3.2 app with ruby 2.2
What's preventing you from upgrading?
the mindset "if it works, leave it there"
edit: also it's a big project without specs, good luck at finding broken stuff...
Building GitHub with Ruby on Rails
81–90 of 332 posts
Re: Building GitHub with Ruby on Rails
#82Another big rails application was twitter, it has been rewritten but the concept fitted well with rails.
Twitter currently uses some java framework as far as I know.
Question, does twitter still have some RoR deployed?
Re: Building GitHub with Ruby on Rails
#83Earlier quoted context omitted.
Exactly, it’s an investment in Rails by tying yourself so closely with it. Contrast to the JS ecosystem where as soon as there’s a disagreement or new idea a new framework is born
Comparing frontend frameworks with backend frameworks seems really odd to me. It takes a lot less time to build a JS framework. They do a lot less. This isn't to say frontend is easier or whatever. But they really do a lot less. That is why they're so many really good frontend frameworks. It's also a lot easier to rewrite your frontend than it is your backend. While backend there is so much to build that you really n…
JS is not only for frontend anymore. Alas.
Re: Building GitHub with Ruby on Rails
#84All the cool kids left Ruby for Go, why are they still in that land?
Re: Building GitHub with Ruby on Rails
#85meanwhile, i have to work on a rails 3.2 app with ruby 2.2
nothing wrong with Rails 3.2 :)
get it on Ruby 3.1 if you can - https://railslts.com
Re: Building GitHub with Ruby on Rails
#86[flagged]
> As someone who has experience working with large codebases, I am thoroughly impressed by GitHub's approach to upgrading their Ruby on Rails monolith. It is clear that the GitHub team has invested a significant amount of time and resources to ensure that their application runs on the latest version of Rails and Ruby, and this has resulted in real tangible benefits such as better database connection handling, faster…
I down voted because it just seems like you wanted to being up the dear GitHub.
It's been years... 7? with great features that go well beyond the letter. Yes gh was stagnant but this is pretty well in the past and your points have almost no current relevance.
Re: Building GitHub with Ruby on Rails
#87meanwhile, i have to work on a rails 3.2 app with ruby 2.2
Those versions are so far removed from receiving any security patches I'd probably want management to sign off that they heard me state this and they take full responsibility if shit hits the fan.
Also, are you at least a little concerned about your career using a tech stack that old?
Re: Building GitHub with Ruby on Rails
#88Earlier quoted context omitted.
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?
Rails has dependencies, but not like node apps; last time I counted create-react-app vs a new rails app, there was nearly 10x as many distinct maintainers with access to push new releases to the default dependency tree. I consider that a better measure of dependency risk than absolute count, since different ecosystems have different ideas about how large a library should be.
Create-react-app isn't really a fair comparison. Create-react-app has ridiculous dependency bloat compared to the norm in the JS ecosystem because it includes every possible option rather than just picking one option in each category. Most serious project using React aren't using create-react-app.
Re: Building GitHub with Ruby on Rails
#89meanwhile, i have to work on a rails 3.2 app with ruby 2.2
Those versions are so far removed from receiving any security patches I'd probably want management to sign off that they heard me state this and they take full responsibility if shit hits the fan. Also, are you at least a little concerned about your career using a tech stack that old?
I work on multiple projects, the main one i work on i recently upgraded from 5.2 rails to 6.1, and ruby 2.7 => 3.0
Re: Building GitHub with Ruby on Rails
#90I 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…
Similar backstory. Back when I used Rails as a young dev I remember loving it but thought it all felt a bit parochial somehow, like they didn’t really get where the web was going. Now I realise they were just not interested in hype and other bullshit, they never get sucked into the latest scalability trends like I always did, they never cared about being first and trendy, and that’s why Rails is still there and still effective. My theory is most other frameworks are unwittingly designed around avoidance - people trying to solve painful things “once and for all” so they don’t ever have to worry about them again, while Rails is more about embracing the uncertainty of the future and being smart and measured about it, like: “Yeah you might need to rethink this part of your setup in a few years to scale it, but there’ll be ways and it’ll be fun; don’t stress about it now, focus on what matters.” And as a more mature engineer I now realise they were so very right with this attitude, and that it results in much better stability and adaptability to new requirements over time. To think, the way I used to think it was a bad reflection on the ecosystem to see popular gems that haven’t been updated for months, while it was a good sign that Node packages were being updated every day… Lol. I think I need to make the jump back to being a Rails dev.