1. Controlled by a single company whose business is surveillance and which has added surveillance "features" (for example it fetches packages from their cache by default)
2. Slower than Java and has GC pauses
3. Promotes non-free software by making distribution of binaries without source easy
4. Its devotees insist on reimplementing things that already have perfectly good implementations
5. Mostly worthless type system that doesn't prevent null pointer accesses
> 2. Slower than java and has GC pauses
Really? I've always read the opposite.
The go GC has improved a lot...
Now the GC pause can take less than 200us (in go 1.5 the same task took 30ms)
Read more about the GC here:
(By the way, I've only looked at the graphs, I should read it too)
@ranfdev Oops, turns out I'm wrong. I didn't realize how much Java had stagnated. Well, scratch that one off the list.
Incremental GC does have a pretty big overhead, though. Low-latency GC overhead can be up to 50%. Which is not a big deal compared to, say, Python's reference counting, but it is compared to Rust without GC. And scanning the heap uses a lot of memory bandwidth, making large heap sizes impractical.
A social network for the 19A0s.