Edit page JuneBlog

diff --git a/JuneBlog b/JuneBlog
index e20c345194546a8cbac5966e6538f19f95fe177a..de5a420afce9b5cbec8e4093c84c0a7cbd88260a 100644 (file)
--- a/JuneBlog
+++ b/JuneBlog
@@ -1,5 +1,42 @@
 == June 2007 ==
 
+=== Tue, 26th ===
+
+==== Long time, no C++ ====
+
+The title was inteded to be a joke on "long time, no see", because I've
+not been updating the blog for some time.
+
+But this reminds me that, yes, indeed I've not been doing any C++ for a few
+months now. That's probably irrelevant to most of you... but this is my blog
+and I get to decide what goes in.  Except when *you* edit it.  Damn WikiWikiWeb!
+
+The reason we don't have any C++ in the OLPC is that, in the Linux world,
+C++ never flied that much.  The kernel hackers say it's not well suited
+for kernel programming, and I partially agree.  Of course, C++ can't be
+used for glibc and POSIX system libraries.  Even MicrosoftCompany uses C
+for those.
+
+This leaves us with three more layers to exclude: windowing server,
+desktop and applications.
+
+X11 is written in C for historical reasons.  Since its internals mostly
+deal with interfaces and specialization of interfaces, C++ would have
+been very beneficial.
+
+Gnome also uses C, for no good reason.  KDE is older than Gnome and
+was entirely written in C++, although I clearly remember g++ 2.7.2 being
+quite a painful experience.  The GObject crap in glib and GTK is expecially
+ugly, hard to use and error prone due to lack of good OOP support in the
+language.
+
+And applications?  Well, applications in the OLPC are written in Python
+anyway, like many higher level applications in regular Linux distros.
+
+There's a few exceptions: Mozilla is written in C++ and eToys is written
+in SmallTalk.  I don't know about TamTam.
+
+
 === Wed, 13th ===
 
 ==== Under pressure ====