Delphi 2007 Handbook








March 15, 2007

Microsoft Retires Visual Jsharp

Microsoft has an interesting way of killing one of the Visual Studio personalities.

I know, this is not new as the announcement is dated January 10, 2007. But I noticed it only some time ago and forgot to blog about it. The news is that Microsoft is removing J# support from Visual Studio. But instead of saying "killing", "removing", "terminating"... they say they are "retiring it". Also, they claim this is because users don't need any new features. I find this very amusing:

Retirement of J# language from future versions of Visual Studio

Since customers have told us that the existing J# feature set largely meets their needs and usage
of J# is declining, Microsoft is retiring the Visual J# product to better allocate resources for other
customer requirements.

Guess what? CodeGear could tell us that the existing Kylix features set largely meets our needs, so they are retiring it... CodeGear might learn from this style, but I'm pretty sure a similar announcement from them would trigger rage in the non-tech newsgroup.

Another interesting element is that Microsoft pushed J# as a way to "convert" big telecoms and financial institutions from Java to .NET. Killing J# looks like another sign that this never happened and .NET is not making big inroads in similar companies. Too bad that the Together support in Delphi is based on J#, which is hey you need to install it among the prerequisites. Anyway, Microsoft promises 8 more years of support, so that will keep working for some more time.

posted by marcocantu @ 0:41AM | 7 Comments [0 Pending]




 

7 Comments

Microsoft Retires Visual Jsharp  

  Illustrates why  competing Tool vendors dont 
really want to be leveraging MS technology for their 
own products in the way that has occurred with 
Borland/Codegear and the Together support in Delphi. 
To easy for them to 'pull the rug from under you'.
Just my $0.02 Worth :-)
Comment by on March 15, 23:45

Microsoft Retires Visual Jsharp  

Well, we all know that DOT NET is the Java killer!! 
Just read the MS forums and the comments from the 
Microsoft zealots!

Is it possible MS and the worshippers of Redmond 
were actually wrong? Nah, can't be. We all know that 
everyone has switched from Java to NET and from 
Linux/Unix to Windows.
 
Comment by Steven Global on March 16, 00:56

CodeGear have done their own retiring..  

How else would we describe what has happened to 
Turbo _Professional_ ?

J# did at least have a fair stab at life.  Turbo 
Professional wasn't even a year old when CodeGear 
"retired" it without even having the good grace to 
admit - how ever prosaically - that this is what 
they were doing, and insisting that nothing had 
changed.
Comment by Jolyon Smith on March 16, 02:25

Microsoft Retires Visual Jsharp  

... the existing Object Pascal features set largely 
meets our needs, so we are retiring it.  Welcome to 
PHP.
Comment by Ann Tique on March 16, 05:22

Microsoft Retires Visual Jsharp  

 J# or Kylix, both companies have said the same 
thing - not enough people care, and any time and 
money spent on them would have so poor a ROI that it 
would be utterly wasted.

Honestly, very few care about either product and some 
third party component vendors has confirms exactly 
this problem with Kylix.

No market.
Comment by Xepol on March 16, 07:02

Microsoft Retires Visual Jsharp  

Not sure anybody seriously used it... ever
Comment by Geek on better solutions [http://sb2.info] on March 27, 02:05

Microsoft Retires Visual Jsharp  

 I think Borland (Code Gear) can consider to create 
Borland J#. They can say Microsoft will support J# 
any more. I feel there is a need for a "Java" 
compiler in .net.

Role777
Comment by role 777 on August 13, 19:50


Post Your Comment

Click here for posting your feedback to this blog.

There are currently 0 pending (unapproved) messages.