4 ms·
> IO is the same speed for all languages, so it cancels out. That's not true, particularly in concurrent systems. Recent improvements to Go's scheduler (that m
by enneff 14y ago
> IO is the same speed for all languages, so it cancels out.
That's not true, particularly in concurrent systems. Recent improvements to Go's scheduler (that make it more aware of various I/O concerns) have made it 2x faster under some workloads. You don't just optimize the compiler to produce the tightest code, you must also finesse its integration with the rest of the world.
> Not really a common use case.
If you say so.
> I don't think command-line-tools are Go's or Java's niche.
There are a lot of Go command-line tools out there. I think Go is a superb language for this area.
- coldtea 14y ago>>Not really a common use case. >If you say so Why the irony? How many cluster deployments you know where you "spin up instances all the time"??? Compared to general server / network application programming done in both Java and Go it's LESS than a drop in the bucket. If you work somewhere that this does not hold, you could also be an outlier.
- redbad 14y ago> Why the irony? How many cluster deployments you know > where you "spin up instances all the time"??? Any cluster environment whose applications abide 12-Factor semantics stands to benefit greatly from low startup times. This describes both SOA environments like Amazon and Netflix, and PaaS environments like Heroku and [what is enabled by] Docker. http://12factor.net http://12factor.net