> Well, all "decent" OSes... You won't find "fork" in stupid WindoSH...
"According to market researcher OneStat.com, Windows now controls 97.46
percent of the global desktop operating system market, compared to just 1.43
percent for Apple Macintosh and 0.26 percent for Linux."
Do you have statistics on the percentage of Windows downloads for httpd?
For the Java apps, the best guess would be .zip vs .tar.gz downloads. When
we did a survey of James users, the results were:
41.5% Windows
51.2% Linux
7.3% Sun Solaris
0.0% Others
So even in our community, there is a large population of Windows users.
Personally, I am typing this on a Windows system with SSH open to 4 Linux
boxes and a FreeBSD box. My next Thinkpad, perhaps I'll be able to go with
linux for the primary OS, and use a VMWare guest for Office.
> So, the silly java architects want java to be your OS and in order to
> have you buy this shit, they tell you that if you don't do this, you
> won't have WORA.
> Java is a great "glue" and inside its vision, there is a deep concept
> of "reuse"...
And I see nothing wrong with using native code, so long as you abstract the
interface to provide portability. Two examples:
- JNDI Service Provider that full access to all file system
features by mapping attributes and file system properties.
Sure, there is native code involved. But the client does
not know that, and since it has to play by the JNDI rules,
it should be happy with whatever it finds on a particular
platform.
This is how I'd have handled the Mac resource fork. I do
not know what Apple did.
- Tuple-space, or object-space, server. Sharing could be
via shared memory, database, RMI, or who cares what, so
long as the appplication doesn't know (or care).
> And I'm afraid that WORA is getting in the way and it's preventing us
> from taking java to the next level, where it enters its medieval
> religious crusade-like attitude and simply becomes a modern, peaceful
> and cooperating technology.
WORA to me means that WHEN you use native code, you have to think about how
to abstract and encapsulate, so that application code remains portable. The
JNDI example is one that comes to mind because I can take Squeak and run it
on all sorts of devices, including my PDA, but access to advanced file
system features and some other things have not been portable. The model was
tied to the platform.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
