[ativzzz]

as a rails dev, if I were to start a new project today I would still pick rails. It makes building web apps a breeze. The technology is mature, stable, active and still staying modern in terms of integration with modern JS

you start running into problems as you scale, but the reality is you will run into scaling problems regardless of what technology you use, and the ability to move quickly and iterate is much more important for new projects than solving scaling problems before they exist

[germandiago]

This is the reason why I will pick Django for my next web: iteration time > scaling problems especially at the beginning. Same for Rails.

[DeathArrow]

>as a rails dev, if I were to start a new project today I would still pick rails. It makes building web apps a breeze.

It's also a breeze if you use .NET and it will run circles around the Ruby app.

[ativzzz]

haha but then I have to learn the entire .NET / windows ecosystem which is a huge jump considering i've only ever developed on mac/linux. I am using wsl now though

and running circles won't matter because for most web apps the DB is usually the bottleneck anyway

[DeathArrow]

But you can use .NET on both Linux and Mac. As for DB being the limit, usually that's only the case for simple CRUD apps. In microservices and high load apps, performance matters.

.NET is just one example. It could be Go or Java.

[ativzzz]

microservices start being useful when your monolith becomes too large for your engineering department to work on simultaneously. If you force good engineering practices and quality code reviews, you can scale this up to at least 100 devs. Microservices are more about Conway's law

high load apps I agree with, pick the technology that is appropriate, but again, for new projects I would say any technology that gives you speed of development (like rails) is far far far superior to speed of the technology.