Yes, I've used plan and it's a beautiful application. But it isn't the point. A scheduler only really works if it's interoperable, and interoperability means standards. So it seems to me what is important is to track the IETF stuff and produce modules for all the open source schedulers (plan, korganiser (which is also nice) and others which use the standards that IETF is developing.
I've built lots of big systems in PHP, and earned a considerable amount of living doing it; so I'm really grateful to Rasmus and his team. However, I'm gradually moving all my systems away from PHP now, over to Java servlets.
Why?
Well, first is engineering. PHP is a neat hacky tool which does what it does very well. But it's not a well thought out general purpose programming language (it's not meant to be). And unless used in it's guise as an Apache module it's highly inefficient. Although I use Apache on all my servers, many of my customers don't.
Also, PHP versioning is a real problem -- it's very difficult to convert things written for PHP2 to PHP3, and PHP2 as distributed does not work with Apache 1.3 as distributed.
Whereas Java is a really elgant language which I use for most of my non-Web based stuff, and it's reasonably efficient, and the Servlets I write to plug into my Apache server will plug just as easily into my customers' Sun and Netscape servers, and even run on (hiss) (spit) NT without recompilation.
Good it is but perfect it ain't. The CSS1 documentation gives a neat way of doing drop-caps, and I toyed with it in an idle moment. Mozilla (Gecko) renders the drop caps *up* from the line; Star Office, interestingly, renders them correctly (although it gets lots of other stuff wrong).
Slashdot Mirror
Yes, I've used plan and it's a beautiful application. But it isn't the point. A scheduler only really works if it's interoperable, and interoperability means standards. So it seems to me what is important is to track the IETF stuff and produce modules for all the open source schedulers (plan, korganiser (which is also nice) and others which use the standards that IETF is developing.
I've built lots of big systems in PHP, and earned a considerable amount of living doing it; so I'm really grateful to Rasmus and his team. However, I'm gradually moving all my systems away from PHP now, over to Java servlets.
Why?
Well, first is engineering. PHP is a neat hacky tool which does what it does very well. But it's not a well thought out general purpose programming language (it's not meant to be). And unless used in it's guise as an Apache module it's highly inefficient. Although I use Apache on all my servers, many of my customers don't.
Also, PHP versioning is a real problem -- it's very difficult to convert things written for PHP2 to PHP3, and PHP2 as distributed does not work with Apache 1.3 as distributed.
Whereas Java is a really elgant language which I use for most of my non-Web based stuff, and it's reasonably efficient, and the Servlets I write to plug into my Apache server will plug just as easily into my customers' Sun and Netscape servers, and even run on (hiss) (spit) NT without recompilation.
Good it is but perfect it ain't. The CSS1 documentation gives a neat way of doing drop-caps, and I toyed with it in an idle moment. Mozilla (Gecko) renders the drop caps *up* from the line; Star Office, interestingly, renders them correctly (although it gets lots of other stuff wrong).