Jade VS Ruby on Rails

If you have a bit of Nodejs SSR background, you would already be accustomed to templating libraries like Pug, Handlebars, EJS, etc. If you’re from a PHP background you would be familiar with the Blade templating engine. These templating libraries basically help you render dynamic data from the backend on the frontend. They also help you generate markup with loops based on conditions.

The right way to start is with HTML and motherfucking web site.

https://motherfuckingwebsite.com/

Really. At this point this is what web sites should strive to be.

Pug is a great way to write HTML by hand. I integrated it with GitHub Pages so pug sources get compiled to HTML and published when commits are pushed. Great experience.

https://pugjs.org/

https://github.com/pugjs/pug

To illustrate the process of migrating from Express to Fastify, we have prepared a demo application. This application utilizes Express, Mongoose, and Pug to create a URL Shortener app as follows:

Disclaimer: The markup of CodePen examples is still in Pug. However, you can view it compiled as HTML by opening the code tab menu and selecting "View compiled HTML" (But, by the way, if you are not already familiar with Pug Templates, I strongly advise you to check them out).

I've been using Pug.js (https://github.com/pugjs/pug) for quite a few projects in the past but when I went to look at it yesterday it looks like it's no longer in active development. Lots of open issues and no response where someone asks what happened.

Hi folks I'm wondering if someone of you is a Django developer who also use pug for templates? Anyone?

I'm sorry about your doggie, but you have the wrong subreddit. The Pug template engine https://pugjs.org/ is discussed here exclusively. Dogs are not discussed here.

The pug support for my projects is the last step for final migration from VSCode to Helix - any suggestions as to what existing language can be used as a basis for adaptation?

[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