Linked by Thom Holwerda on Mon 11th Feb 2013 22:59 UTC
General Development "I feel like writing about the Go programming language (or 'Golang') today, so instead today's topic is computer stuff. For the record, the language I've programmed the most in has been Python, so that’s the perspective I'm analyzing it from." Some good and bad things about Go.
Permalink for comment 552237
To read all comments associated with this story, please click here.
RE[4]: Cross-compiling
by Laurence on Tue 12th Feb 2013 18:35 UTC in reply to "RE[3]: Cross-compiling"
Member since:

I actually agree with moondevil's point. While the c++ ecosystem is filled with tons of incompatible libraries/frameworks across tons of platforms, the c++ language itself doesn't impose significant portability issues, in fact it's highly portable. I think you ought to be blaming the C++ frameworks for portability issues rather than the C++ language itself.

I appreciate what you're saying, but these days frameworks are as integral part of the language as the language itself. eg what would be the point of C# if it wasn't for .NET? Or Java if it wasn't for JRE? Or even Python if it wasn't for it's modules?

I genuinely do like C++ - I'm not trying to argue that one language is a "better" language than the other. But it is fair to say that because of the core frameworks and because of the Go compiler, Go is an easier language to port.

Now in the end this difference may be mute because we really do need the C++ frameworks in practice, but I think it's important to recognize because without a central authority for coordination of one common framework, all languages have the potential to devolve into the situation C++ finds itself in with incompatible local frameworks. I can see it now: "microsoft foundation classes for Go", haha.

That's a very interesting point. We do see this problem in some other languages as well.

Personal anecdote:
Even the JDK, with the most portable framework I've ever used, wasn't perfect. For a university project we were using java to control serial ports connected to early bluetooth prototypes. The JDK worked perfectly from windows, but we needed to adopt a custom serial port driver for spark workstations (oh delicious irony).

hehehe interesting stuff ;)

I'm not a fan of Java personally (to be frank, it's the language I hate the most). But that boils down to personal more than anything. "each to their own" as they say hehe

Reply Parent Score: 3