Tweet
Btw: Confucious say, "Work smarter, not harder."
As for C#, it's slated as the "Java killer". I believe that as much as I believe Delphi killed Visual Basic. (in case you didn't know...it didn't)
What I wouldn't be surprised about is if they ended up just jockeying each other back and forth on new features, kind of like the relationship of PHP to ASP.
I've heard that Java would have more to copy from C# than C# would have to copy from Java, but I have seen nothing convincing in that regard.
But I'll sum it all up right now: The idea of language-neutral code- Good Thing. In the real-world it's a Nice feature- and that's it.
It's a whole hell of a lot less important than they like to pretend, and will lead to some incredibly stupid ends. Writing a program in more than 1 language is like writing a book in more than 1 language- you can, but why the hell would anyone think that's actually a good idea?
At most you should have 1 main language and 1 minor language, like Java and C++ (for instance). But the fact is, Java not only has the potential, but it already does it! That's what the Java Native Interface is for!
But the JNI does kind of suck to use, or so I've heard, but already there are products which act like a wrapper to do the work of JNI even better, such as functionX (I think it's called that...).
Other than the fact that Microsoft is interested only in dominance and nothing more (and willing to use any tool to obtain it, which has varying effects on The Rest of Us), Java has years of a head-start and Sun has said many times they want to release it as totally open-source when the option becomes a good one (they say they haven't done so to protect some company from coming along and producing a proprietary version of it, ie- Microsoft).
In the words of a wise man, "Good software takes 10 years" http://www.joelonsoftware.com/articl...000000017.html
And C# isn't even really "out" (ie, not beta...but then again, MS products never go out of beta...hee, hee, hee) yet, compared to Java's maturation time.
It'll be at least 2 years before C# becomes a truly Good Idea, if not 3-5 years. Assuming it "takes", which it likely will. .NET is a lot bigger of a gamble, but if MS doesn't go extinct then it will stick too. They're resilient bastards, to speak highly of them, and they'll keep releasing new versions, each time slightly growing it's popularity.
But it won't kill Java, though it may however 'kill' Delphi. But the majority of java's turf will stay under java, and the majority of MS's turf will migrate to C#, which might be good for all of us.
C# may even be worth learning, but not now, and could be a fun thing to play with or even use. But hell, Java 1.4 finally fills out almost all my demands for a language - along with all the other java development products I desire - so I'm quite positive it'll be quite the long time before C# manages that.
I do look forward to third-party support for Java in .NET though, and there are many iiiiiiinteresting plans for reverse-engineering C# itself, if not .NET along with it.
If someone adds PHP support somehow too, that'd be excellant too. But as I said, it'll be a few years before C# becomes a viable choice.
As for C#, it's slated as the "Java killer". I believe that as much as I believe Delphi killed Visual Basic. (in case you didn't know...it didn't)
What I wouldn't be surprised about is if they ended up just jockeying each other back and forth on new features, kind of like the relationship of PHP to ASP.
I've heard that Java would have more to copy from C# than C# would have to copy from Java, but I have seen nothing convincing in that regard.
But I'll sum it all up right now: The idea of language-neutral code- Good Thing. In the real-world it's a Nice feature- and that's it.
It's a whole hell of a lot less important than they like to pretend, and will lead to some incredibly stupid ends. Writing a program in more than 1 language is like writing a book in more than 1 language- you can, but why the hell would anyone think that's actually a good idea?
At most you should have 1 main language and 1 minor language, like Java and C++ (for instance). But the fact is, Java not only has the potential, but it already does it! That's what the Java Native Interface is for!
But the JNI does kind of suck to use, or so I've heard, but already there are products which act like a wrapper to do the work of JNI even better, such as functionX (I think it's called that...).
Other than the fact that Microsoft is interested only in dominance and nothing more (and willing to use any tool to obtain it, which has varying effects on The Rest of Us), Java has years of a head-start and Sun has said many times they want to release it as totally open-source when the option becomes a good one (they say they haven't done so to protect some company from coming along and producing a proprietary version of it, ie- Microsoft).
In the words of a wise man, "Good software takes 10 years" http://www.joelonsoftware.com/articl...000000017.html
And C# isn't even really "out" (ie, not beta...but then again, MS products never go out of beta...hee, hee, hee) yet, compared to Java's maturation time.
It'll be at least 2 years before C# becomes a truly Good Idea, if not 3-5 years. Assuming it "takes", which it likely will. .NET is a lot bigger of a gamble, but if MS doesn't go extinct then it will stick too. They're resilient bastards, to speak highly of them, and they'll keep releasing new versions, each time slightly growing it's popularity.
But it won't kill Java, though it may however 'kill' Delphi. But the majority of java's turf will stay under java, and the majority of MS's turf will migrate to C#, which might be good for all of us.
C# may even be worth learning, but not now, and could be a fun thing to play with or even use. But hell, Java 1.4 finally fills out almost all my demands for a language - along with all the other java development products I desire - so I'm quite positive it'll be quite the long time before C# manages that.
I do look forward to third-party support for Java in .NET though, and there are many iiiiiiinteresting plans for reverse-engineering C# itself, if not .NET along with it.
If someone adds PHP support somehow too, that'd be excellant too. But as I said, it'll be a few years before C# becomes a viable choice.
hehe, i'm so excited!
Come on, if you can quote surely you can read. I guess you're gonna be the one to make that next OS with java... with no dirty tricks huh!
Comment