Ruby 2.6 should reach EOL by end of March next year (Ruby always releases around Christmas, the EOL is March 31st 3 years and a bit over 3 months later), so unless Rails 7 releases before then that shouldn't be much of a concern. Given that 6.1 is only a month old and there's usually also a .2 release before a new major version I think this won't affect most people.
This bothered me because I distinctly remember seeing 6.2 in the edge guides. Google still has that indexed, but the article itself now says "6.1 to 7".
I hadn't done Rails since Rails 5. I recently tried installing Rails and created a new project, and it felt like it was way more complicated than it was back then. Biggest of those issues is having Yarn, why cant it just use NPM like a normal person? (even as a fallback)
Well, it’s true that Rails does include JS baked in now, which did not used to be the case. It does make it a bit more complex, I agree. But virtually 100% of projects demand JS on the front end now, so I think it’s wise of them to include a built-in and standardized way to do it.
Discussion (6)
Ruby 2.6 should reach EOL by end of March next year (Ruby always releases around Christmas, the EOL is March 31st 3 years and a bit over 3 months later), so unless Rails 7 releases before then that shouldn't be much of a concern. Given that 6.1 is only a month old and there's usually also a .2 release before a new major version I think this won't affect most people.
They've announced there will be no 6.2, so Rails 7.0 is expected this year.
For everyone else wondering:
github.com/rails/rails/commit/1b45...
This bothered me because I distinctly remember seeing 6.2 in the edge guides. Google still has that indexed, but the article itself now says "6.1 to 7".
Thanks! I somehow missed this.
I hadn't done Rails since Rails 5. I recently tried installing Rails and created a new project, and it felt like it was way more complicated than it was back then. Biggest of those issues is having Yarn, why cant it just use NPM like a normal person? (even as a fallback)
Well, it’s true that Rails does include JS baked in now, which did not used to be the case. It does make it a bit more complex, I agree. But virtually 100% of projects demand JS on the front end now, so I think it’s wise of them to include a built-in and standardized way to do it.