> People wouldn't shut up about how slow it was compared to traditional server-side languages/runtimes which could do multithreading ? There has never not been

> People wouldn't shut up about how slow it was compared to traditional server-side languages/runtimes which could do multithreading ? There has never not been multithreading. And yes, people said it was slow, and they were wrong at the time, having confused single-threaded performance with scalability. > I'd like you to meet my friend, Mr. N-Plus-One Query This is a general problem in all ORMs, it's got nothing to do with Rails and the closest anyone has ever come to solving it is LINQ, which still isn't very close. > Can I point out the libraries that weren't just written specifically to be used within Rails, but actually depended on its heavily-customized initialization and environment preparation? You can, but it doesn't really have anything to do with the point: there are Rails libraries that don't work outside Rails, but Rails is not incompatible with wide swathes of non-Rails libraries. The problem with React is not the quantity of React-only packages, it is that many non-explicitly-React-only packages don't work.