Is it too late to start hating Microsoft/Windows products?

[Perry Winkle]

Originally Posted by dar512

There is an OSS project called Haiku which is working to recreate BeOS. It is getting well along and there is the final (free) release of BeOS to work from in the mean time. It is much more pleasant to use than Linux for a single user, non-server, machine. Worth looking at.

I've heard about Haiku various places but never bothered to read up at all. What's the Sci-Fi writer who is BeOS fanboy? Is it Neal Stephenson?

I can't seem to find where to download Haiku, I guess haiku-os.org is their official site?

I did find a review of yellowTab's Zeta 1.0 which sounds interesting but there's no way in hell I'm paying $130 for it without a compelling reason.

[dar512]

Haiku is still under development and doesn't have a download per se.

Instead go to www.beosonline.com and download the BeOS Developer Edition. This is the free personal edition that BeOS corp ended with, but updated with later drivers.

I was hoping to lend a hand with the development of Haiku as I think it is a much more approachable OS for single users than Linux. But I'm pretty solidly booked with other projects.

[russotto]

Originally Posted by grant

Linux is very solid for desktop use as long as you're willing to read the manual and a large number of options doesn't bug you.

And if you don't want to go blind. Freetype just doesn't cut it, even with the evil patent-violating bits turned on. Err, make that the evil-patent violating bits.

Aside from that, KDE still seems a bit klunky. But then again, so is Windows.

[tw]

By far, the largest problem I have had with Operating Systems is directly traceable to incompatible hardware. No just individual devices and strange driver problems; also conflicts with IRQs, registry problems that the hardware manufacturer did not properly address or properly remove, etc. IOW, by number, the most common reason for problems are directly traceable to component vendors who did not sufficiently design their product.

I can't say enough about brand name products because these incompatibilities tend to be less common with the (more expensive) brand name products.

Some glaring examples were software that, well, the vendor eventually conceded that their product was not compatible (yet) with that upgraded or new Operation System.

[slang]

Originally Posted by Hobbs

All in all, I've been pretty satisfied with Microsoft lately.

This is the "Macroshaft Sucks donkey ass" thread man! What are you doing!?

[BigV]

Originally Posted by Elspode

Ignoring substantive issues is SOP for gigantic corporations flush with other people's money. Hopefully, such blatant disregard for your customer base is the first step to failure.

I know "OPM" sounds cool, but in this context I don't think it applies. I doubt there's much Microsoft needs to use credit for. They're exceedingly cash rich. And it's all their money.

I have to agree with Hobbs. Windows XP Pro SP2 has been beddie beddie good, to me.

[BigV]

Hey, now you can all wallow in it.

[Perry Winkle]

Originally Posted by tw

By far, the largest problem I have had with Operating Systems is directly traceable to incompatible hardware. No just individual devices and strange driver problems; also conflicts with IRQs, registry problems that the hardware manufacturer did not properly address or properly remove, etc. IOW, by number, the most common reason for problems are directly traceable to component vendors who did not sufficiently design their product.

I think the hardware is probably designed well enough. It's more likely that the drivers are bad. That's why it's important to release detailed specs and good docs so that drivers can be written for _any_ system or rewritten if the manufacturer's drivers suck.

I don't think you should blame the OS because the drivers for your hardware aren't up to snuff and you can't blame the hardware because the drivers are shit.

[Hobbs]

Originally Posted by slang

This is the "Macroshaft Sucks donkey ass" thread man! What are you doing!?

Hey, I'm just saying........

I've never used Linux or BeOS, so I can't vouche for the stability of those OS's.

If it makes you feel better Slang, I do like Macintosh OSX and I think Bill Gates glasses makes him look gay, gay, gay!

How's that?

[Perry Winkle]

Originally Posted by Hobbs

Hey, I'm just saying........

I've never used Linux or BeOS, so I can't vouche for the stability of those OS's.

If it makes you feel better Slang, I do like Macintosh OSX and I think Bill Gates glasses makes him look gay, gay, gay!

How's that?

If you think the glasses make Bill look fruity check this out.

[Happy Monkey]

Or this.

[dar512]

Not so much now, but when he was younger BG sounded just like kermit the frog.

[xoxoxoBruce]

Originally Posted by slang

This is the "Macroshaft Sucks donkey ass" thread man! What are you doing!?

No, this is listen to Slang whine about big bad Bill Gates won't design his world around Slangs lifestyle.
When are you going learn to stay away from ANY corporate or gumint programs. Don't seek the truth...you can't handle the truth.

[tw]

Originally Posted by grant

I think the hardware is probably designed well enough. It's more likely that the drivers are bad. That's why it's important to release detailed specs and good docs so that drivers can be written for _any_ system or rewritten if the manufacturer's drivers suck.

The problem with so much hardware design (and I worked on enough for the government to appreciate why) is that the drivers are part of the hardware design. Unfortunately too many hardware designers don't understand software and too many software writers don't have a clue about what is really happening in hardware.

I was often requested to use both software and hardware debugging tools in conjunction - be it to align disk drives in the old days or solve a bus problem in the later years. I would end up writing my own diagnostics because management had never bothered to coordinate hardware and software people in developing those necessary tools (that cost money). In many cases, communication was so poor between the hardware designer and his software assistant (who was writing the drivers) that some hardware and software departments all but would not talk to one another. Another tactic was no documentation for the hardware / software interface. Quality was not as important as cost controls and schedules.

Therefore hardware caused strange problems where it does not affect the manufacturer's bottom line - with you.

USB was a unique and rather unusually reliable creation. To address this hardware/driver problem, the USB consortium would sponsor 'plug-fests'. Then when the product did not work with so many other USB products, the boss probably could attack both his hardware and software people to either force a team or create open warfare.

From the user's perspective (if he does more than just shotgun or swap components), the hardware (chips and software/firmware) incompatibility was often reason for strange failures.

Today, bad hardware causes Windows systems to not recover from standby or from hibernate. Incompatiblity causing clone computer board manufacturers to have long lines testing their boards to video cards from virtually every video card manufacturer. And still I have seen at least one motherboard that was not compatible with a large number of AGP video cards - literally dropping pixels when run in 4X mode. Again, defective hardware. A new version of the same board appeared but months later meaning the manufacturer knew of the intermittent and was designing a replacement while still selling that marginal and earlier version. Again - hardware failure. You don't matter when it is not a brand name product.