On Tuesday 24 June 2003 14:15, Gilboa Davara wrote: > Here's a couple. > > A. Development tools and workplaces: > Low adaptation gives MS power to dictate *bad* (non)standards. MS-Word > is not the real problem here; MFC, DirectX, Visual Basic, C#, etc are! > As developers we are forced to use non standard closed tools and > libraries that can be changed without notice by Microsoft. While for now > most of us can avoid the problem, how much time do we have till we are > forced to write MFC under C#? (Instead of C under Linux/posix?)
MFC under C#?! Do you even know the technologies you're talking about? (Background: MFC, short for Microsoft Foundation Classes, is Microsoft's C++ library, similar in aim to Qt, Borland's OWA and in some areas overlapping STL) Regarding "Microsoft changing libraries without notice" -- Are you generating FUD or spreading FUD you've heard elsewhere? Does the MSDN count or you rely on a Microsoft representative coming to your door to inform you of API changes from MFC 4.2 to MFC 7.0? Or maybe you relied on undocumented functions? (which is just like using headers from /usr/include/qt3/private/ and then complaining to Trolltech that they broke them) I'm not sure how you get to code plain C and POSIX-clean code all day, but it seems to me most software developed today is graphical -- and how is Qt more standard than MFC or the .NET Framework? ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
