Re: Visual Basic.net

> classic Win32 style api is being phased out. The new API is WinFX and
> it is .NET based.
>

---------------------------------------------

http://www.microsoft-watch.com/article2/0,1995,1820607,00.asp

""Contrary to what many believe, Longhorn won't be built on top of the .Net
Framework, we hear. But that might not be a bad thing."".....

""Everything in Longhorn was supposed to be written in C# and to be managed
code. But managed code was going to require machines that weren't going to
be available for five years or more. So now Microsoft is rewriting
everything in Longhorn, the developer says.""...
---------------------------------------------

Require machines that won't be available for 5 years?
They seem to be saying it's so bloated that it can only
run with high efficiency in the realm of futuristic imagination.

On the other hand, is that a surprise? There's no such thing
as a Java OS, after all. (And Microsoft wouldn't be banning
the publishing of benchmarks in their .Net license if there
weren't something to hide.) Why in the world would Microsoft
encapsulate the OS into .Net files and then run it from
there? You're more expert than I am about this kind of thing,
but wouldn't that be a bit like running the file system out of
SCRRUN.DLL? What would be the point? The only reason I
can see for them ever having talked that way in the first place
is simply to prevent .Netters from feeling like second class
citizens; to make the .Netters feel that they're on the right
train and are getting access to the API.

I also wonder how relevant it is to talk, at this point, in terms
of what Longhorn will require. I wonder what percentage of
programmers are still assuming that they'll move on to Longhorn
(which is stil 1 1/2 years away at best). It's appeared for
quite awhile that Microsoft is trying to take off in a radical direction
that is not likely to be 3rd-party-programmer-friendly. Just in the last
couple of weeks there have been two interesting articles (links below)
pointing toward greatly restricted access and usage of the OS with
Longhorn and beyond. (And of course there's the fairly radical
changes with the browser: I've had to add explanations to my
website to explain why Microsoft's Internet Explorer is warning people
that my downloads are unsafe. And now there's a pronouncement that
the browser will henceforth be a fully integrated aspect of Windows, not
just an insidiously intertwined component.)
In short, Microsoft can hardly turn Windows into a DRM-armored
multi-media player and still leave 3rd-party programmers with
unfettered access to the API.

related links:

http://www.latimes.com/business/la-fi-micro17jul17,0,3776901.story?coll=la-h
ome-business

""Fashioned with considerable input from Hollywood, the forthcoming Longhorn
version of Windows will allow rights-management tools made by Microsoft and
others to keep video encrypted as it moves around inside the PC and stop it
from leaving the home network.""

----------------------------

http://www.engadget.com/entry/1234000143050582/

If OPM determines that your monitor
falls below the security restrictions (i.e. isn't DVI or HDMI w/HDCP),
you could be greeted with a "polite message explaining that [your
monitor] doesn't meet security requirements."


.

Relevant Pages

  • Re: Wronghorn
    ... I can run the same Windows ... As far as I can tell, Longhorn is yet another Windows ... >> Microsoft typically pushes big software bundles that ... >> Customers who chose to migrate to Longhorn will be faced ...
    (microsoft.public.windowsxp.general)
  • Re: <<< Small Biz Server News week of April 11, 2004>>>
    ... > Small Business Server Customers ... > Partner Edition with Microsoft Office InfoPathT 2003 at no additional ... > of Longhorn, the next version of Windows, to make sure it's shipped ... > paring down its next generation Windows release code-named Longhorn. ...
    (microsoft.public.backoffice.smallbiz)
  • Re: <<< Small Biz Server News week of April 11, 2004>>>
    ... > Small Business Server Customers ... > Partner Edition with Microsoft Office InfoPathT 2003 at no additional ... > of Longhorn, the next version of Windows, to make sure it's shipped ... > paring down its next generation Windows release code-named Longhorn. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: <<< Small Biz Server News week of April 11, 2004>>>
    ... > Small Business Server Customers ... > Partner Edition with Microsoft Office InfoPathT 2003 at no additional ... > of Longhorn, the next version of Windows, to make sure it's shipped ... > paring down its next generation Windows release code-named Longhorn. ...
    (microsoft.public.windows.server.sbs)
  • Re: re:vb.net?
    ... etc. that work on all Windows versions. ... Longhorn looks to be at least 2 years out. ... from a Microsoft hardware partner. ...
    (microsoft.public.scripting.vbscript)