IDE's and other development tools for programmers...are NOT meant to be cheap programs for Joe Blow
What about Emacs? I've used Visual Studio.Net, JBuilder, and a boat load of other professional IDE's, and while I like some of their features, IMHO Emacs is still the best for speed, quality, and flexibility of use.
I have no interest in debating what you or I think are great software
I agree that one of the key features of.net is it's full featured IDE. with ms visual studio, the vb "leisure coders" can still write their small apps utilizing countless global variables all with names like jkl1, jkl2, etc. But it's also easy (and encouraged of course) to write and manage large OO projects written in several languages.
If you're a real programmer, then you probably already know at least two languages and it wouldn't be too hard to migrate from, say, java to j#.net with a learning time of somewhere between a week and a month ( with a good book ).
Now, about the shared objects between languages, while.net makes this simple (as long as all the other languages are.net and the os is windows), there are currently models implementing cross platform, cross language object and interface sharing. The one that comes to mind is XPCOM.
Slashdot Mirror
IDE's and other development tools for programmers...are NOT meant to be cheap programs for Joe Blow
What about Emacs? I've used Visual Studio .Net, JBuilder, and a boat load of other professional IDE's, and while I like some of their features, IMHO Emacs is still the best for speed, quality, and flexibility of use.
I have no interest in debating what you or I think are great software
sorry, my bad.
--Joe BlowI agree that one of the key features of .net is it's full featured IDE. with ms visual studio, the vb "leisure coders" can still write their small apps utilizing countless global variables all with names like jkl1, jkl2, etc. But it's also easy (and encouraged of course) to write and manage large OO projects written in several languages.
If you're a real programmer, then you probably already know at least two languages and it wouldn't be too hard to migrate from, say, java to j#.net with a learning time of somewhere between a week and a month ( with a good book ).
Now, about the shared objects between languages, while .net makes this simple (as long as all the other languages are .net and the os is windows), there are currently models implementing cross platform, cross language object and interface sharing. The one that comes to mind is XPCOM.