Hacker News new | past | comments | ask | show | jobs | submit login
Rails 6.0 (rubyonrails.org)
594 points by vipulam on Aug 16, 2019 | hide | past | favorite | 169 comments

Congrats to the Rails team! With this new major release, I’m planning to update the Ruby on Rails Tutorial accordingly. See here for details:


You can join the Learn Enough/Rails Tutorial email list to receive a notification when it’s ready:


I work as a senior engineer at a FAANG and this whole road started with The Rails Tutorial. It isn’t hyperbole to say that Mike Hartl changes lives. Him and the old RailsCasts dude deserve to be in the Rails Hall of Fame.

Thank you Michael! I will forever be grateful for your work on Rails Tutorial, it started me on my path to becoming a developer and the Learn Enough series has been super awesome.

Thank you so much for your work! I owe a lot of my initial success in getting into the industry and setting up my career to your book!

Great, glad to hear it!

Add me to the long, long, long, long list of people living a better life because of your tutorials. Thanks.

Really, really happy to hear this. The Hartl tutorial is my gold standard. Props.

I also am a senior engineer now because of this tutorial :) I'd taken a mess of CS courses in college but had never done professional web development.

Along with many, many other things, this tutorial taught me the basics of TDD, which for me was the big unlock, keeping me out of the debugger for every little thing.

Many thanks, Michael.

You’re very welcome! I’m always so happy to hear success stories like this.

That is indeed a fabulous tutorial.

Cool! After a hiatus from Rails, I threw together an internal tool this week with 6.0.0.rc2 - breath of fresh air in a world of microservices and complex architectures.

Good job rails team!


Edit: P.S. - Thanks rails community too! Was super simple to build thanks to the vibrant community...

- Corporate SSO via devise + omniauth

- CSV uploads (activerecord-import gem)

- pagination (will_paginate gem)

- external API integration

- DB seeding

- audit logging on edited/created data (audited gem)

- wizards (wicked gem)

- etc, etc.

Conventions in rails are so strong, that I quite possibly know how to seed and migrate your database, can integrate additional omniauth providers and know how to pull audit data even without looking at your code.

100%. I can walk into most new jobs and be productive right away

on a whim...do you know of any good guides for integrating an external API? i'm new to rails and working on a rails project that needs to communicate with a third party api -- there are a lot of messy guides, particularly for oauth

If I was starting out fresh, I'd probably try and check out some of the guides that services like stripe and github have for interacting with their own api's if you'd like some real world experience.

Here some links:

- https://github.com/octokit/octokit.rb

- https://github.com/stripe/stripe-ruby

Depending on how you set up your app, you should look into organizing your external services like this: https://www.engineyard.com/blog/keeping-your-rails-controlle...

I think the pattern of making generic classes that leverage the httparty gem is solid. Depending on your preference have another layer of classes between that and your models. Or have the apis called directly from models or controllers

I don't know of a library for external API integration (so I'll be watching this space), but for OAuth specifically, Omniauth has been invaluable. It supports a lot of various strategies [0] which is what it called various OAuth2 implementations.

0: https://github.com/omniauth/omniauth/wiki/List-of-Strategies

I've been working with Rails for several years. First, it was fullstack rails, then we got a giant mess of jquery, tried to solve it by moving to an SPA with Vue... and since then our productivity really dropped.

While Vue works, I miss the productivity of having a single server app to maintain, instead of two. I'm considering moving back to Rails only, with the aid of some library like Unpoly for the nice ajax unobtrusive javascript helpers.

Congrats on the release, and thanks for helping to keep alive the model of server-rendered apps, while everyone else appears to be moving to SPAs.

You might find Rails + Turbolinks + Stimulus to be relatively headache-free.

There's nothing wrong with some good ol server side template rendering. Non trivial pages will take longer to render though.

How is that possible if you're comparing the same data loaded on the client vs the server? Server has a faster Internet connection and connects to the DB directly (not over HTTP).

Sure, clients load "faster" if you mean they don't actually load everything. Apples to oranges.

If a page needs to make 5 DB queries to present a bunch of data, those 5 DB queries will be faster on the server than from the browser. So will parsing the response and transforming it into HTML.

If you're creating a desktop application in the browser, a SPA is the way to go or the experience will be nightmarish for both users and developers. For anything else a classical server rendered web app is OK. Example: Amazon is not a SPA.

You can do the first render without loading everything from the DB, then load your more expensive data while the page is loading.

Or do infinite scrolling and only load 10 rows from the DB, where you would have to render more rows to be usable if you didn't have infinite scrolling.

Congrats on shipping!!!

Been doing Rails for the past year coming from a C# and ColdFusion background. God I love what you can accomplish in a short amount of time with Rails.

ColdFusion became a nightmare since there is NOTHING for it any more.

C#, though awesome, is just too verbose.

Rails and Ruby are a God send.

I'm a long term ColdFusion developer (since 1999) - about 5 years ago we (the company I work for; I have autonomy to choose the stack and tools) switched to Rails (from CF) for the ecosystem.

and never looked back i presume ;)

We still support old code we haven't rewritten, occasionally adding some features, but generally speaking, no, we haven't looked back. The core of our business logic (a lot of background processing) has long since moved from a hand-rolled CFML approach to Sidekiq. The eventual goal is to retire CFML completely.

That's our goal also. We just ported a site over to WordPress with a Rails admin backend. We're hoping to move off of ColdFusion completely by next year.

Just curious: how does WordPress with Rails admin work? What was lacking in the WordPress dashboard that required a Rails app as well?

Though you can do ALOT with Wordpress and Woocommerce, the Wordpress "framework" just feels icky. Not to mention that WordPress is a beast and can slow down considerably with only a few people in the admin area.

That said we use a Rails admin backend to mange all aspects of the stock and categories. We sync up to Woocommerce with the API and ActiveJob.

This really isn't anything ground breaking, it's using the right tools for the right areas to bring things together.

The clients LOVE it.

Thanks for elaborating — that does sound like a good compromise that would be easy for someone/a team familiar with both Rails and the WordPress JSON API to set up.

I’m considering learning rails for a new project. Also coming from a .NET background. Any good resources you can recommend?

OMG! Railscasts got me through so much in the early days. I didn't realize that they were on YouTube. Nice!

This is the defacto learning guide https://www.railstutorial.org/, although not currently updated for Rails 6.

Oh I totally missed his reply in this thread https://news.ycombinator.com/item?id=20718729 (currently at the top)

I switched from .NET to rails. agree with the other comments about rails tutorial. It is excellent but don’t forget the rails guides (guides.rubyonrails.org).

If you already understand MVC (for example if you’ve worked with .NET’s MVC offering) reading rails guides will serve you very well.

> I’m considering learning rails for a new project. Also coming from a .NET background. Any good resources you can recommend?

Yes, learn anything else other than Rails or Ruby. It was never good, just well promoted. I haven't checked on it recently, and I'm sure there are improvements, but there are so many better options today (e.g., .NET, Python, Node), it's hard to see a good reason to take up Ruby or Rails.

I think I have a good enough reason. I’d like to pursue a remote job as a backend engineer. Most interesting job listings are for rails or go. I’m not particularly fond of go, so I’m trying out rails. Who knows - maybe I’ll hate it.

I also recommend the Rails Tutorial; it covers a lot in a short amount of time.

Rails has been the joy of my web developer life for the past five years. Went through native development, SPAs, etc. – and happily came back to Rails in the end. The productivity of it is just fantastic.

Congrats for shipping, and to many good years to come!

Started a new project with Rails 6.0.0.rc2 the other day. Great experience, up and running quickly and enjoyed all the new little touches (object allocations in the logs is great). The multi database[1] thing is also great to have built in - the new app has an analytics database and a web app database that it needs to query, so it is great to be able to use the new functionality for that!

[1] https://edgeguides.rubyonrails.org/active_record_multiple_da...

Apparently reports of Rails' death are greatly exaggerated.

Say what you will about performance, but Rails continues to be the most productive framework for building a database backed web application or (non-trivial) REST API. It's secure by default, includes optional peripherals (ActiveJob, ActiveStorage, ActiveMailbox, etc.) to handle most common tasks and has excellent documentation.

Congrats to the Rails team on this release and for continuing to plug away after all these years.

Rails just became boring technology. It works. The hype is gone, but it continues chugging along happily and is generally an understood problem.

I think you mean mature.

Well, yes. Mature, boring technology. I meant it in the sense of this essay[1].

[1] https://mcfunley.com/choose-boring-technology

And the presentation at http://boringtechnology.club/

I hated on Rails forever. It has its flaws for sure. And granted, I now have 5 years of experience with it, but there is nothing that compares to it for whipping something together quickly.

Don't get me wrong, Python is a great language. And Django is a great framework. There's lots of good languages and Frameworks.

But Rails has the right magic of incredibly stable tooling, a huge community, and tons of documentation & guides written for beginners. It definitely has a unique (and valuable) place in the world / businesses.

Has it ever been accused of being dead as a project? Falling out of favor for new projects, sure, but a new major release doesn't counter that.

What?! Rails has been announced as dead at the release of almost every new MVC framework. The last major proclamation was when Phoenix was the new hotness.

Search for "rails dead" and you'll find a whole genre of Rails eulogies ... and denials that it needs one.

All of the ones I’ve seen have been “dead” in the sense of “there is some new hotness that has replaced it for new projects” not “no one is still maintaining Rails”.

A new release contradicts the latter, not the former.

If dead means not the new hotness, then yes, Rails is dead. If it means the project has stopped releasing major features and improving the code base top to bottom, it isn't.

Rails: still dead after 15 years.

Will it ever hit critical mass?

Eh, no. The whole MVC pattern is obsolete and every web project I've worked on less than 5 years old is a SPA. It's gone the way of PHP. It will always be around in legacy stuff but hardly anyone is building new project with it.

What are you using for the backend? A SPA has no value without one. Unless you're using something like Firebase, pretty good chance your backend is an MVC app. (I think you're confusing server-rendered apps with the MVC pattern)

If you're using graphql for the backend, is it still MVC?

Even if you can stretch the definition to fit, is it still useful to organize your code along those terms instead of what's natural in the new ecosystem? (data source resolvers, type schemas, queries/mutations)

Depends on what you're building the API in. GraphQL is a specification, not a language. For example, you can build a GraphQL API using Rails.

Eh I guess I meant "traditional" web MVC where HTML template for the whole page is pre-rendered on the server.

We use gRPC web, so backend is a bunch of RPC endpoints. Front end is regular SPA.

This has worked great for us because it reduces backend to "shipping objects" instead of all the bs you normally have to deal with in HTTP.

With gRPC there's no use for rails, or any HTTP server framework. As far as I can tell, this is the future of web endpoints, so rails will die out.

> rails will die out

That'll suck. Hope your company doesn't use Github.

Amazon still runs a bunch of Perl in the back. Just because you're stuck with some design choice doesn't mean that framework has a solid future. People still write plenty of COBOL but you don't see any new applications using it

Plenty of new mainframe code is written in corporate settings. Legacy modernization is strong as ever and for some companies that doesn’t mean moving off mainframe - it means upgrading, cleaning up and cloning legacy COBOL code bases and some times writing new.

Pretty sure Rails is just adapting so that the V in the MVC is the SPA.

I'm convinced RPC frameworks are the future of REST. It's too crufty without them. Most of the rails stack just isn't involved in those calls, so there's not much purpose using it.

MVC is way bigger than "server-rendered websites". It applies to anything with an interface - native apps, SPAs. Arguably even services that don't have GUIs. It's a method of separating concerns that has remained remarkably popular through many different technology cycles. You're saying a lot of words but I don't think you know what they mean.

Right on. My concept of MVC just helps guide me on how I’m going to go about building some particular web functionality, irregardless of whether or not the end result is more or less SPA in nature or not. Some parts of my app are nearly completely Ajax driven and server side rendered, other parts are just static web pages. The model means, what classes or methods do I need to build to store the data/state. The view means how am I going to present the to the client side, with a mix of html/template engine working with a backend view class/methods. The controller is how am I going to network the model with the view, and that is generally with forms and other supporting logic. The level of people on this thread that are talking very confidently about things with which they are clearly novices, is pretty shocking. I haven’t seen such a thread on HN in a long time. I’m a python guy using Flask, but congrats to the Rails users and thanks to the developers for continuing to drive it! You’ve made the web a better place.

Irregardless isn’t a word. :)

Assuming your API follows REST, I find the MVC pattern to be immensely helpful. Even if the "V" part is just an object serializer, it's still a great pattern.

And this is why every website now has a loading screen in front of it.

That's stupid implementation. You can _easily_ build static websites that load near instantly and are tiny. Also if you choose to shut off javascript that's your choice, but don't complain the web does not work.

If nearly every implementation of a technology is broken, I wouldn't blame the implementors. I would blame the technology.

Hell, Facebook basically invented reactive Javascript and they still have loading bars everywhere, broken content sections, and requires a full reload every now and again to get content to show. Reddit is even worse. Those are two major implementations of SPAs and they're both horribly broken.

It's nothing to do with if Javascript is enabled in your browser. If Facebook and Reddit, two of the most popular sites on the Internet, can't get SPA right, I'm blaming the technology.

MVC has been around since the 70s and is one of the most formative design patterns. Hardly obsolete.

You can very easily eschew the V and run your spa against a Rails API.

Strictly speaking, the V is still there. The View doesn't have to render HTML; it's still there, rendering JSON, in a Rails API.

You can even build an SPA using the MVC pattern. I think nullwasamistake's comment was misusing buzzwords, and they were rather comparing server-rendered apps vs client-side SPAs.

I think one of Rails' biggest strengths is:

> In fact, GitHub, Shopify, and Basecamp, as well as plenty of other companies and applications, have been running the pre-release version of Rails 6 for months and months in production.

Test suites are nice and all but nothing beats having tons of real world production workloads thrown at something to really test it and iron out a good developer API. There's just a massive amount of confidence you have that you won't be the one having to pioneer some weird edge case bug.

Can someone list at least 1 other popular web framework that has multiple individual sites pushing billions of page views through it before it hits a stable release?

I would not be surprise if there was a PHP framework that rivals that in page view. But I don't think there will be any other framework that gives as much confidence to developers as Github and Shopify.

I think Cookpad wants to test Rails Pre-Release in the future as well, that is a site possibly bigger than Github. I wonder if Apple Music is still on Rails.

Yeah, when I think Shopify, I think mission critical SAAS app where your customers have customers and there's tons of payment transactions happening. Reliability is of the upmost importance while running at massive scale.

There's just a huge amount of goodness in being able to piggy back off a bunch of sites' engineering teams to ensure by the time you use a release, it's been through so much testing.

I really never got that feeling from any other framework. I wish Phoenix had more success stories like that.

Symfony. Last i heard, pornhub ir youporn was using it and their traffic dwarfs most other sites.

Probably WordPress.

Maybe I'm nitpicking but WordPress is a CMS and not a generic web framework.

He said billions, not trillions ;-)

Not multiple sites perhaps, but Facebook uses React's unstable versions on production.

Very exciting. While in medical school, I taught myself a decent amount of Ruby and learned the Rails framework due to an old mentor of mine.

The same app that I learned with is now a full fledged startup, with thousands of future doctors using it, and one of our DB tables has nearly 1m objects.

Kudos to the rails team, really. I know a lot of titles and headlines talk about "is Rails dead?" and this should put it to rest. It might not be the most cutting edge technology, but it's proven.

Is this passmed, by any chance?

The multiple database support is really exciting. Anything that makes it easier to push database reads to replicas is huge!

The cool thing about multi-database feature that's coming to Rails is setting like

>config.active_record.database_selector = 2.seconds

Rails provides a way to make sure that at-least for first two seconds after the write operation, read requests are handled by the write instance. This assumes that your read replica will get updated within 2 seconds with the live data.

How cool is that

How does that work though? If you have multiple instances that are serving the same traffic, how do one know about the change made by the other? Is it a global timer? i.e. any write affects reads, or it knows and only works on the same table?

Why not keep dependent operations within the same transaction? If that would be done by rails from the start then I could just easily split read/write through pgpool.

It is read-your-writes semantics, and the metadata is stored in the session.

We've been doing this for years on a Rails 3 app. We yield from a `slave` method, with the connection pointing to the replica DB until yield returns. It's just a short method. It's great if Rails now supports this directly, but a shame if people have been waiting for it.

Ditto, though we started this behavior in Rails 3 or 4, I no longer recall, and are now on 5.2.X.

For people who are making the switch from Rails 5 to 6, or transitioning from Sprockets to Webpacker, I strongly urge you to bookmark what I consider to be the missing manual for everything that falls through the cracks:


My only complaint with v6 is that we didn't take the opportunity to make a clean break from the Asset Pipeline. I know that there are gems that would break etc. Luckily, the process moving CSS to Webpacker is made easy via this document.


If you're using Sass, make sure you switch from sass-rails to sassc-rails.

Stimulus is an awesome solution for your JS needs. Don't even think about React again until you've at least considered the power of a well-cached backend fronted by a Stimulus + Turbolinks solution.

Try to get an early handle on the multiple ways that import can be used in your JS files. There are three different forms and they all have subtleties that can bite you:

import 'library'

import { x, y, z } from 'library'

import * as Library from 'library'

If your JS has require() directives, convert them to import directives. import is the future.

Finally, don't ever let anyone shame you out of using jQuery. jQuery rocks and is an incredibly powerful tool that still brings superpowers to the table. Anyone who suggests it's simply "bad" is not bringing good arguments to the table. (But when things get hairy, take a good look at Stimulus!)

Finally!! Let's have a party! \o/

A lot of web apps in Debian are depending on Ruby on Rails 5. Right now, I'm making their transition for 6.0.0 with its RC1 [1]. So glad to meet its stable release now.

[1] https://wiki.debian.org/Teams/Ruby/Rails6

Rails 6 coupled with a starter template like Jumpstart Pro, and you can literally have a complete MVP SAAS app up running (payment support, team support), within a few hours.

Rails continues to win in the productivity category.

Love the parallel testing thing. I wonder if it’s already working with Rspec.

They mentioned in the PR that it seems like an adapter for rspec/cucumber needs to be added for that to work out--I, too, am hoping that such a thing comes to fruition.

Would someone more familiar with Ruby mind explaining what Zeitwerk is/does? I think I have a vague idea, but both the announcement post linked to from this one and the project's README assume a lot of prior knowledge about the use case.

Sure, I can try! One part of the Rails "magic" that the framework tries to abstract away from an app developer is code loading. So, instead of each file in your app needing to explicitly specify using "require" statements which other files it needs to run, Rails uses Ruby to automatically "require" files for you. This system is dependent on constant names and namespaces matching file names and directory structures. So, a constant (Rails model) like "Sports::Player" used in a controller might be found via lookup automatically in "app/models/sports/player.rb".

A system which does this has been a part of Rails for a _very_ long time, and Zietwerk is an upgrade to it by a longtime Rails contributor that fixes some of the previous downsides and gotchas.

Oh, so it's similar to PHP's autoloading based on psr4.

Sure, I'll give it a shot.

Ruby classes usually need to explicitly require the other classes and modules which they use. Rails implemented a different way to achieve requiring dependencies using a method called "const_missing" which requires the missing dependent when it is not found in the known constant list.

The problem with this is that if your classes and modules do not adhere to a strict arrangement within your source code directories then Rails can sometimes not find the file you are looking for, or worse find the wrong file.

Since "require" has an effect on the loaded constant namespace, the order of requiring dependencies can make a difference in the presence of bugs related to which code has been required.

There's more information here: https://github.com/fxn/zeitwerk#motivation

Congrats to the Rails team ! I can't praise Rails enough. Such a huge boost in productivity for prototyping or full production app. I use it for both work or side project. I can't imagine a world without it. Long live Rails !

Great news, and a hearty congrats and thank you to all the contributors!

As a frontend designer, I'd been hoping for some mention of faster SASS/SCSS compiling, but it looks like it's the same asset pipeline for that. Can anyone recommend a current resource for decreasing compile times?

I love designing in a Rails app, but my non-Rails projects all seem to inject CSS changes into the browser almost instantaneously, whereas with Rails there's often a wait of up to 10 seconds. The lag is pretty disruptive to the design workflow. I'm pretty new to Rails so any tips on what I might be doing wrong would be appreciated :)

Definitely switch over to sassc-rails, which should give you a massive speed boost.

I also run an instance of bin/webpack-dev-server which handles all of my dev-time Sass pushing needs.

One thing I'm a little sad about is the decision to continue using sprockets (aka Asset Pipeline) for CSS and images. My understanding is that a lot of gems would break if they changed but I can't help feel an opportunity was lost to bite the bullet and do the big switch all at once. I guarantee you that it's coming.

Luckily, I can say that switching to using Webpack for CSS is very doable. The best instructions are here: https://gist.github.com/andyyou/834e82f5723fec9d2dc021fb7b81...

Use Webpack for SCSS (and if necessary enable PostCSS, though I am pretty sure Rails' Webpack config supports SCSS by default) and enable livereload, the problem will fix itself.

Awesome, thanks for the tip.

sassc-rails is helpful since it binds to libsass.

Framework that works. If you are building a business - use it. If you are into developers masturbation - use something that was released a month ago and got lots of GitHub stars/HN upvotes.

Congrats. Unfortunately my favourite PR [1] Model error as object didn't make it into Rails 6, but it will be in Rails 6.1

Active Storage still needs work [2], ( I really wish paperclip had stayed a little longer ), but the update should really be good enough for general purpose usage.

And hopefully someday Action Cable would really work without switching over to Any Cable, the latency are way too high.

And I heard Stimulus 2.0 [3] is coming too.

And with Github and Shopify taking more hands on approach in development, Rail's future is brighter than ever.

[1] https://github.com/rails/rails/pull/32313

[2] https://github.com/rails/rails/issues/31419

[3] https://github.com/stimulusjs/stimulus/pull/202

Thrilled about this. Haven't written rails in a few years because I've mostly been backend at a FAANG co, but if I had to build a small-medium size site again I'd go back in a heartbeat.

Support for multiple databases? Django added that 9 years back!? - https://django.readthedocs.io/en/1.4.X/releases/1.2.html#sup...

Are they both talking about the same thing, or I am missing something?

It's a lot more than talking to pg and mysql at the same time, thankfully!


In short, to do this feature family properly and in an opinionated, predictable way means that you have to cover a number of non-trivial cases. Multiple primaries and their replicas is just the beginning:

- automatic connection switching on a per-model basis

- Automatic swapping between the primary and replica depending on the HTTP verb and recent writes

- Rails tasks for creating, dropping, migrating, and interacting with the multiple databases

Sharding, cross-cluster joins and load balancing replicas are coming soon.

I think what's important here is that every site over a certain scale previously needed to implement their own take on this, and there were a lot of thorny edge cases, race conditions and heisenbugs to do so. It's kind of like the old chestnut that if you find yourself writing original crypto code, you're probably doing it very wrong.

The fact that any project can uncomment a few lines and get all of this for free is properly awesome.

Thanks to the Rails team for a great release! I'm enjoying the stimulus js framework to handle client side UI behavior.

Glad to hear this. This sound so good. I started to update my book about building an API with Rails 6 [1]. I hope to finish it this week-end.

Thank to all Rails community to build this exciting project

[1]: https://github.com/madeindjs/api_on_rails

Finally made it! Congratulations!

Zawinski's Law “Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can.”

--- Action Mailbox routes incoming emails to controller-like mailboxes for processing in Rails. It ships with ingresses for Amazon SES, Mailgun, Mandrill, Postmark, and SendGrid. You can also handle inbound mails directly via the built-in Exim, Postfix, and Qmail ingresses. The foundational work on Action Mailbox was done by George Claghorn and yours truly.

Funny, I first saw this law mentioned yesterday in a discussion about a new PHP Laravel package for handling incoming mail.

Once you hear about Baader-Meinhof effect, you see Baader-Meinhof effect everywhere.

Rails and Laravel have many things in common. In some cases one is ahead of the other one.

Hah! And with not a lot of code and an ActionText integration, you can write some nice looking emails too!

I can build my own Gmail in an hour!

What is the lightest weight, best practice / pattern for using rails, not django/flask, to call python-based programs (e.g. python machine learning inference such as tensorflow/pytorch, or other scientific computing like scikit or numpy) on a lean server (keeping costs down)?

I would probably write a flask wrapper and expose an api to the Rails app. I’ve seen this done successfully at scale in a large Rails app.

I think Node.js is the better choice for this than Rails. You want your Python number-crunching API accessed async leaving Node to take care of auth, logging and database reads. With your Python API returning JSON I would imagine Rails serialisation would slow down performance relative to Node.

Nothing beats Rails for slinging out a website or interactive "web app" in a week.

It's christmas eve already?

I think you are confusing Ruby (the language) with Ruby on Rails (the framework).

Ruby - the language - is the one released usually on Christmas.

I love rails, but I found the wild that the metaprogramming can make things far more complex and unintuitive than they need to be.

Has anyone else thought the same?

Any tools to work around this?

Wow, Multiple DB and Parallel Testing is super productive.

I hope framework maintainers of other language community should also get inspired by these features.

Exciting! I've been a rails developer for the past 5 years, hoping to hold onto it for as long as possible!

I’ve been using Rails since 1.2, and somehow it has never lost it’s magicalness for me. These days I might eventually end up using something different to build a production app, but Rails is always still the first tool I reach for. It is absolutely incredible to me how much value DHH and the core team have created with it. I’ve got a new project starting Monday, so this is great timing! Thanks to all the Rails contributors that made this happen!

I haven't used Rails since 5.0 came out. Might be time to take a look at it again.

Very cool! Congratulations!

I was happy to se new Rails notification from newreleases.io today.

How does it compare to Elixir/Phoenix?

Congrat, so excited to test it.


What is the fastest web server for Rails today? I've always wanted to run something serious with Rails, but the performance always puts me off.

Do you plan to run something more serious than github, basecamp or shopify? Usually it is not rails, which is the bottleneck, but the architecture of your application.

As a matter of fact, yes. Not as big as GitHub, but bigger than Shopify. So the choice of application server matters, as well as how easy it is to scale and provision that server.

Shopify has 800,000 customers, 4,000+ employees, and handles over $40,000,000,000 per year. And you're building something from scratch, starting today, that is going to be bigger than Shopify in a fast enough timeframe that your Rails server today is the biggest concern?

"Bigger than a shopify website" is a possible interpretation.

Something doesn’t add up: You have have a high profile project that is bigger than Shopify (!) but you ask a question that seems like the first question you should type into google to research this if you were interested.

Any server is fast enough. If your web app is literally doing anything other than rendering empty pages the time a request spends in the web server will be an insignificant fraction of your total response time.

Puma is definitely the fastest or one of the fastest. It's also the default in Rails now. https://github.com/puma/puma

I don't know if it's the fastest, but I've had good success using Puma with Ruby on Rails in a real-world production site. That said, if performance is your goal, then the web server is only a small part of it. In my experience, the way to get a high-performing Ruby on Rails application is primarily through fragment caching and using a CDN. You can get excellent performance with very little effort that way.

You should probably ask Github, they run their main site on Rails.

Wow, got down voted for asking a question on which web application server I should use with Rails today. Really?

Because people are tired of hearing "Rails is so slow". It's been a dead horse for 10 years now, in 2019 it just feels like you're trolling.

Ah, great, all the features we don't need, but would have to upgrade to anyway.

Applications are open for YC Winter 2023

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact