positioning (it tries hard, though), but it's excellent
at border specification, coloration, fonts, and other
And I will briefly mention RDF, which I'd have to study,
but I think of that as a data retrieval system for
arbitrary XML documents (as opposed to SQL, which is a
data retrieval system for arbitrary data records).
Does OO support any of this? MS Office?
Not even close, though OO can read plain HTML files.
HTML/HTTP itself is a major bodgeup. First, HTTP was
a nice little stateless protocol; fetch a doc, get
the results back. Then images got involved -- all right,
another server transaction. Now we have cookies, plugins,
I can't even get inline SVG to work reliably in IE,
that's how bad it is, and heaven help those who want to
save about 40 bytes of headers and some processing time
by including binary pictures in that initial fetch (as
opposed to initiating another fetch, as HTTP requires now).
At least with Microsoft Word all of the crap is contained
within one, count 'em ONE, document. It would be nice
if we could get responses such as
HTTP/1.1 200 OK
Content-Type: multipart/alternate; charset=UTF-8
and have browsers and word processors process them reliably.
I'm not all that hopeful.
> How come Firefox managed to take away a good chunk
> of IE market share while Linux and Open Office can't
> even get out of 1st gear?
Because IE needs to get fixed, but it runs on a stable
platform, namely, Windows XP.
> Maybe people just don't like Linux and Open Office.
Correct. Mostly because they don't *know* it -- and even
you don't know it; Linux is the *kernel*, and just that.
Most people would probably get introduced to Linux via
Ubuntu, which could just as easily build itself around
HURD or FreeBSD, were Canonical willing to put sufficient
engineering time around the matter (and HURD sufficiently
functional; FreeBSD to its credit probably can support
almost everything Gnome and KDE require).
> Maybe you should face reality that even with 500+ Linux distributions and
> the fact that Linux is free, you still can't get people to use Linux.
People don't use Linux. They get work done (or try to,
in some cases).
*I* might write code such as the following:
movl $datas,%edx /* len */
lea data,%ecx /* buf */
movl $1,%ebx /* fid 1 -- STDOUT */
data: .ascii "Hello, world!"
(Yes, that's right, another "hello world" variant. There's
so many of them.)
Not many others would. That's as close to bare metal as
Linux allows, and the INT 80H (represented here in [g]as
syntax as int $0x80), is where the app program meets the
Most people prefer to type in commands such as 'ls'
(if they're old school) or point and click.
[*] in the sense that it never mutated. Linux now has at least
*three* audio systems (OSS, ALSA, and now PulseAudio), which
is almost as bad as Windows' internal drivers -- but no one
ever sees the drivers. To their credit, they do work reasonably
"Your mother was a hamster and your father smelt of
elderberries!" - Monty Python and the Holy Grail
Posted via a free Usenet account from http://www.teranews.com