Re: How will PatchGuard change kernel programming?
- From: "smerf" <smerf@xxxxxxxxxx>
- Date: Sat, 14 Oct 2006 00:08:57 -0400
That makes sense. No need to use APIs that are being discontinued.
"Alexander Grigoriev" <alegr@xxxxxxxxxxxxx> wrote in message
news:OUKO0U07GHA.3812@xxxxxxxxxxxxxxxxxxxxxxx
An API documentation is a contract between the API vendor (Microsoft) and
the user (ISV). As such, only those functions are documented which are
guaranteed to stay and won't break compatibility with previous OS
versions. This is not always the case, though; there's been breaking
changes in Windows API sometimes, and not always for good.
Things that's never been documented are not guaranteed to stay in OS or
always continue working the same way. It's silly to rely on undocumented
API, because it will cause compatibility problems in the future.
"smerf" <smerf@xxxxxxxxxx> wrote in message
news:FtYXg.44703$8s6.18853@xxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for your response.
IMHO, this is just another way that Microsoft is increasing its monopoly
of the desktop. First, they don't release all of the OS APIs - except to
thier internal applications developers and "select" Microsoft Partners.
Now, they are locking people out of 3rd party methods that help to
protect us (like Spysweeper and AVG). They are also blocking graphics
hooks that make apps like VNC a viable alternative to the Windows-only
Remote Desktop (which is not on all versions of Windows).
I think this move (until it is hacked) will force more software vendors
out of business and increase Microsoft's stranglehold on the desktop.
I'm starting to think that we need to revisit the notion of breaking
Microsoft into an applications company and an OS company. We probably
should have done that in the original anti-trust suits.
I really don't see the problem with giving developers the ENTIRE API to
work with. Will they find flaws? Sure they will, and some will even
abuse them. But, Microsoft would be aware of flaws even sooner than they
are now and could actually take a decent stab at making the OS secure
from malicious hacking instead of from developers and users.
REALbasic + Linux is looking better and better.
"Don Burn" <burn@xxxxxxxxxxxxxxxx> wrote in message
news:uQuguay7GHA.4568@xxxxxxxxxxxxxxxxxxxxxxx
It is a good thing, since it forces people to develop properly and not
use kludgy hooking, which exposes the system to threats. For any decent
developer it will not impact them at all.
--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply
"smerf" <smerf@xxxxxxxxxx> wrote in message
news:NiUXg.10022$nn6.4289@xxxxxxxxxxxxxxxxxxxxxxxxx
How will Vista's PatchGurad change the ability of coders to extend the
OS?
.
- Follow-Ups:
- Re: How will PatchGuard change kernel programming?
- From: Alexander Grigoriev
- Re: How will PatchGuard change kernel programming?
- References:
- How will PatchGuard change kernel programming?
- From: smerf
- Re: How will PatchGuard change kernel programming?
- From: Don Burn
- Re: How will PatchGuard change kernel programming?
- From: smerf
- Re: How will PatchGuard change kernel programming?
- From: Alexander Grigoriev
- How will PatchGuard change kernel programming?
- Prev by Date: Re: Shortcomings in Win32 API docs
- Next by Date: Re: How will PatchGuard change kernel programming?
- Previous by thread: Re: How will PatchGuard change kernel programming?
- Next by thread: Re: How will PatchGuard change kernel programming?
- Index(es):
Relevant Pages
|