page.js
awesome-go-orms
Our great sponsors
| page.js | awesome-go-orms | |
|---|---|---|
| 4 | 4 | |
| 7,665 | 517 | |
| 0.2% | - | |
| 0.0 | 7.7 | |
| 10 months ago | 1 day ago | |
| JavaScript | Go | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
page.js
-
Show HN: React Routing in 120 lines (including comments)
I've used a lot of routers and my favorite is still page.js[1]. It hasn't been updated in years. But it's small, is Express-compatible (i.e. server/client routes can use the same code), and, more importantly, is hackable. I'll never use a router tied to a certain framework again (react, nextjs, etc.) because you trade flexibility for perceived convenience (e.g. using folder structure as route structure, or React component tree as route structure). But it's a terrible trade-off that paints you into a corner later, IMO. Routing can get really niche and site-dependent, so having it fully under your control is worth it.
[1] https://github.com/visionmedia/page.js
-
Dynamic routes using vanilla HTML CSS JS?
Use a simple routing library like pages.js, but in this case I feel it might be overkill.
-
[AskJS] Are there any framework agnostic routing libraries that are well supported?
I've used Page.js for a couple of SPA projects. It was last updated a couple of years ago. The documentation isn't the best, but the client-side router does its job.
-
Building a blog with Svelte: Dynamic imports For Svelte components
We're using onMount to trigger the dynamic import when this component is first rendered. My blog uses page.js as a router, so these dynamic imports are triggered by page transitions, but the logic is the same.
awesome-go-orms
- Go and PostgreSQL
-
Show HN: React Routing in 120 lines (including comments)
> 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
-
Top Go ORMs
I created a PR to add Ent to the list. See https://github.com/d-tsuji/awesome-go-orms/pull/8
What are some alternatives?
director - a tiny and isomorphic URL router for JavaScript
sqlc - Generate type-safe code from SQL
crossroads - JavaScript Routes
react-snippets - A sample of useful snippets in React
pathjs - Simple, lightweight routing for web browsers
universal-router - Universal routing both for backend and frontend
frontexpress - An Express.js-Style router for the front-end
awesome - 😎 Awesome lists about all kinds of interesting topics
navaid - A navigation aid (aka, router) for the browser in 850 bytes~!
go-formatter - A curated list of awesome Go frameworks, libraries and software
SPApp - Single Page Application micro framework. Views, routes and controllers in 60 lines of code
podium - A leaderboard backend using redis