Sorry but it’s not really an opinion for you to contest it, it’s a well defined guideline of what makes a Show HN post vs a normal link share. If the OP wants to add commentary to their submission they could use “Tell HN” or simply point at the actual blog post and write a comment.
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.
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.
The GP post describes a common problem in _most_ workplaces in the market today. It’s not specific to crypto, AI, or anything in between.