Linked by Eugenia Loli on Tue 11th Nov 2003 21:43 UTC, submitted by John
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
Linked by Thom Holwerda on 05/15/13 23:03 UTC
More News »
Sponsored Links



He might have meant "going away in the UI", but he said, "Longhorn is going to have vector graphics only."
To your point of just the UI having vector graphics. Again, that is a misnomer. The Longhorn UI can't go to vector graphics 100% without completely breaking all existing applications that rely on the bitmap UI toolsets. While Apple might've been able to demand a break in compatibility with OSX, Microsoft has too much inertia with the current apps to demand that everyone buy new programs immediately when they buy Longhorn. Longhorn will have to support bitmaps in the UI in some way shape or form.
I've seen the videos on XAML. It's nice, it's slick. It also won't be the only way we interact with our Windows boxes for probably a decade or so. People are still using DOS and Win16 apps a full 8+ years after Win95 came out. People are hesitant to change, especially if what they have works for them. Given that, people will still be using apps that require MFC, QT, wxWindows, et. al. for a long long time after Longhorn ships.