On: What Python developers need to know before migrating to Go

[liveoneggs]

I keep looking for IEEE or ISO spec for Go and not finding it. I keep looking for alternative compilers and can't find any.

Is there a defined standard library that you can count on for the next decade?

Maybe in 15 years when Go has outgrown its lock-in it may be worth considering. At this point signing on with google is like playing russian roulette.

[jlgreco → liveoneggs]

> I keep looking for alternative compilers and can't find any.

Really??? How long did you look?

I call bullshit; you did not look. GCC is an alternative compiler. Go away troll.

[liveoneggs → jlgreco]

gccgo is still from the same google-owned go project.

I'll gladly go away, fanboy.

[jlgreco → liveoneggs]

It is a first class member of GCC, under the GNU project. There are no possible concerns. I challenge you to attempt to articulate even one. No vague "google pulls the plug" statements, articulate a specific concern. Try it. You idiot crybabies, seemingly primarily people who got butthurt at having their hosted RSS reader pulled out from under them, never can.

You are either a troll or an idiot. Actually, I'm leaning towards both.

[cmccabe → liveoneggs]

gcc is owned by Google? Someone should tell the gcc folks and Richard Stallman that.