Re: Thanks for all the replies...
- From: Gerry Hickman <gerry666uk@xxxxxxxxxxxxxxxx>
- Date: Thu, 07 Sep 2006 22:11:27 +0100
Hi,
If you can program Win32/64 API in C++ you are already WAY ahead of anyone who uses .NET
I don't agree MFC is a waste of time - it's a CHOICE, you are not forced to use it. It's very good if you need standard Windows UI such as menus, hotkeys, common dialogs and MDI with views. It also has SOURCE CODE - tell me where the source code is for .NET??? It also has a fraction of the file size and dependencies of .NET
Try creating a professional video editing app like Adobe premiere
a) using .NET
b) using MFC
which one worked best, hell which one worked at all??
Now try changing user rights for every machine on your network so your new AntiVirus service login account can be given the right to log on as a service
a) using .NET
b) using Win32 API
which one worked best, hell which one worked at all??
Now try writing a device driver for the new scanner from HP
a) using .NET
b) using Win32/64 DDK
which one worked best, hell which one worked at all??
now try writing your latest "killer" cross platform desktop app (something like FireFox)
a) using .NET
b) using C++ with freely available libraries
which one worked best, hell which one worked at all??
now try out Microsoft's own MSI deployment technology in .NET, (not COM interop), how well did that work?
now try out Microsoft's own WMI in .NET, how bloated and idiotic was that?
now try Microsoft's AutoUpdate and vunerability scanning technology, how did that go in pure .NET?
I could write a whole book on it, but the simple answer is AVOID .NET
You are right about job adverts. If you just want a boring job it's fine, but if you plan to be at the forefront of IT and leading the way with new innovations, it's NOT fine. You can get a job at AOL, it doesn't mean AOL is the cutting edge of technology just because they have lots of jobs.
Micus wrote:
Gerry,
I'm actually migrating from straight c++ Windows API programming, however when you look at the job listings, .NET cannot be denied. Besides, it's not MFC which was (IMHO) a waste of effort.
I will wait a bit on the books or buy used ones. But I will be very frustrated if I will need a new version of Visual Studio when 3.0 becomes the standard.
Thank you, Carlos, and pvdg42,
M
"Gerry Hickman" <gerry666uk@xxxxxxxxxxxxxxxx> wrote in message news:uUOTxRT0GHA.4808@xxxxxxxxxxxxxxxxxxxxxxxHi,
I have a simple solution - AVOID .NET!
Your programs will be smarter, smaller, run faster, run cross-platform and the dependency overhead will be minute. You'll also get access to open source libraries and have the ability to tailor them to your needs - no more waiting around to see if Microsoft will fix this problem or that problem. Don't be tied to Framework versions, just avoid the Framework completely!
Micus wrote:Hi All,
I've heard some chatter about WinFX == .NET Framework 3.0. I'm about to
invest some of my hard earned cash on a few .NET 2.0 books and I was
wondering if their fate will be the same as my Managed C++ books as well as
my .NET 1.X books (and my VS 2003!)... Any links or comments will be
appreciated.
TIA, M
--
Gerry Hickman (London UK)
--
Gerry Hickman (London UK)
.
- Follow-Ups:
- Re: Thanks for all the replies...
- From: Carlos J. Quintero [VB MVP]
- Re: Thanks for all the replies...
- From: Micus
- Re: Thanks for all the replies...
- References:
- .Net 2.0... longevity question?
- From: Micus
- Re: .Net 2.0... longevity question?
- From: Gerry Hickman
- Thanks for all the replies...
- From: Micus
- .Net 2.0... longevity question?
- Prev by Date: Re: Access Denied Error In WinForms App
- Next by Date: Re: using VS as HTML editor. can not switch to design view because of errors in the page.
- Previous by thread: Thanks for all the replies...
- Next by thread: Re: Thanks for all the replies...
- Index(es):
Relevant Pages
|
Loading