Everybody will talk about it and everybody will know that Microsoft is limiting XP users to push them at buying their new Windows 7 OS.
They did the same with directx10 and vista.
I'm sure it's pretty easy for them to devellop a patch for XP to support those IMPORTANT FEATURES like double buffering, next directwrite API (text) correcting shitty WPF small fonts bug, directx 10.1 and direct2D etc..
I'm sure windows 7 is gonna be quite popular no need to cripple users. It will actually give them a bad name and they should instead really work in the direction of being friendly and sincere to all windows users not just new buyers.
I hated vista but i wanted directx10 , i still decided to stick to XP because it's like a 300hours work to just reinstall all my programs, addins, vsts ect, reconfiguration etc..
I will buy windows 7 no worries and run it in dual boot but still i need my XP to AT LEAST be FIX for the WPF font bug, visual studio 2010,tearing fix, support for Directwrite and also some hardware acceleration would be great.
What will i say to every company that use XP, if i want to sell them a WPF application. Sorry you gonna have to change everything upgrade everywhere to windows 7 if you want to be able to see the text clearly in my application that i spent 9 months develloping.
Clearly, you can put nice words here and there but if WPF application work badly on XP your gonna loose a lot of support from everywhere. Think about it, your on a nice road now with windows 7 no need to spit against the wind.
Everywhere you promote the new WPF 4 and new WPF interface for visual studio in the 2010 release but if you don't fix all those XP WPF bugs for the final release then your risking a lot believe me. You might be able to control review sites a little but you
cannot controls forums review.
(Like if every company will be able to pay upgrade cost to both visual studio 2010 + Windows 7 for every devellopment computer at the same time)
Believe me all XP devellopers will fight until they have what they want and the only way they can fight is on forums like this one.
You don't want all those devellopers to bloat all your forums with post like this one
Hi Don, I really like what you did with F# but why all the change from c# in the syntax/keywords for things that are doing the same thing????
like void and unit?? (i'm sure you know best all those construct that have had a synthax change, me i'm still new)
I guess some change could be nice but are you sure they are all necessery? I'm sure it would be easy just to redo at least the most evidant unnecesery naming change!!
C# which use similar syntax to java is in my opinion a very clear syntax.
(i'm not talking about the specific part of the F# language but the identical parts to C#)
My brain is tired of translating everything languages construct everytime a new nice language come out and F# is so nice.
Anyway I guess your doing this because Microsoft told you this so that in the future they can incorporate F# in C#.
still why unit for void, why not void i can't understand hehehe in delphi a unit is a module not nothing... and unit??? i don't see the point of using a word like unit to represent nothing.
Anyway this is only my opinion as a starter with F#. I understand for people that are already totally in it that their language construct is what they want but heck it's always the same * a new language arrive.
I still think F# as a wonderfull future tho and I'll put the time to learn it but these days, all those C# changes + all the change that are coming from every libraries, my brain is so fucking tired, please every component and language programmers relax a bit
for me to breathe hehehe
and i'm a young programmer hehhee how old programmers are doing these days???? I'm sure most are in the verge of depression hehhe
I still think those new tools/constructs/components are useful and will save me a lot of time but dam, they will all become mandatory and after so many years i'm still totally in books, guide, tutorials, videos, .....
hihihi sorry all, I just wonder if i'm alone like this