"Is Golang Long Enough for Large-Scale Backend Projects?"
Hey folks, been wrestling with this question lately. Golang long seems solid for small to mid-sized stuff, but when it comes to massive backend systems... idk, does it *really* hold up?
Like, the simplicity is great, but sometimes I wonder if it’s *too* simple. Missing generics was a pain (tho they fixed that now), and the ecosystem feels a bit thin compared to, say, Java or Python.
But then again, the performance is killer, and goroutines make concurrency stupid easy. So maybe golang long *is* the move for big projects? Or are we just hyping it up?
What’s y’all’s take? Anyone running golang long in production at scale? Spill the tea.
(also, pls no "just use Rust" replies—we get it, you’re smart lol)
Hey folks, been wrestling with this question lately. Golang long seems solid for small to mid-sized stuff, but when it comes to massive backend systems... idk, does it *really* hold up?
Like, the simplicity is great, but sometimes I wonder if it’s *too* simple. Missing generics was a pain (tho they fixed that now), and the ecosystem feels a bit thin compared to, say, Java or Python.
But then again, the performance is killer, and goroutines make concurrency stupid easy. So maybe golang long *is* the move for big projects? Or are we just hyping it up?
What’s y’all’s take? Anyone running golang long in production at scale? Spill the tea.
(also, pls no "just use Rust" replies—we get it, you’re smart lol)