3 ms·
> Wasn't large compilation time driving forces behind writing Go yes, that was one of the tenants. > Is a garbage-collected language not suitable for a web br
by jdc0589 9y ago
> Wasn't large compilation time driving forces behind writing Go
yes, that was one of the tenants.
> Is a garbage-collected language not suitable for a web browser?
In theory its fine; but there's a lot of historical baggage that comes along with garbage collection and the majority of languages that support it (e.g. almost no value types).
Golang fairs pretty well latency wise for a GC'd language. I'd be curious for someone with more experience than me to talk through a deep dive of instances where go's latency/throughput characteristics are and are not good enough for specific applications.
- pjmlp 9y agoWe have Java to blame for it. With the exception of Smalltalk and its derivatives, all the GC enabled languages that came before Java had value types, even Lisp.