Slashdot Mirror


J#

fuze writes: "It's basically a way for Java developers to migrate their Java apps to .NET.... even provide a 'convenient' migration tool... check it out on MSDN." News.com has a story describing Microsoft's plans to suck Java into .Net, and some commentary saying basically, "No one will use it".

5 of 337 comments (clear)

  1. Re:What will they think of next? by Anonymous Coward · · Score: -1, Flamebait

    English, motherf*cker, do you speak it?

    J# ISN'T another language. It's just that Sun sued Microsoft, so MS can't use the "Java" word (and which is why they had to drop Visual J++, more's the pity, as it was easily the best Java IDE out there).

  2. Michael# by Anonymous Coward · · Score: -1, Flamebait
    Michael# - it's a way of migrating Michael to having a clue.

    Why am I not surprised that this lame story is posted by Michael the Gay?
    What in the name of hell does J# have to do with Open Source?

    Slashdot - now your source for all lame Microsof&#174 news.

  3. Re:.NET = component-based programming on the Inter by Anonymous Coward · · Score: -1, Flamebait

    .Net locks you into an OS and a tool provider??? Bahahaha, you haven't been paying attention at all, have you? Loser.

    And the difference between J2EE and .Net is that one of them is fucking hard to use and the other is as easy as falling off a log. Competition will see that J2EE is eliminated fairly soon. Bye bye, dinosaur.

  4. Re:.NET by Anonymous Coward · · Score: -1, Flamebait

    No... that's called CORBA. MS and .NET suck. :)

  5. Could we have slightly less sun propaganda? by Zeinfeld · · Score: 1, Flamebait
    Hey folk, before prostrating ourselves at the shrine of Sun's 'open standard' remember that Sun has exclusive control over the future of that language.

    The whole Java thing was more in Sun's interest than the developers from the start. In return for a somewhat better objective extension of C than C++ you wrote your code so it would run on Sun hardware as well as Intel and it would run at a tenth the speed on both. JIT compilers closed the gap somewhat but there is still a major performance penalty. A good C coder will write faster code than a good java coder.

    The 100% pure stuff is ridiculous. If I am writing a program to run on Windows I want to make use of the extensive APIs. I want the program to look and feel like a windows program, and definitely not like a Java applet.

    Sure platform independence is a good thing, but it should not be forced. Sun's little tantrum was about preventing people writing the programs they wanted to in 'their' language. So Microsoft have invented their own. I don't give a hoot about running on Solaris, Linux and NT are the only platforms I can be confident will be mainstream in 5 years time. Sun will go the way of the rest of the *nix hardware vendors in the end. (and blame their bad management on Gates to the end).

    There is not a great deal of innovation in C#, but there wasn't much in Java either. The big step forward in both comes from junking bits of C that were really bad ideas.

    There are a number of features of C# that make it much better to write programs for manipulating XML etc. than Java. If I did not anticipate ever wanting to port to another platform (and did not think C# for linux would arrive) I might use J#.

    In the meantime J# means that you can still use Java to teach intro to programming.

    --
    Looking for an Information Security student project suggestion?
    Try http://dotcrimeManifesto.com/