rails-i18n VS Ruby on Rails

Note that if you are using rails-i18n, configuration is automatically available for many locales.

And this example of translation for Rails defaults: https://github.com/svenfuchs/rails-i18n/blob/master/rails/locale/en.yml

Also, download ja.yml from rails-i18n and place it in config/locales.

Everything else is set up like site/welcome, but here, we introduce pluralization for countable things. I18n is able to select the appropriate translation based on the variable passed to it. If you see that pluralization is not working well for your locale, it's a good idea to enhance your Rails app with the rails-i18n gem.

rails-i18n

No. That does not contain time only no date i cannot use that without also geting date output also: https://github.com/svenfuchs/rails-i18n/blob/62ffdacdf52e2895715c9d708118bd5ffc320f6a/rails/locale/es-ES.yml. See? This is why I pose question in this reddit.

The origin of this format start Ruby. The i18n-js format is a direct export of translations defined by Ruby on Rails. To export the translations, a Ruby gem can be used, that's completely disconnected from Rails and that can be used for the solely purpose of exporting the translations, even if your project is written in a different language. For JavaScript there's a companion JavaScript package. It comes bundled with all base translations made available by rails-i18n. Base translations allow formatting date, numbers, and sentence connectors, among other things.

The translations are accquired from rails-i18n project -- which is one of the first modules that does things like this.

The Rails Locale Data Repository seems to be the only comprehensive collection of formats but unfortunately I have not seen a single date/time format it uses that is an actual date time format used in the given locale.

The cherry on top was that Comfy gem depended on rails-i18n, which overwrote date I18n translations coming from russian gem, breaking translations on some of the pages. Surely enough, this resulted in another hour or so of debugging and fixing.

[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