Why Garbage Collection Paranoia is Still (sometimes) Justified

Re:Why Garbage Collection Paranoia is Still (sometimes) Just... by bunderbunder on Monday November 07, 2011 @10:55AM (#3206702)

Seems like languages which can't or don't want to target JVM or CLR might do well to at least take a cue from Sun and Microsoft, and pool resources. On both those platforms, there are scads of languages all sharing the same GC.

Which leads me to wonder - WTF ever happened to Parrot? I know the project is still alive, but why doesn't anyone seem to be using it?

[ Parent | on HN ]

Re:Why Garbage Collection Paranoia is Still (sometimes) Just... by lucian1900 on Tuesday November 15, 2011 @03:05PM (#3239912)

Sadly, Parrot sucks. It doesn't have a stable bytecode, its assembly is buggy and too high-level, it only recently got a generational (but still m&s stop-the-world) GC and has no useful object system.

I've tried implementing Python3 on it for GSoC and failed.

[ Parent | on HN ]