meanwhile, 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?
Building GitHub with Ruby on Rails
131–140 of 332 posts
Re: Building GitHub with Ruby on Rails
#132Unfortunately I’m fairly certain the message that will be heard is ‘We should totally change something around on the customer every week, that’s what GitHub does’
Re: Building GitHub with Ruby on Rails
#133All the cool kids left Ruby for Go, why are they still in that land?
Since they left ruby (2.0) raw rails performance improved by 75% (3.0) https://www.fastruby.io/blog/assets/images/RRBPerfHistory_72... Then in 3.2, ruby released YJIT which improved median rails response time by about 100% https://raw.githubusercontent.com/easydatawarehousing/ruby_m... It's kind of a golden era for rubyists that stuck it out. Beautiful maintainable code that hits C performance for many tasks.
Really?
Re: Building GitHub with Ruby on Rails
#134Re: Building GitHub with Ruby on Rails
#135GitHub 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 would have expected Microsoft to focus on developer efforts into speeding up Ruby as a language given they are one of a small few large companies that have deep language/compiler expertise.
Re: Building GitHub with Ruby on Rails
#136Earlier 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
As a counterpoint I have yet to see one that is locked in my 15 years working with Rails.
It took Github a full eight years to get caught up after that fateful decision in 2010 to hold off on Rails 3.
Re: Building GitHub with Ruby on Rails
#137Re: Building GitHub with Ruby on Rails
#138Earlier 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.
Re: Building GitHub with Ruby on Rails
#139Are there other languages where the dominant web framework changes so much? Will Rails ever be "done"?
Change is somewhat inevitable though
Re: Building GitHub with Ruby on Rails
#140Are there other languages where the dominant web framework changes so much? Will Rails ever be "done"?