Why Go Is Not Good

Re:Why Go Is Not Good by wyager on Sunday June 29, 2014 @08:05PM (#7963013)

>You get out of having to write your own GC

You also don't have the ability to write a GC-less language, because there is no practical way to write non-GCed Go code.

>you can incorporate a few nice concurrency features with little effort

You also can't implement any custom OS-level concurrency features.

[ Parent | on HN ]

Re:Why Go Is Not Good by stcredzero on Sunday June 29, 2014 @11:15PM (#7963517)

You also don't have the ability to write a GC-less language, because there is no practical way to write non-GCed Go code.

True, so you probably don't want to do that.

You also can't implement any custom OS-level concurrency features.

True. But for "journeyman" level language implementation, the toolset is quite good.

[ Parent | on HN ]