3 ms·
Once a hacker, always a hacker. What an amazing story! And to think he was coding raw GTK, which is a nightmare even with vim+autocomplete. Sample from his patc
by mayank 16y ago
Once a hacker, always a hacker. What an amazing story! And to think he was coding raw GTK, which is a nightmare even with vim+autocomplete. Sample from his patch:
image = eog_thumb_view_get_first_selected_image(EOG_THUMB_VIEW (priv->thumbview));
g_return_if_fail (EOG_IS_IMAGE (image));
file = eog_image_get_file (image);
filename = g_file_get_path (file);
- unwind 16y agoMeh. I would disagree; It's very subjective. Sure it might look very verbose on first sight, but most of the seemingly excessive text is just there since it's C. You get used to it, and the GTK+-family API:s are generally very well-designed, very orthogonal and predictable. The verbiage "falls away" from your sight after a while, and you just do what you want done.
- zem 16y agoi think he meant it in the context of the long function names really making a difference when you have to tap each character out in morse code with your knee.
- pbhjpbhj 16y ago>"long function names really making a difference when you have to tap each character out in morse code with your knee" I wonder if he did or if he shorthanded them and used find+replace?
- unwind 16y agoAh, good point of course. For that reason, I really hope he used some kind of completion in the IDE/editor.