awesome-go-orms VS wouter

> 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

We're using wouter with great success. It's simple and effective for what we need from a router

If you feel like React Router is a bit too over-engineered and you just need simple routing, you can have a look at https://github.com/molefrog/wouter

I changed over to using wouter instead of react-router, and I love it!

Just to add alternatives. I'm a fan of Wouter its 1/10th in size compared with react-router.

Other options than react-router are also available, like wouter, if you can't use react-router for some specific reason.

Single page just means one index.html is served and then JavaScript takes over to display content. You can use a client side router to simulate pages. There are some to choose from, I can recommend wouter. https://github.com/molefrog/wouter

Routing: At this point you should understand how routing in React works. You can use react-router to enhance it. There is a small library called wouter which you might want to have a look at.