It started out as a take-home assignment for a job I’m interviewing for (they asked for about 10% of what I ended up implementing but I wanted to do/show more :). It’s an aggregator for crypto exchange data.
The app reads the public data stream from exchanges, handles the nitty, gritty details of each exchange’s websocket connections, deals with its quirks, cleans up and normalizes the data into a uniform structure (currently only supporting spot trades) then exposes it downstream as an SSE stream.
Uses Go, Templ, and Mithril.js, and is open source
There’s a great deal of value in the “fullstack meta-frameworks” model of things. For one, using the same language on the backend and frontend is underrated feature.
But Next.js is not the only option on the market, so I partially echo your sentiment, not around React SPA vs React fullstack, but around Next.js vs a half dozen better alternatives for the React ecosystem.
> using the same language on the backend and frontend is underrated feature
I agree, but you can definitely do this without SSR or Next.JS. Common examples are tRPC, Zodios, or even just plain fetch calls with shared type definitions.
The takeaway is that most people don’t think this way. A large portion of online recommendations for auth in Nextjs recommends middlewares for it. Knowing this, you’d expect a faster response time from the people maintaining the framework and stand to lose the most.
I do like your homepage, but my immediate thought was I want to see a specific example without having to read (maybe a photo). I'm assuming youre just proxying information and then showing proper OG tags, so probably good for marketers who have no idea what theyre doing
Yeah that's true, it's targeting marketers. I will try to look into giving examples, maybe show casing two social posts side by side, one before and one after.
> Please don't submit comments complaining that a submission is
> inappropriate for the site. If you think something is spam or offtopic,
> flag it by going to its page and clicking on
> the "flag" link. (Not all users will see this; there is a karma threshold.)
> If you flag something, please don't also comment that you did.
I disagree with you completely about this article not being suitable for HN, but on the other hand, I have to respect this approach to people quoting guidelines.
I certainly found this interesting and implemented the node.js package[1] in a project just now. I found it super easy to use -- much moreso than minimist[2] or commander[3].
I certainly didn't know about it. I had the exact same issue with argparse as the video on the page showed, I always had to look of the documentation to use it or copy and paste it from old scripts to get it to work. This is soo much better, I don't think I'll use argparse again.
The app reads the public data stream from exchanges, handles the nitty, gritty details of each exchange’s websocket connections, deals with its quirks, cleans up and normalizes the data into a uniform structure (currently only supporting spot trades) then exposes it downstream as an SSE stream.
Uses Go, Templ, and Mithril.js, and is open source
Link: https://metra.sh
Github: https://github.com/hadydotai/metra-sh