On 2020-02-12 13:23, Henrik Johansson wrote: > We shouldn't pretend that GC is be all end all to both developer and runtime > performance.
Frankly I think performance has a lot to answer for and likely why a secure C that drops features and/or performance, has never become mainstream. A default of slow with unsafe like go has would be nice in the embedded world. After all hw acceleration or assembly often replaces C where performance is required. As far as GO is concerned, for it's intended use cases. OOM avoidance rather than performance is the concern, if anything. You can always throw more hardware at performance and it already performs many times faster than python etc.. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/ae75de21-abaf-919d-e100-68b9d6135cc6%40gmail.com.
