Linked by Thom Holwerda on Sun 16th Dec 2007 17:57 UTC
Windows The first publicly available test release of Vista SP1 has been released a few days ago, release candidate 1. "The Windows Vista Service Pack 1 Release Candidate is now available to the public. In addition to previously released updates, SP1 contains changes focused on addressing specific reliability and performance issues, supporting new types of hardware, and adding support for several new technologies. SP1 also addresses some management, deployment, and support challenges." Ars reports that it finally enables the hotpatching support in Vista.
Thread beginning with comment 291491
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: no shit
by sappyvcv on Mon 17th Dec 2007 03:46 UTC in reply to "RE[2]: no shit"
sappyvcv
Member since:
2005-07-06

But at the end of the day, I want control over my operating system. I'll decide whether or not something is deleted, whether or not it is over written. UNIX treats me like an adult and says, "if you want to do that, you know the risks, you're a big boy".

And that would work really well for most Windows users...

Reply Parent Score: 4

RE[4]: no shit
by kaiwai on Mon 17th Dec 2007 03:56 in reply to "RE[3]: no shit"
kaiwai Member since:
2005-07-06

And that would work really well for most Windows users...


Why should Windows be castrated because the ineptness of a few? Sometimes a bit of tough love and mistakes is the only way for some people to learn.

Reply Parent Score: 2

RE[5]: no shit
by sappyvcv on Mon 17th Dec 2007 03:58 in reply to "RE[4]: no shit"
sappyvcv Member since:
2005-07-06

But they won't learn. You HAVE to make things safe and recoverable. To not is to be naive about the realities.

Reply Parent Score: 7

RE[5]: no shit
by PlatformAgnostic on Mon 17th Dec 2007 07:41 in reply to "RE[4]: no shit"
PlatformAgnostic Member since:
2006-01-02

Most people don't care to learn... it's not interesting to anyone but us OS geeks.

I think that the choice made in Windows is the right one. The highest priority bug is one which can cause loss or corruption of permanent data on the hard-drive. If users can somehow have multiple versions of a dll accessing the some shared file or shared memory region (for instance take a look at the ESE engine, which was mentioned so vociferously in response to your recent mac post on Ars), then replacing a dll in one process but not in all of them could result in total loss of the data in that file.

It might seem far-fetched, but Windows is used by a lot of people in many environments and who knows what random third-party dlls are doing with shared files or shared memory. Choosing safety over convenience and efficiency is often a valid engineering choice when the cost is low and the cost of failure is unknown.

Reply Parent Score: 7

RE[5]: no shit
by null_pointer_us on Mon 17th Dec 2007 14:48 in reply to "RE[4]: no shit"
null_pointer_us Member since:
2005-08-19

The ineptness of a few?

Try...many?

Reply Parent Score: 3