Re: 7 Places Where Mac OS X is Still Behind Windows
- From: "ed" <news_test@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 31 Jul 2005 00:44:27 GMT
In 2005073023305016807%marinuso@zeelandnetnl">news:2005073023305016807%marinuso@zeelandnetnl,
Marinus <marinuso@xxxxxxxxxxxxx> typed:
> On 2005-07-23 20:16:11 +0200, Snit <SNIT@xxxxxxxxxxxxxxxxxxxx> said:
>
>> "TheLetterK" <theletterk@xxxxxxxxxxxxxxxxxx> stated in post
>> 9KvEe.17251$Wt3.8189@xxxxxxxxxxxxxxxxxxxxxx on 7/23/05 11:11 AM:
>>
>>>> It links separate things together so when one fails, both do. You
>>>> have two separate documents open. While working on one you
>>>> experience a crash. If both are in one process, then both
>>>> documents go away and any changes to either are lost.
>>>
>>> And in practice, the same thing occurs on Windows because
>>> applications are never designed with that level of process
>>> independence. It's like socialism, great in theory, awful in
>>> practice.
>>
>> While it is not consistent, I have seen times when one IE window
>> will die while others are OK...
>
> That's because you're essentially running IE twice if you have two IE
> windows.
nope, not necessarily- if you start a new window from a running instance of
IE (or a javascript popup does), it's still a single instance. it's only
two instances of IE if you explicitly start it twice.
<snip>
.
- References:
- Re: 7 Places Where Mac OS X is Still Behind Windows
- From: Marinus
- Re: 7 Places Where Mac OS X is Still Behind Windows
- Prev by Date: Re: Truth and liars.
- Next by Date: Re: Vista... is MS blatantly stealing the Mac's UI?
- Previous by thread: Re: 7 Places Where Mac OS X is Still Behind Windows
- Next by thread: Re: 7 Places Where Mac OS X is Still Behind Windows
- Index(es):
Relevant Pages
|