Go
Go
Posted Jul 16, 2013 20:09 UTC (Tue) by lsl (guest, #86508)In reply to: Go by juliank
Parent article: The next 20 years of Python
Yes, as the runtime used in gccgo is (mostly) the same. But the issue isn't as bad as people make it sound. I wouldn't worry about it. The GC is constantly improving and even now, with Go 1.1 (in GCC 4.8.1), you shouldn't have any problems outside of some pathological cases
Also note that Go gives you enough control over memory that you can easily work around those cases, should you actually encounter them.