|
|
|
|
|
by bb88
1105 days ago
|
|
There's a bunch of negatives I found. I'll gloss over them here. - New libraries can't just be deployed to the OS, they must be compiled into the project. - A check for thing==nil doesn't always work for all types of nil. Yes nil does not always equal nil. - Panics aren't necessarily a bug. They could be a feature (?). Crashes are always a bug in C. - Garbage collection is mandatory in go. C people are used to managing memory themselves like going for a walk. It's kinda natural. - GC causes hard to debug performance issues. This was true in Java. And it's true in Golang. - Golang channel primitives has bugs of their own with deadlocks and other interesting behaviors, whereas a lot of the threading issues in C are pretty well understood. |
|