An Invitation to .NET developers to travel the Open Roads

  • Thread starter Thread starter asj
  • Start date Start date
Hi ASJ,

I found this in this page,
-----------------

Here's another look at the list, and again Java dominates the list, with
smatterings of C++, Perl, Python, and C. There was not one single C# book in
the entire top 25, nor any Visual Basic books.

-----------------

My personnal opinion was also that the documentation on MSDN was pretty
good.

Cor
 
Cor said:
Hi ASJ,

I found this in this page,
-----------------

Here's another look at the list, and again Java dominates the list, with
smatterings of C++, Perl, Python, and C. There was not one single C# book in
the entire top 25, nor any Visual Basic books.

-----------------

My personnal opinion was also that the documentation on MSDN was pretty
good.

Cor
Click to expand...

Nice call, but remember, this list is the product of the /most popular/
not the most *intelligent* .
 
In comp.lang.java.advocacy, Travis 'Bailo' Bickel
<[email protected]>
wrote
Nice call, but remember, this list is the product of the /most popular/
not the most *intelligent* .
Click to expand...

Or the highest performance, or the cheapest, or the best.

An interesting problem, but one that's probably not going to be
answered with a mere Amazon.com bookscan. It is also far
from clear that a simple benchmark answers all, either; Java
has heavy startup times but once it's in memory, it appears that
it flies. .Net's startup is probably faster, but currently it
can only run on x86 equipment. (That may change as GNU's
dotNET effort gets rolling.)

And then there are issues if one already has a Microsoft
infrastructure. .NET slips right in; Java may require
some conversion work. (At least, in theory. And who in
their right mind would use Microsoft for *new* work, given
all the malware flying around already?)
 
The Ghost In The Machine said:
And then there are issues if one already has a Microsoft
infrastructure. .NET slips right in; Java may require
some conversion work. (At least, in theory. And who in
their right mind would use Microsoft for *new* work, given
all the malware flying around already?)
Click to expand...

LOL - ya got that right....but all is not well just because you're a
microsoft shop - just look at all the VB and ASP developers
complaining about difficulties moving to dotnet- it sucks to be a
hamster in the microsoft treadmill ;-)
 
In comp.lang.java.advocacy, asj
<[email protected]>
wrote
LOL - ya got that right....but all is not well just because you're a
microsoft shop - just look at all the VB and ASP developers
complaining about difficulties moving to dotnet- it sucks to be a
hamster in the microsoft treadmill ;-)
Click to expand...

The flip side of backwards compatibility is actually being compatible. :-)

The last time Java had major problems (other than missing classes,
AFAIK) is during the alpha3-beta1 switchover, many many moons back.

Of course one issue with VB/ASP => .NET is that a lot of VB/ASP is
not compiled until the website is browsed by a webbrowser, whereas
with .NET everything has to be precompiled.

Presumably, this is mostly an issue with dynamic method lookup on objects.
In ASP it's simple to write

obj.name(p1,p2,...)

and if obj is an object, name() is queried for, called, and the result
returned.

Obviously not compatible with strong typing -- although I don't know if
ASP.NET enforces strong typing, or not.
 
Back
Top