4 ms·

I think this is also a function of team size. Suppose you have been given 100,000 developers to work on a website, but it will have millions of customers and t

I think this is also a function of team size. Suppose you have been given 100,000 developers to work on a website, but it will have millions of customers and things cannot fail. Now it is actually useful to be able to parcel out the database layer to a group of 1000, and they can split up each service into groups of 100 etc. There are enough people to decide what conventions, logging, validation people ought to use and perhaps measure them. If all of them hack on the same Rails codebase they might be running into each other all the time. Of course, for a solo developer, it makes sense to use Rails/Django/etc. Now there is a little spot in between 2-99,999. It is possible that there is a team or two at this level. And I think that gear shift or pathway has not yet been discovered. Typically you start on rails, suspect you should switch and then switch way too late. A pathway might look like this: Django -> Django API + VueJs -> Redis + update database? It probably depends on the challenges. If someone has an idea, or something they have tried, it would be interesting to take a look so please share. Edited for clarity.

andjd 5y ago
This is an interesting example of the 80-20 rule (or some variant of it) The vast majority of businesses/projects are small, and will only have one or a small number of developers working on it. So Ruby on Rails (or PHP or Wordpress) is a suitable choice for maybe 80% of projects. At the same time, a very small number of businesses require 100,000+ (or even just 1000+) developers. These businesses, because they have so many developers, employ the vast majority of professional developers. Thus, maybe only 20% of professional developers work on products that are typical of business needs. This disparity explains why communities on Hacker News are typically so negative towards Ruby on Rails. It also explains part of what makes Ruby on Rails so remarkable. Even after all these years, it has a thriving community and has resisted the pull to become more "enterprisy." It's still a tool that is targeted at and well suited for a large swath of business cases, the vast majority of which will likely never need to migrate to something "better".
- jack_riminton 5y ago
  "from HELLO WORLD to IPO" as dhh said today https://twitter.com/dhh/status/1471267036793765888?s=20 https://twitter.com/dhh/status/1471267036793765888?s=20

andjd 5y ago

This is an interesting example of the 80-20 rule (or some variant of it) The vast majority of businesses/projects are small, and will only have one or a small number of developers working on it. So Ruby on Rails (or PHP or Wordpress) is a suitable choice for maybe 80% of projects. At the same time, a very small number of businesses require 100,000+ (or even just 1000+) developers. These businesses, because they have so many developers, employ the vast majority of professional developers. Thus, maybe only 20% of professional developers work on products that are typical of business needs. This disparity explains why communities on Hacker News are typically so negative towards Ruby on Rails. It also explains part of what makes Ruby on Rails so remarkable. Even after all these years, it has a thriving community and has resisted the pull to become more "enterprisy." It's still a tool that is targeted at and well suited for a large swath of business cases, the vast majority of which will likely never need to migrate to something "better".

jack_riminton 5y ago
"from HELLO WORLD to IPO" as dhh said today https://twitter.com/dhh/status/1471267036793765888?s=20 https://twitter.com/dhh/status/1471267036793765888?s=20