POV-Ray : Newsgroups : povray.off-topic : The Daily WTF [again] : Re: The Daily WTF [again] Server Time
20 Jul 2025 04:26:41 EDT (-0400)
  Re: The Daily WTF [again]  
From: Darren New
Date: 12 Feb 2008 13:25:28
Message: <47b1e498$1@news.povray.org>
Invisible wrote:
> Personally, I don't think so. People have created products like 
> OpenOffice and KOffice and so forth, and they work. Reliably.

Yet, funny enough, when I boot Linux, it screams "FAT support is ALPHA!" 
  Depends on your priorities. I haven't ever had Word actually crash on 
me, either.

> Interesing you should say that. You're aware of course that the fist 
> Amiga was a 16-bit machine, and the later ones were 32-bit?

If you're going to go along that line, the first Windows machine was 
8-bit, and now they're up to 64-bit. :-) The first Amiga was a 32-bit 
machine running on a 16-bit bus.

> And - most importantly - you can take an application written back when 
> we only had 6 bits per pixel, and run it on a screen operating at 8 bits 
> per pixel. And it can share the screen with other applications and 
> change parts of the colour table and so on and so forth, and WORK.

Yeah. Better than X-Windows used to be at the same time.

> [Assuming it does all this through the OS. The Big Problem the Amiga had 
> is that since the hardware is "always" the same, a lot of software 
> bypasses the OS. Obviously this breaks horribly when the hardware 
> changes...]

Yep. On the other hand, the original Amiga books described how to frob 
the hardware.

Note that Windows supports DOS programs that bypass the OS in exactly 
the same way, and it WORKS.

> So Windows is designed to do a bunch of unecessary stuff in the 
> background by default. I consider this a design flaw. What *useful* 
> stuff does Windows do that AmigaDOS doesn't?

It depends who you are. Aren't you the one complaining about lack of USB 
support in your NT machines?

> I mean, sure, it tells you what was happening at the exact instant the 
> crash happened, but how do you find out what the actual problem is?

Same way you do for Linux errors. You google the text of the error 
message, or search for it on MSDN.

> If there were anything I could do to find out, I'd do it. Unfortunately, 
> there isn't.

There's lots you can do. You just don't know how. That's why they give 
you the stack dump and such.  "Wow, if only I could read a core file, 
I'd be able to tell which program is dumping core!" :-)

-- 
   Darren New / San Diego, CA, USA (PST)
     On what day did God create the body thetans?


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.