Re: Is that a joke ?

To Jim and Ted:

You're just another bunch of Anti-Microsoft fools. You're the kind of
fellows who start uproars in enterprise environments because you're so
concerned with performance that it blinds you from getting the job done. It's
a shamed that guys like you will always exist. I'm not doubting you guys as
being very smart people. However, from a business perspective....you're
F.U.C.KING STUPID.

Regards

"Jim Hubbard" wrote:

> If you're going to develop in .Net, do yourself a favor and read the book
> ".Net Gotchas" (O'Reilly).
>
> It not only shows you where .Net is not mature yet, it shows you how to
> avoid getting slapped around by .Net gotchas.
>
> Jim
>
> "Ted Nicols" <__NoSpAm__deltafox@xxxxxxxx> wrote in message
> news:e3UQUWneFHA.3280@xxxxxxxxxxxxxxxxxxxxxxx
> > That's what I keep asking myself whenever develop in .NET. Is this a joke
> > a farse or just a bad dream?
> >
> > .NET is slow, actually slow is just a polite word I can use in a
> > newsgroup.
> >
> >
> >
> > .NET is just a VM and as one it works very slowly, before and after JIT. I
> > don't understand why some people insist that a VM can be compared with
> > native code. I really feel sick, whenever compare native C++ code against
> > the same code ported to C#. I don't know what is the performance loss with
> > databases or corporate solutions but my math/CAE functions run times
> > slower in .NET.
> >
> > Managed code might be fast enough for enterprise apps, database front ends
> > or asp intranets. It probably looks fast to Java or VB developers but what
> > about real time applications?
> >
> > What about CAD, CAE, CAM, scientific applications, utilities, math,
> > imaging, desktop publishing etc. What should developers who write such
> > applications must do ? Port them into UNIX ?
> >
> >
> >
> > What happened to the rule i knew twenty years ago? "Next version of
> > anything should be at least faster and more stable than the previous one"
> >
> >
> >
> > I have many questions for MS developers, although I'm sure nobody will
> > ever answer.
> >
> >
> >
> > 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
> >
> > 4. If .NET was slow for WinFS, Office or Longhorn then why we have to
> > believe that is fast for our own applications?
> >
> > 5. If Microsoft want a new API why that must be based on VM technology?
> >
> > 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.
> >
> > 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?
> >
> > 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?
> >
> > 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.
> >
> >
> >
> > Finally, a single word question to all those bright scientists who work
> > for MS, Why ?
> >
> >
> >
> > Please don't try to change my opinion, you cannot. 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 really like .NET/WinFX as a library and C# as a modern language, but I
> > feel sick with all that waste of processing power and lack of performance.
> >
> >
> >
> > Regards
> >
> > Ted Nicols
> >
> >
>
>
>
.

Relevant Pages

  • Re: Wild speculations about the "other" factors
    ... Delphi copies through a direct channel at Borland. ... There are thousands of Enterprise customers that buy Delphi, ... Individual pro developers, hobbyist, and students ...
    (borland.public.delphi.non-technical)
  • Re: Development considerations for Win XP
    ... From my limited reading thus far, ... Microsoft advises developers ... Administrator if apps are to work. ... "Jim Carlock" wrote: ...
    (microsoft.public.vb.general.discussion)
  • Re: Proposed MSDN Subscription Changes - VERY BAD!!!
    ... and that the developers who are working on them ... tools be included in a Microsoft product which is not VSTS, ... If you need to have Enterprise features, you will need to pay for them, ... >> aren't teally able to steer that segment of the market. ...
    (microsoft.public.dotnet.framework)
  • Re: Proposed MSDN Subscription Changes - VERY BAD!!!
    ... and that the developers who are working on them ... tools be included in a Microsoft product which is not VSTS, ... If you need to have Enterprise features, you will need to pay for them, ... >> aren't teally able to steer that segment of the market. ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: Proposed MSDN Subscription Changes - VERY BAD!!!
    ... and that the developers who are working on them ... tools be included in a Microsoft product which is not VSTS, ... If you need to have Enterprise features, you will need to pay for them, ... >> aren't teally able to steer that segment of the market. ...
    (microsoft.public.dotnet.framework.adonet)