Re: VS2005 and VS 6.0
- From: Daniel James <wastebasket@xxxxxxxxxxxxxxxx>
- Date: Wed, 14 Jun 2006 14:29:44 +0100
In article news:<ekBXhq0jGHA.4044@xxxxxxxxxxxxxxxxxxxx>, Tom Serface wrote:
Microsoft is very interesting in "Trustworthy computing" so
they are, of course, pushing .NET as their paradigm towards this end,
NET isn't really much of a solution to untrustworthiness. The fact that
executables run in a sandbox and can check for some error conditions (and
possible engineered exploits) at runtime does help, but it isn't enough.
Other technologies -- correctness proofs and code signing, for example --
could offer far more, and can be applied to native code.
What could make .NET really useful is the ability to deploy a single
application binary across multiple disparate platforms -- how ironic it is,
then, that the only platform on which .NET is fully supported in Windows
intel/AMD platforms (even Pocket MP .NET on ARM is an eunuch). If Windows
for PPC, MIPS, and Alpha were still supported .NET would be far more
useful.
None of this has anything to do with IDE design, though, except insofar as
MS has chosen to target managed code rather than unmanaged with its GUI
designer.
... for what it's worth, I think there are far more people who like
.NET than don't ...
There were always more VB programmers than VC++ programmers, that doesn't
mean that VB is or was in any way as good as VC++ -- just that it was (or
was perceived to be) an easier (or cheaper) way for average programmers to
achieve relatively simple tasks ... and that as much the result of hype and
marketing from Redmond than of any property of either VB or VC++.
There is a class of tasks for which the controlled execution environment of
Java or .NET brings useful benefits ... it's not a very large class of
tasks, and I doubt that most people who code for those environments are
coding tasks in those classes. People like .NET because MS have built an
easy-to-use etch-a-sketch designer that makes it look as though you don't
need to do any coding to use it ... so people who aren't interested in
doing any coding like it.
This sort of tool support could be provided for native C++ development --
it doesn't depend on .NET in any way -- it's just that MS have chosen to
create tools that target the .NET runtime and not to create tools that
target native Win32. This gives people the mistaken impression that ".NET
is easy", when the reality is that ".NET has better tool support".
Personally I find .NET to be a distraction I could well do without. Most of
the code I write would not benefit from running in a software VM -- it
doesn't need a sandbox -- and much of it needs to be portable to
non-Windows platforms. I normally write backends in portable standard C++
and Windows frontends in MFC (though I'm looking at using wxWidgets or Qt,
or maybe something non-C++ like Python for the front-end code in future
projects). Although I regard C# as a better thought-out language than Java
it doesn't have the cross-platform support that Java has, so if/when I need
something that runs in a sandboxed environment I'll use Java rather than
C#.
NET is still very CV-friendly. It's a new technology, and people are still
keen to learn it and evaluate it for themselves, and to be able to claim
experience with it when job-hunting. Java went through this a few years ago
when it was still buoyed up with hype. I don't expect it to last.
Cheers,
Daniel.
.
- Follow-Ups:
- Re: VS2005 and VS 6.0
- From: Joseph M . Newcomer
- Re: VS2005 and VS 6.0
- From: Tom Serface
- Re: VS2005 and VS 6.0
- References:
- VS2005 and VS 6.0
- From: saywhat
- Re: VS2005 and VS 6.0
- From: Joseph M . Newcomer
- Re: VS2005 and VS 6.0
- From: CharlesC
- Re: VS2005 and VS 6.0
- From: Joseph M . Newcomer
- Re: VS2005 and VS 6.0
- From: Ian Semmel
- Re: VS2005 and VS 6.0
- From: Tom Serface
- VS2005 and VS 6.0
- Prev by Date: Re: DLL linking to another DLL
- Next by Date: Re: VS2005 and VS 6.0
- Previous by thread: Re: VS2005 and VS 6.0
- Next by thread: Re: VS2005 and VS 6.0
- Index(es):
Relevant Pages
|
Loading