3 ms·
Tell him its writern in C++ .... He will switch again ;)
by z3phyr 14y ago
Tell him its writern in C++ .... He will switch again ;)
- raverbashing 14y agoBuilding graphical interfaces in C feels like carving a tree with a knife Now, building them in C++ feels like carving a tree with a power drill. Better, but still not the right tool And GTK makes C feel like C++, the bad parts I mean, without the good ones. I think Android does it in a good way, browsers also made it easier to create nice interfaces, not sure how it works in IOS though.
- meaty 14y agoI will vouch for your comment. I recently tried to knock up a simple GTK+ UI for something and it was utterly painful.
- bkor 14y agoYou can write GTK+ in pretty much any language, so if it was painful, you chose the wrong one.
- 3amOpsGuy 14y agoI don't know. Take QT for example, I'm happy to risk blowing my leg off with c++ just because I feel really productive with Qt, it truly is a wonderfully productive library, and the external ecosystem is supportive, whatever complex visualisation I want to draw, I can often find a lib that's happy to draw into a qpixmap - c++ on its own or with boost etc. doesn't leave me feeling as productive. GTK feels drawn out to me in comparison.
- raverbashing 14y agoExactly Some libraries manage to iron out the difficulties of the language. QT and WxWidgets are examples of that. GTK (on C) and Windows MFC are examples of how libraries can make it harder on the user.
- meaty 14y agoI tried python and c. Both were horrid.
- omaranto 14y agoFor writing GTK apps the language Vala seems like a good choice. It's a C# like language whose object system uses glib objects underneath the hood, this makes object-oriented C code (as required by GTK) look like a modern object-oriented language.