Yeah, I guess a more accurate headline would say your SPA doesn’t need “a general routing solution” vs “a router”. The only way I can imagine not needing any kind of router whatsoever is to have an app so simple that you only have a single route anyhow.

But what he is really advocating for is doing the work of routing from other aspects of your application: do dependency checks in your controller, do component selection in your view, do path/state marshalling with a focused library, etc.

Maybe all of that is just moving the furniture around and doesn’t net you enough wins to be worth the effort, but it’s an intriguing proposition nonetheless.

I see the life of a software developer as living on a continuum somewhere between Dependency Hell and Not Invented Here syndrome. Some lean towards DH, others toward NIH. Different strokes for different folks. In this article, Stanislav is making the case for a little less DH and a little more NIH.