Results 1 to 7 of 7

Thread: who uses J#?

  1. Jul 4th, 2002, 04:12 PM #1
    MrPolite
    MrPolite is offline

    Thread Starter
    l33t! MrPolite's Avatar
    Join Date
    Sep 2001
    Posts
    4,428

    who uses J#?

    I just went to microsoft.com and they had J# for free (you have to have a part of VS.NET to use it).... I'm just wondering if anyone is using this "unheard melody"?
    MS is getting crazy, what's the point? I never quite understood the point of making C# neither, it's almost same as VB.NET
    now what's the point of J#?! just to support Java people?
    rate my posts if they help ya!
    Extract thumbnail without reading the whole image file: (C# - VB)
    Apply texture to bitmaps: (C# - VB)
    Extended console library: (VB)
    Save JPEG with a certain quality (image compression): (C# - VB )
    VB.NET to C# conversion tips!!
    Reply With Quote Reply With Quote
  2. Jul 4th, 2002, 04:38 PM #2
    Dillinger4
    Dillinger4 is offline
    Dazed Member
    Join Date
    Oct 1999
    Location
    Ridgefield Park, NJ
    Posts
    3,418
    Micro$oft seems to get crazy with this stuff. It seems just like an attempt to pull Java developers over to their side. Im really torn between wether i like the idea of Micro$oft having J# and wether i hate the idea. I learned Java because i wanted to learn somthing "non-microsoft" but i kept up with visual basic because of job security issues and even more so now since Sun Micro seems to be having internal problems as a company. But ive always been afraid that what if somthing happens to sun and all i know is java? So i guess Micro$oft having J# is a good idea. As long as it is not much different.
    Java CodeBank Entries >>

    Parsing URL's    | Collections/ShuffleElements |
    Threads isAlive()     | Daemon Threads |Remote Class Loading | Sorted Keys (Map) | Backwards List | Thread States | Collections/Arrays Generics | Regular Expression(Grouping and Capturing) | Properties | JLabel/JTextField Combo | Reading Request Parameter Values | Host Lookup | Setting the size of a JFrames inner-region | GUI Native L&F


    Reply With Quote Reply With Quote
  3. Jul 4th, 2002, 04:40 PM #3
    MrPolite
    MrPolite is offline

    Thread Starter
    l33t! MrPolite's Avatar
    Join Date
    Sep 2001
    Posts
    4,428
    oh well... I guess it feels safe to be with microsoft
    rate my posts if they help ya!
    Extract thumbnail without reading the whole image file: (C# - VB)
    Apply texture to bitmaps: (C# - VB)
    Extended console library: (VB)
    Save JPEG with a certain quality (image compression): (C# - VB )
    VB.NET to C# conversion tips!!
    Reply With Quote Reply With Quote
  4. Jul 4th, 2002, 04:42 PM #4
    Dillinger4
    Dillinger4 is offline
    Dazed Member
    Join Date
    Oct 1999
    Location
    Ridgefield Park, NJ
    Posts
    3,418
    Java CodeBank Entries >>

    Parsing URL's    | Collections/ShuffleElements |
    Threads isAlive()     | Daemon Threads |Remote Class Loading | Sorted Keys (Map) | Backwards List | Thread States | Collections/Arrays Generics | Regular Expression(Grouping and Capturing) | Properties | JLabel/JTextField Combo | Reading Request Parameter Values | Host Lookup | Setting the size of a JFrames inner-region | GUI Native L&F


    Reply With Quote Reply With Quote
  6. Jul 4th, 2002, 05:10 PM #5
    hellswraith
    Guest
    The reason that MS puts all these different languages out is so that developers will be able to EASILY adapt to .Net from their past languages. This is simple, the more people they get developing with .Net, the better it is for them.

    C# is targeted towards VBer's, C++ people, and Java people. As a matter of fact, I see plenty from each one of those languages in C#. This is really good. This means you get the best from 3 different languages. But maybe a Java developer that spent all that time learning the ins and outs of Java dosen't want to reinvest that much time learning a new language. J# will allow them to put their skills to use much quicker than if they were to switch to C# and have to learn all the little syntax changes and such.

    It is all subjective. I will use what ever the employer wants me to...lol. But I prefer C#.
    Reply With Quote Reply With Quote
  7. Jul 4th, 2002, 06:04 PM #6
    Dillinger4
    Dillinger4 is offline
    Dazed Member
    Join Date
    Oct 1999
    Location
    Ridgefield Park, NJ
    Posts
    3,418
    Yes exactly. I think it is good because if one switches over to J# because they had too they would probably just have to adapt a little. But i think unless people are forced to switch from Java to J# for what ever reason or they are completly new to Java and start J# from scratch that will be the only way they will use it.
    Java CodeBank Entries >>

    Parsing URL's    | Collections/ShuffleElements |
    Threads isAlive()     | Daemon Threads |Remote Class Loading | Sorted Keys (Map) | Backwards List | Thread States | Collections/Arrays Generics | Regular Expression(Grouping and Capturing) | Properties | JLabel/JTextField Combo | Reading Request Parameter Values | Host Lookup | Setting the size of a JFrames inner-region | GUI Native L&F


    Reply With Quote Reply With Quote
  8. Jul 4th, 2002, 08:04 PM #7
    Ahriman
    Ahriman is offline
    Member
    Join Date
    Apr 2001
    Location
    Hamilton, ON, Canada
    Posts
    43
    i think the whole idea behind J# was to make the APIs similar to the Java APIs so java devs wouldn't have to relearn the C# or .NET APIs

    C# is basically Java that uses the .NET APIs
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules


Click Here to Expand Forum to Full Width