Inside SWT

Tuesday, August 21, 2007

Backpfeifengesicht

German for a face that cries out for a fist in it.

As part of the "API is forever" philosophy, SWT committers spend a lot of time exploring naming, package visibility and the way an API works, a long time after the code works. There is always tension between the smallest number of classes, methods and constants needed to get the job done, consistency with similar concepts in the toolkit and the future. The future is important because "API grows like fungus", however twisting today's API for a future that may never come makes today's API cumbersome and hard to maintain. So, before an API makes it out, we've considered the likely futures and have concrete ideas about what we will do should they arise. As you can imagine, all this discussion is very stressful.

I love the fact that the Germans have a word for something I feel every once in a while.

Steve

3 Comments:

  • Well the Germans, you have to like them. Period. :)

    On a different note - is there some secret competition inside of the foundation to somehow compare Eclipse and fungi?

    First Ian: http://ianskerrett.wordpress.com/2007/05/15/is-eclipse-a-small-fungi/
    and now you:
    The future is important because "API grows like fungus", however twisting today's API for a future that may never come makes today's API cumbersome and hard to maintain.

    Talking about "future" and "Eclipse" there has been a new double-release of SWTSwing/EOS recently ( http://eos.sourceforge.net ). It is still not perfect but already runs quite nicely on all platforms most importantly OSX Leopard and OS/2. Since I bought myself a Macbook this summer I wonder if there are any news about Leopard and native SWT support?

    By Blogger Dieter, at 2:28 PM  

  • Ask Apple.

    By Blogger Steve, at 7:01 AM  

  • We implore you, impart us with more wisdom from the funny desk. My cubicle begs for more freedom.

    By Blogger Tucson Rye, at 1:02 AM  

Post a Comment

<< Home