Re: About speed


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.

It is simple for understand. But I mean - new platform must simplify
develpment. But according to arguments used by you and others (including my
own expirience in Delphi.NET) I cannot see if it become simple. Seemslike it
become simple only for usual tasks, which enough simple with VB or Delphi
standard VCL development. Probably except ASP.NET (I cannot compare it with
another platforms like Java, Ruby etc due to lack of expirience).
But as only you move to complex tasks it becoem not only not simple but even
much and much complex as for understanding as for implementing (I mean - if
you need to check additional interface to allow your object to be disposed
right, implement right methods for dispose resources, etc - is is
simplifying from simple Create/Destroy model? Seems like not.
If you need to keep in mind - object will be boxed so you mostly must avoid
to use object-type properties if you not want to lost perfomance etc etc. It
seems like not simple way.
Well, any person can form a habit with any even complex ways (I work with
ActiveX and OLE and sometime I cannot understand when it complex for
somebody). But it mean only one for me - each technology is best for
specified tasks only. Probably .NET too. At least as you said it is best for
Web development.

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.


Same words can be said for any language. You may find a lot (I think even
more) libraries for Delphi Win32 or C (even not C++). The most sinetific
libraries can be found on Fortran. Business - on Cobol. So I do not think it
is serious argument.


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.


Yes, I understood. Every can do the same if he can and must. Even me.


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

Yes of course I speak about serious tasks. Simple tasks can be done even in
VB or any another language.

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.

Could not agree. .NET show BIG difference in architecture from Win32 so my
knowledge of algorithms works for Win32 was need fully changed for .NET So
it is quite uneasy to create right architecture if you not a guru in that
platform. Previous expirience may not help even worse.


On the other hand, you need less knowledge about Win32 development.

Yes of course. But I already have it. Since Win 3.1 development. So it is
not a problem for me, like for any developer who work more than 5 years.


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

Where?

Alex


.

Relevant Pages

  • Re: creating windows
    ... >> supports, and the OP didn't state what platform he wanted, did ... While he is reading his news on a Win32 ... the newsgroup and the one who asks. ... > not cross platform libraries. ...
    (comp.lang.cpp)
  • Re: So what Standard are we working off?
    ... If portability doesn't matter, why bother using C? ... I can write a Win32 ... And then there are libraries. ... of which platform I'm using, than have to learn a separate library for each ...
    (comp.lang.c)
  • Re: Why wont this 17 line program link?
    ... Platform: Win32 ... You don't only have to tell the linker where your libraries are, ... of your project and, on the linker tabs, look for "additional libraries" (or ...
    (microsoft.public.vc.mfc)
  • Re: Adding Win 32 to a MFC program
    ... want to be able to use the win32 into my MFC application but it give ... THis looks like the api for the WinSock 'connect' call ... What does the documentation of 'connect' tell you about it? ... but a failure to include libraries that are expected and used by the other "program". ...
    (microsoft.public.vc.mfc)
  • glext++
    ... The purpose of the library is to provide Yet Another OpenGL Extension ... Initialization Library and platform abstraction between ... libraries existed. ... These methods are related to context creation and abstracting platform ...
    (comp.graphics.api.opengl)