4 ms·
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 mad
by stephen_g 15y ago
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'...
- chrisjsmith 15y agoI think it's fair. GTK programming in C is painful (the moment you hit gobject), which is where I think he is going.
- gue5t 15y agoWhat 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.
- chrisjsmith 15y agoThat's about it - macros, boilerplate, constants. Straight from wikipedia the ultimate yuck: http://upload.wikimedia.org/wikipedia/commons/1/17/GObject_example.png http://upload.wikimedia.org/wikipedia/commons/1/17/GObject_e... I have no problem with C at all (I prefer it to C++).