inflection VS Ruby on Rails

> Could you elaborate on this

I think it's more than evaluating each feature in isolation like migrations, ORM, template engine, etc..

As much as I like Python (I use Flask a lot too besides Rails), I always found Rails to include more useful features for building web applications than Django. There's lots of examples but Rails' inflector is one of them. This happens all the time in web apps, which is wanting to output "1 person" or "2 people". Rails give you a template helper for this. Python has options in the form of third party tools like https://github.com/jpvanhal/inflection, but would you rather pull in a third party tool that hasn't been updated in 2+ years or use a solution maintained by a group of folks who are building web apps used by millions of people and then extracted those features into a framework?

The APIs in Rails feel more intuitive to me (super opinion based of course), but it's like someone tried 10 different variants in a few large web apps, tinkered with it for a while, arrived at a solution and that's the one that ships with Rails. There's so much thought put into everything and you know when it's released it's been put through the ringer at Basecamp, Hey, GitHub and Shopify because those sites all run off Rails master. That's a massive amount of confidence that it'll for you too, and the best part is you get to benefit from that on day 1 when a new stable release is shipped.

It's not that Django is bad or unstable but in my opinion if I were looking to use a batteries included framework I wouldn't look anywhere else besides Rails. It's just one of those things where it feels like a really good combination of things all came together (Ruby, Matz, DHH, Basecamp, lots of sites using it, enough community support to find blog posts for tons of stuff, great third party SDK support, etc.). You could say a number of languages have similar traits but they lack the first 4 things which are IMO the most important.

PyHeck is 5-10x faster than the established case conversion library, inflection.

[0] is a my favorite demonstration of it.

[0]: https://github.com/rails/rails/commit/b83965785db1eec019edf1...

Here's a real life example: Imagine a Ruby on Rails app on which a team of developers are working. The code is hosted on GitLab and all the work is coordinated using GitLab issues. In other words: For every commit, there's an associated issue and the issue number acts as a sort of primary key for documentation, time reporting and so forth. This convention has a few advantages, most notably the ability to easily learn more about how, when and by whom features were implemented as well as how this implementation came to be.

Ruby on Rails is regarded as one of the best ruby frameworks. It was the primary language in developing big projects such as Twitter and helped the language boost the community. Often referred to as “Rails,” Ruby on Rails is a web development framework with an MVC control structure and currently running its 6.1 version. The 16-year-old language has dramatically influenced the web development structures and managing databases, web pages, and other components on a web application.

In Rails 7.1, a new option _instance_methods is introduced, allowing developers to opt-out of the automatic generation of instance methods for enums. When enum is defined with _instance_methods: false, Rails will no longer generate methods like pending?, processed?, etc.

Rails isn't super opinionated about database writes, its mostly left up to developers to discover that for relational DBs you do not want to be doing a bunch of small writes all at once.

That said it specifically has tools to address this that started appearing a few years ago https://github.com/rails/rails/pull/35077

The way my team handles it is to stick Kafka in between whats generating the records (for us, a bunch of web scraping workers) and and a consumer that pulls off the Kafka queue and runs an insert when its internal buffer reaches around 50k rows.

Rails is also looking to add some more direct background type work with https://github.com/basecamp/solid_queue but this is still very new - most larger Rails shops are going to be running a second system and a gem called Sidekiq that pulls jobs out of Redis.

I'm looking forward to see what extractions from this will land on rails. For example: https://github.com/rails/rails/issues/50454

Here is what strict_loading does (source):

Kamal is a wonderfully simple way to deploy your applications anywhere. It will also be included by default in Rails 8. Kamal is trivial, but I don’t recommend using it on your development machine.

Here's the GitHub milestone I've based this article on — https://github.com/rails/rails/milestone/87