Hi Robert,
(this is a report to the correct group I hope)
> So when you add it all up, it really doesn't look good for Delphi
> down the road. And especially not for Delphi NET which is already behind by
> two versions. Microsoft recently released NET 3.0 and there's no indication
> the next version of Delphi NET will even handle NET 2.0!
The next version of Delphi will handle .NET 2.0, and will also be able
to use all .NET 3.0 assemblies (but probably not with a designer for the
WPF and XAML stuff).
Note however that .NET 3.0 is a misleading name. .NET 3.0 can best be
seen as a set of add-on assemblies op top of .NET 2.0 (.NET 3.0 cannot
exist without .NET 2.0 - it's only extending it). The difference between
.NET 1.0 and .NET 1.1 was far bigger - since these resulted in different
.NET folders and different mscorelibs and different applications for
each version (1.0 or 1.1) of the framework. With .NET 2.0/3.0, I can
write a single application that will run on "both" frameworks. And you
will only have a single folder, so really it's *not* a new works. The
name .NET 2.1 would have been better, although .NET 2.01 might probably
be best.
This is just Microsoft marketing at its best, I guess ;-)
> Delphi, being a fan doesn't get the work done or impress those whom I work
> for. So I am going to continue straddling the fence until it becomes
> obvious that one side or the other has won out!
I'll be on the 'other side' of the fence then, throwing Delphi related
stuff (articles, tips, news, code snippets, etc.) over to you.
Wanna play catch? ;-)
Groetjes,
Bob Swart
--
Bob Swart Training & Consultancy (eBob42.com) Forever Loyal to Delphi
Blog: http://www.drbob42.com/blog - RSS: http://drbob42.com/weblog.xml
New Delphi 2006 Courseware e-books at http://www.eBob42.com/courseware
__________________________________________________
Delphi-Talk mailing list -> Delphi-Talk@elists.org
http://www.elists.org/mailman/listinfo/delphi-talk
