It's debatable. You can have perfectly valid reasons to develop your own framework: - you want to propose something different compared to existing solutions in

It's debatable. You can have perfectly valid reasons to develop your own framework: - you want to propose something different compared to existing solutions in the field, where your vision is clearly incompatible with what already exists - the coding standards for an existing, similar solution is not acceptable, and unlikely to change On the other hand, many a "me-too" piece of software crops up simply because it can be easier to reinvent than to contribute (not implying that RailwaysJS is that). But TFA's point is also that server-side-heavy frameworks are a thing of the past, which is a fair argument.