Windows XP really impressed me. With that and having heard of J#, I thought wow, that'd be great, because I like Java, but it's too irresponsive for GUIs and even though hand-coding GUIs makes nice code, I don't like it (using Eclipse for java). So I got a copy of VS.Net from campus, which goes for not so much.
At first I thought it was damn cool. You could just build your GUI very quickly by clicking around, the online help is nice and all, multi-monitor support is really good, etc. Then bugs started popping from everywhere and I found I was spending more time on writing workarounds than "real" code itself (or simply redoing dialogs because the IDE decided to forget about some). Then, when I had assignment demos to do for school, I was writing them in J#, but I had to redo the GUI by hand anyways, because you can't run J# on.Net by itself, you also need a redistributable for J#, which isn't installed in the computer labs. Deployment is also very complicated. You have to distribute the.Net and J# distributables along with your app, then if you want DB support, you need a third one and then your app by itself is already big...
So I just switched back to Java, where you just install one distributable sometimes, for machines that don't already have it. And then deployment is a joke, you just send a 50k jar and that's it. No 2-3 megs for simple apps! Sure the GUI's not too responsive, but I'm waiting for 1.4.2 eagerly now instead of wasting time on.Net.
I payed.Net from my pocket because I wanted to use it and at the end, the only thing I can say about it is that I got robbed. Eventually, it will mature up and if it gets accepted as well as Java, it might become interesting. But next time around, it's gonna be forced on me, I won't switch by will.
Slashdot Mirror
I would use paper and a pencil and then scan it. Just make sure you pick a nice scale so that you can do the math in your head.
On my usb pen drive, I've got...
Around 2 inches of dust.
Windows XP really impressed me. With that and having heard of J#, I thought wow, that'd be great, because I like Java, but it's too irresponsive for GUIs and even though hand-coding GUIs makes nice code, I don't like it (using Eclipse for java). So I got a copy of VS.Net from campus, which goes for not so much.
.Net by itself, you also need a redistributable for J#, which isn't installed in the computer labs. Deployment is also very complicated. You have to distribute the .Net and J# distributables along with your app, then if you want DB support, you need a third one and then your app by itself is already big...
.Net.
.Net from my pocket because I wanted to use it and at the end, the only thing I can say about it is that I got robbed. Eventually, it will mature up and if it gets accepted as well as Java, it might become interesting. But next time around, it's gonna be forced on me, I won't switch by will.
At first I thought it was damn cool. You could just build your GUI very quickly by clicking around, the online help is nice and all, multi-monitor support is really good, etc. Then bugs started popping from everywhere and I found I was spending more time on writing workarounds than "real" code itself (or simply redoing dialogs because the IDE decided to forget about some). Then, when I had assignment demos to do for school, I was writing them in J#, but I had to redo the GUI by hand anyways, because you can't run J# on
So I just switched back to Java, where you just install one distributable sometimes, for machines that don't already have it. And then deployment is a joke, you just send a 50k jar and that's it. No 2-3 megs for simple apps! Sure the GUI's not too responsive, but I'm waiting for 1.4.2 eagerly now instead of wasting time on
I payed