Microsoft opening up .NET

[Terry Fox]

I just started messing with Java a little, in order to make some 
functionality work on a program under Linux that it was **supposed** to do 
already.  This is a program that supposedly worked in both Windows and 
Linux.

I may have had a unique experience, but I spent a week fighting Java (and 
eventually Eclipse) just trying to get things to build.  It was "deprecated 
this", "deprecated that", wrong version class library, wrong javac, wrong 
java, etc.  I'm glad that "they" don't say "write once, run everywhere" with 
Java anymore.  It just ain't true.  Java 1.6 is different than Java 1.7, and 
1.8 is different still - and all have incompatibilities that prevent 
previously working code from running on the later version.

I'm not a software weenie, I have enough problems keeping up with where the 
Linux distro gurus have moved libraries to (that break running code).  I 
don't need the language gods breaking their code as well.

While I'm concerned about a language that thinks of whitespace as 
significant, I have had a MUCH easier time understanding and writing in 
Python than I have with Java.  Even though I am a C (or assembler) guy at 
heart.  We don't need no stinkin' pluses(++) or sharp(#) signs!  And I don't 
drink no coffee neither...
73, Terry, WB4JFI


-----Original Message----- 
From: Mike O'Dell
Sent: Sunday, November 16, 2014 9:52 PM
To: Terry Fox
Cc: tacos at amrad.org
Subject: Re: Microsoft opening up .NET


Most of the Windoze programs you'd really like running
cross-platform are still written primarily in C++ and
are tightly bound to the Win32 API. Even if the CLR -
Common Language Runtime - runs on multiple platforms,
it's very unclear how the Win32 API calls get handled.
That is what Wine and such do and I doubt seriously
that's going away any time soon.

that said, Microsoft *is* working hard to make Office
genuinely cross-platform for some definition of that term.
So far, that means Office 365 available on multiple platforms
with the exception of Office for OSX. it seems that the
codebase for the OSX version is actually ahead of the
Windoze version. Maybe that means moving some or a lot
of it to CLR/.NET - maybe not.  I suspect Office is at
the heart of the strategy, though, because it has
long been the case that the primary reason the vast
majority of Windoze users ran it was to run Office.
It's Office people want, *not* Windows. I think the new
guy gets it - put Windows on everything reasonable and
just collect the money - don't argue about what kind
of car they bought - just take their money.

It is the case, though, that Java is the unassailble
standard in the Enterprise Software World. MS completely
missed the boat by playing hard to get.
The ready cross-platform availability of Java
let it simply explode. There are far more Java
developers in the world than .Net or native Windoze.

That's unfortunate because C# had
the advantage of looking at several years of Java experience
and then avoiding some of the design "challenges" in Java.
so out the chute, C# was a better language and CLR had
much better support for dynamic dispatch languages than
the JVM. The JVM stuff has been fixed and many, if not all,
of the misfeatures in Java have been fixed or at least
ameliorated.

The tragedy is that this could have happened at least
10 years ago if Balmer had not been CEO. Why fight the
next war when you have so much experience fighting the
last one?

It will certainly be interesting to see what happens, though.

BTW - in the latest ACM survey, the instructional language
that is rapidly displacing Java in intro CS courses is

     PYTHON!

they do more, they learn more, and enjoy it more.

Most of Facebook and Amazon Web Services is written in Python.

     -mo