>> as someone who's trying to give up smoking, had to contribute to this
>> thread.
>>

Warning: Windows can damage your health (and perhaps that of others: Passive
Computing);

>> "OS" and ""windows" in the same sentence ???  Ha.  If you try to use a
toy
>> as
>> a real tool for real work, it's bound to break.
>>
> >(sorry, couldn't resist. :-)
>>
>>  Derrell
> - second, i wish people would keep politics and religion out of this forum
> (""OS" and ""windows" in the same sentence ???  Ha.")  windows has
> contributed more to the economic health of this planet that any other
> single technology.
I think penicillin and learning to sharpen flint were as important if not
more so!
Food has also contributed to the health of this planet, but, tastewise,
there is good food and there is bad food, even though both might have
similar nutritional value;

Religions often suggest what we might be theoretically capable of, their
practical application being rather a disappointing mix of failure to live up
to the ethics proposed and a desire to eliminate alternatives (spot the
analogy with operating systems if you dare).
I can actually conceive of an OS that I would consider ideal, the market
reality being Windows however;
The principle of the "open" market has the inbuilt flaw that if it is truly
open it inevitably leads to a monopoly (Microsoft being possibly the best
historical example to date);

So as not to be completely OT, I send best wishes to all involved with
SQLite development and testing.

I am interested to see SQLite being proposed for a cross platform Open
Source database engine: it is interesting to note that forty years of
commercial competition has not really proposed a viable standard for such a
database engine (too much proprietory vested interest to permit such a
thing?), the usual case of what the supplier can sell being more important
than what the client needs to use: end result: the "client", in this case
the serious database user, collaborates with others of that ilk to produce
what he himself needs to use:
Since SQLite might be moving in this direction, I suppose it might be a good
thing if the 'standard' database engine moves towards the 'standard'
database format, by which I mean XML import/export; this can be arranged
secondarily by whatever frontend is being used but I suppose standard XML
import/export functions might be a good thing, perhaps eventually using XML
as the primary file format (I know its bulky but it is more or less a
standard and memory and disks are huge);

K. O'Neill

----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, July 16, 2004 10:50 AM
Subject: Re: [sqlite] sqliteOsEnterMutex() and sqliteOsLeaveMutex()


>
>
>
>
>
> as someone who's trying to give up smoking, had to contribute to this
> thread.
>
> - first of all the generalisation about using multiple threads is
> misguided. its low level work, you need to be careful, and applications
> need to be architected so that most programmers working on the project
> don't need to worry about multithreading issues. using multiple processes
> has similiar problems when trying to access shared resources - race
> conditions, deadlocks etc. the only obvious difference is that in a
> multi-process approach you don't get to share the same memory structures
by
> default, and so don't need semaphores etc guarding them.
>

>

Reply via email to