The Go Programming Language, or: Why all C-like languages except one suck.

Re:The Go Programming Language, or: Why all C-like languages... by stephen_g on Wednesday June 08, 2011 @04:15AM (#2632406)

This seems like a fairly poor article overall... His point about GTK is nonsensical - C is a very good language to use because it means that bindings can be made for pretty much any language any language - which is why you can use GTK in any language from C++, to Python, to C# and Java, PHP, Javascript and so on... And C is used on thousands of projects more than 10K LOC, so I don't see how it's 'not suitable'...

[ Parent | on HN ]

Re:The Go Programming Language, or: Why all C-like languages... by chrisjsmith on Wednesday June 08, 2011 @08:55AM (#2632888)

I think it's fair. GTK programming in C is painful (the moment you hit gobject), which is where I think he is going.

[ Parent | on HN ]

Re:The Go Programming Language, or: Why all C-like languages... by gue5t on Wednesday June 08, 2011 @02:28PM (#2634369)

What part of it is painful? I've found gobject to be quite effective. It's not the most enjoyable to extend (there's marshalling and other boilerplate that's not difficult but not interesting either), but in the majority of cases when using GTK you're doing just that--using it, rather than extending it. Using C avoids the complex semantics of C++ templates/inheritance at the cost of losing type safety when things become void*, but if you a have a little discipline that tradeoff grants flexibility that's quite nice in my opinion.

[ Parent | on HN ]

Re:The Go Programming Language, or: Why all C-like languages... by chrisjsmith on Thursday June 09, 2011 @06:29AM (#2636592)

That's about it - macros, boilerplate, constants. Straight from wikipedia the ultimate yuck:

http://upload.wikimedia.org/wikipedia/commons/1/17/GObject_e...

I have no problem with C at all (I prefer it to C++).

[ Parent | on HN ]