Hacker News new | past | comments | ask | show | jobs | submit login

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



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.


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++).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: