Ultimately, the problem is that by choosing React (and inherently JSX), you’ve unwittingly opted into a confusing nest of build tools, boilerplate, linters, & time-sinks to deal with before you ever get to create anything.
Rails doesn’t scale
“Rails doesn’t scale” is a thing people say, but means very little. It is a buzzword with a popularity that seems to date back to the news that Twitter was moving off of Rails as the central structure for its service in 2011. People took the phrase and ran with it, sometimes to make a quick explanation about a software choice, sometimes to sound smart, and sometimes because it fit the context in which it was said. Ruby on Rails thoroughly did not fit in with what Twitter was doing, for reasons that would seem obvious to experienced developers. But experienced developers also tend to recognize the strengths of the Ruby language and the benefits of the Rails framework. Inexperienced developers and ignorant decision makers have used the buzzword “Rails doesn’t scale” to reach for overly complicated systems that extend the time to first product shipped by months or years for no reason beyond the fear of the “scaling” boogeyman.
The nature of open source software
Open source software is built by humans with varying styles, goals, cultures and spoken languages. The wisdom (and effort) of the crowds approach to software development sometimes seems out of place in a world where lack of reasonable consensus is about as guaranteed as death and taxes. But despite some hardships along the way, great things have come out of it. Open source software powers thousands of companies across the world of varying sizes and provides the glue for much of the usable web as we know it. The side effects of open-source software tend to be exposed and managed over time.
Because of this distributed nature of open source software development, public debates are a critical factor in the health and stability of any project. The health and stability of popular projects is ultimately critical to the long term productivity of software developers. And because stable, economical software development is so critical to global economic strength, it cannot be understated how important these open debates are. But we should recognize when debates are oversimplified and boiled down into chunks that are too easily digested when not properly chewed.
So what do we do?