J# finally bites the dust
-
:(( All those years of intensive J# study down the drain. Whatever shall I do?! ;P
:josh: My WPF Blog[^]
-
Serious question? J# is an implementation of the Java language and libraries, version 1.1, for the .NET CLR, including Microsoft's proprietary extensions that were what caused Sun to withdraw Microsoft's right to produce Visual J++. As such, the J++ feature set was pretty much locked-off as of version 1.0. It was intended for people to migrate their J++ applications to .NET, but in practice, people found that migrating them to C# was just as easy or even easier. See for example this case study[^].
Stability. What an interesting concept. -- Chris Maunder
-
ad3z wrote:
the language is declining.
Why is it declining? It obviously isn't meeting some need, right? Marc
People are just notoriously impossible. --DavidCrow
There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer
People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh SmithMarc Clifton wrote:
Why is it declining?
J# served one purpose: to move Java projects to .NET easily. I used it to convert a large Java project to the .NET world relatively painlessly. But no one wants to maintain that in the long run. Its usage is declining because now those projects are being moved to a first class .NET citizen language, like C# or VB.NET.
Tech, life, family, faith: Give me a visit. I'm currently blogging about: The Lord's Prayer in Aramaic song (audio) The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
-
Serious question? J# is an implementation of the Java language and libraries, version 1.1, for the .NET CLR, including Microsoft's proprietary extensions that were what caused Sun to withdraw Microsoft's right to produce Visual J++. As such, the J++ feature set was pretty much locked-off as of version 1.0. It was intended for people to migrate their J++ applications to .NET, but in practice, people found that migrating them to C# was just as easy or even easier. See for example this case study[^].
Stability. What an interesting concept. -- Chris Maunder
Mike Dimmick wrote:
but in practice, people found that migrating them to C# was just as easy or even easier
I disagree. I just ported a large Java app over to a J# winforms app and it was easy. I tried converting to C#, but there were so many tedious manual conversions to work out, it just wasn't worth it.
Tech, life, family, faith: Give me a visit. I'm currently blogging about: The Lord's Prayer in Aramaic song (audio) The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
-
well thats good cos its been biting a*s ever since it was unleashed on the world if ever there was a more pointless development product from ms ive yet to discover it :cool:
"there is no spoon" {me}
-
I could see that one coming, last week I had a discussion with a fellow consultant on the usage of J# and it seems we were right, it isn't popular.
WM. What about weapons of mass-construction? "What? Its an Apple MacBook Pro. They are sexy!" - Paul Watson
I expected it not to last long. I couldn't see it as being any more than a transitional migration tool for the few J++ apps that were around.
-
A sad day for the three people still using J#... :-O
--Mike-- Visual C++ MVP :cool: LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ Ford, what's this fish doing in my ear?
-
That is amazing to me. I would not think MS would "drop" any language for .NET as it tries to be everything to everyone. Does not seem like it would take that many resources to keep the language where it is for years to come. Guess Java people are more comfortable just moving to C# :)
Rocky <>< Latest Code Blog Post: OpenID/CardSpace - Is it time? Latest Tech Blog Post: Corel Lightning - what is the plan?
-
I expected it not to last long. I couldn't see it as being any more than a transitional migration tool for the few J++ apps that were around.
-
Since customers have told us that the existing J# feature set largely meets their needs and usage of J# is declining Doesn't that seem, um, contradictory? If something meets your needs, wouldn't you expect to see usage increasing? :rolleyes: Marc
People are just notoriously impossible. --DavidCrow
There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer
People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh SmithI think that it's something like 5 developers are using it and are content with what the language has to offer. 5 developers is too few justify development costs, so they stop producing it. (Ok, 5 developers is indeed a bit on the extreme side, but you get my point)
WM. What about weapons of mass-construction? "What? Its an Apple MacBook Pro. They are sexy!" - Paul Watson
-
Since customers have told us that the existing J# feature set largely meets their needs and usage of J# is declining Doesn't that seem, um, contradictory? If something meets your needs, wouldn't you expect to see usage increasing? :rolleyes: Marc
People are just notoriously impossible. --DavidCrow
There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer
People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh SmithI actually read that as "largely met their needs". It was a conversion helper, not a serious development platform. All I can say is: About time.
cheers, Chris Maunder
CodeProject.com : C++ MVP
-
Some of the features like java.util.zip etc are really very useful and excellent.
Vasudevan Deepak Kumar Personal Homepage Tech Gossips