Re: Is that a joke ?
- From: "Wraith Daquell" <WDaquell@xxxxxxxxx>
- Date: 26 Jun 2005 11:22:54 -0700
> 1. Is .NET just an approach to enterprise development?
> 2. Or another battle with Sun's Java
> 3. Or an MS conclusion that performance doesn't matter any more
I wouldn't recommend using C# (and definitely not VB) to program a 3D
FPS. But, to be reasonable, you couldn't do it in the vast majority of
languages. That's not what they're here for; if MS 'reinvented the
wheel', would anyone be pleased? I develop many useful applications in
VB.NET that run as fast as they need to. It would be an unproductive
waste of time to use C++ or even VB6. Look at sharpDevelop, the open
source IDE. It runs quite on par with Delphi, which is natively
compiled, but sharpDevelop is written in C#.
> 4. If .NET was slow for WinFS, Office or Longhorn then why we have to believe that is fast for our own applications?
Nobody is forcing you to use .NET. There are a myriad of languages out
there... take your pick. For me, and my applications, and the
applications I've seen written and run, it works well enough.
> 5. If Microsoft want a new API why that must be based on VM technology?
First, MS gets slapped because "Java is the thing of the future". Then,
they get slapped because "they copy their competition". If the world
didn't want a VM API, MS wouldn't have made it. There are many things
that impossible or close to it to implement in a natively compiled
framework. And for the majority of apps, speed is not a killing issue,
so VMs work just fine.
> 6. Why MS call .NET a "safe" framework, safe from what? Safe from hackers, I don't thin so, they can write anything they want in unmanaged code. Safe from mem leaks, a garbage collector doesn't make good programmers or safe applications. I still wonder what "safe" means.
"safe" is a loose term. "safe" could mean that eventually, there will
be no unmanaged code. "safe" could mean that more people could create
more useful applications using good practices without worrying about
garbage collection and the like. When the PC came out, many were wary
about switching from the typewriter. "On the PC, people don't have to
worry about typos! They won't be as careful!!!" How far did that
philosophy of "we learned it, so the new generation must learn it" get
them?
> 7. Winforms1 will become obsolete because of WF2. WF2 will become obsolete because of Avalon. Then why they introduced them? Just to have something that hides Win32/GDI calls?
Think experimentation here. Considering the fact that less than thirty
years have passed since MS Windows became great, I as a developer am
willing to be forgiving when a new, better idea totally eclipses a past
innovation.
> 8. Longhorn drivers, kernel and anything "low-level" will be written in native code. LH must run in 64bit processors too, so native code must be natively compiled in 64bit API calls. That means Win32 will become Win64. Why MS don't simply implement WinFX as an OO frontend to Win32/64 API, leaving out the VM?
Well, that'd be great. That's the mistake they made with Win16, all
native stuff that won't run right on a Win32 machine. With a properly
made VM, the transition to Win64, and eventually Win128, will be
easier.
> 9. Mr Gates, why all that brain wash? You can fool some enterprise programmers but not the rest of us who used to hand-optimise our code, just to gain speed.
He's out to make money for MS, he's out to promote his products. Brain
wash is what happens in tyrannical regimes.
> Finally, a single word question to all those bright scientists who work for MS, Why?
Free Country, Freedom of Choice rings a bell. If they like it and love
it, let'm be. You don't have to work for MS; if you're correct in all
that you believe, join a competitor, fight against them following the
law (viruses prove nothing), and once again, if you're correct, the
world will come to you.
> Please don't try to change my opinion, you cannot.
Why'd you ask all these questions, then? Arrr... I got writer's cramp
for nothing :)
> By the way I'm not one of those stupid guys who use to call Microsoft as M$. Me and all my colleagues use Microsoft development tools since 1982 and we all know what exactly are JIT, VM and native compiler.
I'd agree with you on that one. Your questions were all valid, and
you're obviously a knowledged developer. Your post is a good example of
non-profane, non-offensive tech discussion. Thanks Ted.
.
- References:
- Is that a joke ?
- From: Ted Nicols
- Re: Is that a joke ?
- From: Nick Malik [Microsoft]
- Is that a joke ?
- Prev by Date: Re: Is that a joke ?
- Next by Date: RE: SQL 2000 and .NET events
- Previous by thread: Re: Is that a joke ?
- Next by thread: Re: Is that a joke ?
- Index(es):
Relevant Pages
|
