win32...MFC...obsolete?
-
Is the win32 platform going obsolete? Is it being replaced by the dotnet framework or something like that?
yes. of course.
image processing toolkits | batch image processing | blogging
-
yes. of course.
image processing toolkits | batch image processing | blogging
-
Visual LISP .Net 2010++ , i think
image processing toolkits | batch image processing | blogging
-
XML-based operating systems and apps, with code embedded in CDATA blocks. But hey, it'll compress real well, since it's all ASCII. The biggest problem they're working on though is the code security issues. You thought .NET was bad with tools like reflector, but an XML-based OS can be read without even needing a tool, just pop it into notepad. So, that's a problem right now, but there should be some obfuscators coming along to change the XML tokens and mangle the tags, etc. But it makes sense, when you think about it. The backplane for the OS is going to WCF for the communications, which of course is XML-based both in the way you specify the I/O endpoints and the packets themselves, and then there's WF, the workflow foundation, which will manage the OS's low level thread and resource allocation, completely XML specified, and the shining jewel is WPF with XAML for all the XML-based UI components. Really. Marc
-
Is the win32 platform going obsolete? Is it being replaced by the dotnet framework or something like that?
deostroll wrote:
Is the win32 platform going obsolete? Is it being replaced by the dotnet framework or something like that?
There's this CPian guy here - I forget his name, from Texas. Fellow was dead against .NET and kept saying garbage collection sucks and all that. Last I heard he's been running around in a mad rush trying to get a .NET job. He's even porting some of his C++ code into C#. That says it for you I think. Now if only I could remember who I am talking about. :rolleyes:
Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
My latest book : C++/CLI in Action / Amazon.com link -
deostroll wrote:
Is the win32 platform going obsolete? Is it being replaced by the dotnet framework or something like that?
There's this CPian guy here - I forget his name, from Texas. Fellow was dead against .NET and kept saying garbage collection sucks and all that. Last I heard he's been running around in a mad rush trying to get a .NET job. He's even porting some of his C++ code into C#. That says it for you I think. Now if only I could remember who I am talking about. :rolleyes:
Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
My latest book : C++/CLI in Action / Amazon.com link -
deostroll wrote:
Is the win32 platform going obsolete? Is it being replaced by the dotnet framework or something like that?
There's this CPian guy here - I forget his name, from Texas. Fellow was dead against .NET and kept saying garbage collection sucks and all that. Last I heard he's been running around in a mad rush trying to get a .NET job. He's even porting some of his C++ code into C#. That says it for you I think. Now if only I could remember who I am talking about. :rolleyes:
Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
My latest book : C++/CLI in Action / Amazon.com linkNishant Sivakumar wrote:
this CPian guy here - I forget his name, from Texas. Fellow was dead against .NET and kept saying garbage collection sucks and all that
Hmmmmm, and I wonder who that is :laugh:
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
-
Visual LISP .Net 2010++ , i think
image processing toolkits | batch image processing | blogging
Chris Losinger wrote:
Visual LISP .Net 2010++
Woohooooo :laugh:
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
-
XML-based operating systems and apps, with code embedded in CDATA blocks. But hey, it'll compress real well, since it's all ASCII. The biggest problem they're working on though is the code security issues. You thought .NET was bad with tools like reflector, but an XML-based OS can be read without even needing a tool, just pop it into notepad. So, that's a problem right now, but there should be some obfuscators coming along to change the XML tokens and mangle the tags, etc. But it makes sense, when you think about it. The backplane for the OS is going to WCF for the communications, which of course is XML-based both in the way you specify the I/O endpoints and the packets themselves, and then there's WF, the workflow foundation, which will manage the OS's low level thread and resource allocation, completely XML specified, and the shining jewel is WPF with XAML for all the XML-based UI components. Really. Marc
I heard we want to be switched over by this fall, when all Win32/MFC/C++/C# support is dropped. :rolleyes:
Mark Salsbery Microsoft MVP - Visual C++ :java:
-
I heard we want to be switched over by this fall, when all Win32/MFC/C++/C# support is dropped. :rolleyes:
Mark Salsbery Microsoft MVP - Visual C++ :java:
Mark Salsbery wrote:
to be switched over by this fall
And go with Visual Lisp++, it's the wave of the future. Just imagine all the curly-cues :laugh:
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
-
XML-based operating systems and apps, with code embedded in CDATA blocks. But hey, it'll compress real well, since it's all ASCII. The biggest problem they're working on though is the code security issues. You thought .NET was bad with tools like reflector, but an XML-based OS can be read without even needing a tool, just pop it into notepad. So, that's a problem right now, but there should be some obfuscators coming along to change the XML tokens and mangle the tags, etc. But it makes sense, when you think about it. The backplane for the OS is going to WCF for the communications, which of course is XML-based both in the way you specify the I/O endpoints and the packets themselves, and then there's WF, the workflow foundation, which will manage the OS's low level thread and resource allocation, completely XML specified, and the shining jewel is WPF with XAML for all the XML-based UI components. Really. Marc
What do you think of this guy's opinion? He is Allen Holub from Holub.com http://www.sdtimes.com/fullcolumn/column-20060901-05.html[^] "XML is perhaps the worst programming language ever conceived. I’m not talking about XML as a data-description language, which was its original design. I’m talking about perverting XML for programming applications. It’s inappropriate to use XML as a scripting language (e.g., ANT), a test-description language (e.g., TestNG), an object-relational mapping language (e.g., Hibernate, JDO), a control-flow language (e.g., JSF), and so forth. These sorts of XML “programs” are unreadable, unmaintainable, an order of magnitude larger than necessary, and audaciously inefficient at runtime."
-------------------------------- "All that is necessary for the forces of evil to win in the world is for enough good men to do nothing" -- Edmund Burke
-
What do you think of this guy's opinion? He is Allen Holub from Holub.com http://www.sdtimes.com/fullcolumn/column-20060901-05.html[^] "XML is perhaps the worst programming language ever conceived. I’m not talking about XML as a data-description language, which was its original design. I’m talking about perverting XML for programming applications. It’s inappropriate to use XML as a scripting language (e.g., ANT), a test-description language (e.g., TestNG), an object-relational mapping language (e.g., Hibernate, JDO), a control-flow language (e.g., JSF), and so forth. These sorts of XML “programs” are unreadable, unmaintainable, an order of magnitude larger than necessary, and audaciously inefficient at runtime."
-------------------------------- "All that is necessary for the forces of evil to win in the world is for enough good men to do nothing" -- Edmund Burke
Richie308 wrote:
I’m not talking about XML as a data-description language
The point is, the line is getting fuzzy between execution description and data description. Scripts, workflows, states, decision graphs, ORM, etc., all sit somewhere in the middle, because a lot of these things have to express data, relationships, and map to code units. So, I think he's trying to see everything in black and white when there are a lot of shades of gray. Marc
-
deostroll wrote:
Is the win32 platform going obsolete? Is it being replaced by the dotnet framework or something like that?
There's this CPian guy here - I forget his name, from Texas. Fellow was dead against .NET and kept saying garbage collection sucks and all that. Last I heard he's been running around in a mad rush trying to get a .NET job. He's even porting some of his C++ code into C#. That says it for you I think. Now if only I could remember who I am talking about. :rolleyes:
Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
My latest book : C++/CLI in Action / Amazon.com linkPeople change, but their old posts don't. :) Marc
-
Is the win32 platform going obsolete? Is it being replaced by the dotnet framework or something like that?
I've been hearing this kind of talk for ages but neither MFC nor Win32 is “dead” yet or, by the looks of things, will be in the near future. There is little doubt that .NET has sparked a lot of interest from the developer community and that managed languages have many advantages over their un-managed brethren (as things stand the reverse is also true however), but the rumors of Win32’s and MFC’s death have been greatly exaggerated.
Steve
-
Richie308 wrote:
I’m not talking about XML as a data-description language
The point is, the line is getting fuzzy between execution description and data description. Scripts, workflows, states, decision graphs, ORM, etc., all sit somewhere in the middle, because a lot of these things have to express data, relationships, and map to code units. So, I think he's trying to see everything in black and white when there are a lot of shades of gray. Marc
Marc Clifton wrote:
Scripts, workflows, states, decision graphs, ORM, etc., all sit somewhere in the middle, because a lot of these things have to express data, relationships, and map to code units.
No hardware can directly execute XML, so what do you mean when you say that OS's will be based on XML? Maybe there will be some layer that interprets the XML, but that layer itself needs to run in some kind of context, and that context is most likely going to be written in C or C++.
-------------------------------- "All that is necessary for the forces of evil to win in the world is for enough good men to do nothing" -- Edmund Burke
-
Marc Clifton wrote:
Scripts, workflows, states, decision graphs, ORM, etc., all sit somewhere in the middle, because a lot of these things have to express data, relationships, and map to code units.
No hardware can directly execute XML, so what do you mean when you say that OS's will be based on XML? Maybe there will be some layer that interprets the XML, but that layer itself needs to run in some kind of context, and that context is most likely going to be written in C or C++.
-------------------------------- "All that is necessary for the forces of evil to win in the world is for enough good men to do nothing" -- Edmund Burke
Richie308 wrote:
No hardware can directly execute XML, so what do you mean when you say that OS's will be based on XML?
I was making a joke without using the joke icon to see who would fall for it. :-D (The clue was the "Really" at the end.) Marc
-
Is the win32 platform going obsolete? Is it being replaced by the dotnet framework or something like that?
deostroll wrote:
Is the win32 platform going obsolete?
Yep.
deostroll wrote:
Is it being replaced by the dotnet framework
That's obsolete as well.
deostroll wrote:
or something like that?
Yep - JavaScript.
-
Richie308 wrote:
No hardware can directly execute XML, so what do you mean when you say that OS's will be based on XML?
I was making a joke without using the joke icon to see who would fall for it. :-D (The clue was the "Really" at the end.) Marc
:doh: Good one! I forgot you were the one who wrote the article about not using "int".
-------------------------------- "All that is necessary for the forces of evil to win in the world is for enough good men to do nothing" -- Edmund Burke
-
Is the win32 platform going obsolete? Is it being replaced by the dotnet framework or something like that?
I think using MFC for new projects is not the most money making proposition you can take on. However, I think it's wrong to suggest win32 is obsolete. There are several tools that have built up on top of it, such as wxWidgets that are thriving. Win32 is fast and down to the metal. :-) For a small project, WTL is perfect, fast, and requires NO dependencies. If you have to build a generic corporate internal software project, sure .NET is the only thing that makes sense. But if you want to work on the big juicy projects such as MS Office or some from Adobe, or any other windows application, you better know C++ and Win32 :-).
