universal-router VS awesome-go-orms

I use it like that and I am pretty happy with it.

There's one thing, you should redirect all the pages to one single endpoint in server side order to use "pushState". Otherwise it will return 404 when you hit the refresh button. If you don't own a server, you can support routing with hashtag "#" and listen to "onhashchange" event instead of "popstate".

Also, if you would like to support nested and dynamic routes (it's not possible with that code snippet in the github repository since it just checks like `path===currentPath`), you might look at the following solution:

https://github.com/fatih-erikli/universal-router/blob/main/u...

I use that solution in server-side and client-side so it works like Nextjs.

> we'd see the same problem everywhere at the same scale

we do. Every C app implements its own linked list or hash table library. The entire Scheme community is nothing but toy interpreters of various stages of completeness (you can tell a project is serious when they implement call/cc). How many game engines do you think exist? It's a meme that game devs like to spend more time on their pet game engine than actually making their game. How many ORMs do you think exist for ? At least half a dozen. At least. For any given language. Python, Ruby, Go[1]. ORMs, in particular, seem to get created over and over again. Probably because they are trivial to implement and allows one to voice their opinions on SQL abstraction (bike shedding).

[1] https://github.com/d-tsuji/awesome-go-orms

I created a PR to add Ent to the list. See https://github.com/d-tsuji/awesome-go-orms/pull/8