It will most likely be fast enough. If not there are libs that will compile your templates to Go code with very minimal overhead, or templating libraries that are much faster than builtin one.
I'd think adding megabytes of JS garbage just to run site would be opposite of "HN clone"
As for "working at scale", this post itself is id ~35 million. You could likely fit all of that into ram on a modestly sized server.
Do you have any references where one could read up on such issues and how to navigate them?
This. A million times this. Please don't be discouraged by any negative responses you get here.
any resources or benchmark numbers to back this claim?
Look at HN for example. Everything is public and they use incrementing ids for posts and comments.
Also, nothing wrong with incremental ids. Twitter and fb are doing just fine.
1. Go has a major bottleneck and that’s the growth of its memory size when it’s under pressure. Templates bloat the memory quickly and make the site less performant at scale (aka if you put it on Heroku, you’d need more Dinos to support the traffic, which costs more.). Instead of GO templating, you can produce static pages and fill them up with JS Ajax or React, or whatever your front end flavor is and make that call a Go API you produce with the framework instead. This also helps you turn your site into an app if needed as well.
2. Saw somewhere you had database incremented user ids and other models? Not safe as it allows any bad actor to peruse your user base. Always do UUID as a scramble that can’t be iterated on.
Keep hammering. For everyone who says you don’t need a framework in Go, there are at least a few newbies who learn how to set up and run their Go server and stack from your framework.