Re: About speed

"Alex" <zencovich@xxxxxxxxxxxxx> wrote:

Sorry guys, I read this branch...and I disappointed.

I'm disappointed too - did you have to quote quite as much as you did :)

You positioned yourself as experienced developers (at least Joanna Carter, I
think is experienced).

But you still fight for thing which seems like absolutely clean even for
novice in Win32 development.

Experience in Win32 development doesn't always transfer completely
cleanly to .NET. .NET, despite being around for some time, is still
fairly new, and many people here on the Delphi newsgroups aren't fully
up to speed with the platform.

There's nothing shameful or worthy of disappointment in experienced
Delphi/Win32 developers being a little confused when learning a new
platform.

So it born a question from me.

What is .NET preference if so experienced developers cannot know how to (and
when) allocated objects must be disposed?

Experience only applies to what you've done before. If you're coming on
to a new platform, of *course* not all your experience is going to apply
directly.

..NET has a lot of libraries and architecture, especially on the server
side with ASP.NET, that make it much easier to build large systems,
IMHO. Rich reflection enables libraries that are much harder to write in
unmanaged languages.

It comes down to this: look at the libraries and infrastructure
available to .NET applications (and keep in mind coming libraries, like
WPF), ask yourself the question: would my job be easier if I could take
advantage of those libraries, rather than settling for whatever your
alternative patchwork of library support is.

Seems like if I'm not GC guru and I have not a deep understanding on .NET
architecture (which types are boxed and which are not, when they disposed by
GC, will resources free etc etc..I do not guru so I think I even not know
for all possible question I can to ask) I cannot write application with
.NET. In most cases it will worst against Win32 until I become a guru.

I picked up most of my .NET knowledge from writing and tuning an
application server written in C# 1.1 and 2.0 on .NET 1.1 & 2.0 (we
upgraded half-way through to the early betas of 2.0). In total, the
serious experience on .NET was probably about 2 years. I didn't find it
that difficult to pick up the information: research papers, blogs, PDC
presentations, SSCLI source code, there's more information available
these days than ever before. It's like everything else: you learn on the
job and build up experience.

The thing is, you only really need to know most of this stuff if you're
writing a critical piece of architecture or a library that will be under
a lot of pressure. Most of the time, writing the most obvious thing is
the right thing to do. Like almost all programming, as long as you have
the higher-level architecture right, you don't need to worry about the
details of the implementation: you can fix those with tuning etc. as you
go along.

So same question again - what is a point to use .NET?

Seems like it will require more knowledge than usual Win32 and development
will slower. Otherwise, applications will much slower. Otherwise
applications will earn too much resources and memory.....

On the other hand, you need less knowledge about Win32 development.
I personally find development with .NET *much* faster than old Delphi,
for the kinds of things I'm doing in .NET. But then, the things I'm
doing aren't typical: things like run-time code generation, for example.

Anonymous delegates and GC are two things that have changed the way I
program, and I can write much more complex applications more easily now
that I don't have to contort my code into unnatural shapes.

Sometimes you don't even realise how stale your approach is until you
learn a new language and environment that teaches you a new way.

As for things being much slower: I don't necessarily think that's true.
You have to try it and see.

PS Really I do not want to be a troll. But I really want to understand what
is reasons for people to move to .NET. At least it is important for my
business future.

You have to answer the question I posed above, for yourself, and you
have to make an effort to learn what's available for .NET in your
application domain.

If you base your decision on your experience with Win32 and lack of
experience with .NET, then I think you're only fooling yourself.

-- Barry

--
http://barrkel.blogspot.com/
.

Relevant Pages

  • Re: Can MS listen to customers?
    ... IE is comprised of a set of libraries that other applications use. ... a HUGE portion of even a minimal install of Windows (or even in ... For Windows, Notepad, Paint, IE, OE, msconfig, Wordpad, Hearts, NT ...
    (microsoft.public.windowsxp.general)
  • [Full-Disclosure] Overflow in SunRPC-derived XDR libraries
    ... Applications using vulnerable implementations of SunRPC-derived XDR ... BSD-derived libraries with XDR/RPC routines ... Note that this vulnerability is similar to, but distinct from, ... Because SunRPC-derived XDR libraries are used by a variety of vendors ...
    (Full-Disclosure)
  • Re: display array in a frame wnd
    ... I have read some articles on document/view architecture (I began with this ... It takes me on line to create and display datas. ... window into which it is to generate its display. ... Most libraries I use just require a DC; ...
    (microsoft.public.vc.mfc)
  • Re: Shared libraries and modules
    ... another computer architecture which should have been built ... modules and libraries that pervades the computer world today. ... not want to have the code, say, for a "stack of widgets" being different ... If a program in a class-based language wished to ...
    (comp.sys.acorn.misc)
  • Re: Reading great code
    ... not aware of any mission-critical applications that use .NET, ... and libraries) or no operating system at all (except perhaps ... The C language, for example, can't be used ... more than Java is a prototyping platform. ...
    (microsoft.public.dotnet.languages.csharp)