Java or .Net
I'm writing this entry while reading a book titled "C# for Java Developers".
Java is cool, but I'm tired of having to learn 5 different ways of doing one thing. Not only playing a guessing game of possible solutions, but once picking a solution, books tell you to wrap the solution up in a facade, adding more complexity to your application.
That's not to say that patterns are patterns, in any language, but with .Net you are left with the confidence of a strong single leader, Microsoft. Sun and Java, on the other hand, is led by commitee. Smart people are tossing API's out there left and right that are nothing more than ideas-- J2EE for example. Again, I'm left with picking a vendor/solution for every "idea" they throw out there.
With Microsoft, things are pretty much set in stone via the tools they provide. This is how .Net handles MVC, this is how .Net handles Database access, this is how .Net cooks a turkey.
I would feel more confident know that our implementation was written on a single standard versus constantly wondering if we made the right pick of persistent frameworks a month after finishing a project.
Java is cool, but I'm tired of having to learn 5 different ways of doing one thing. Not only playing a guessing game of possible solutions, but once picking a solution, books tell you to wrap the solution up in a facade, adding more complexity to your application.
That's not to say that patterns are patterns, in any language, but with .Net you are left with the confidence of a strong single leader, Microsoft. Sun and Java, on the other hand, is led by commitee. Smart people are tossing API's out there left and right that are nothing more than ideas-- J2EE for example. Again, I'm left with picking a vendor/solution for every "idea" they throw out there.
With Microsoft, things are pretty much set in stone via the tools they provide. This is how .Net handles MVC, this is how .Net handles Database access, this is how .Net cooks a turkey.
I would feel more confident know that our implementation was written on a single standard versus constantly wondering if we made the right pick of persistent frameworks a month after finishing a project.
posted by Jacob Hookom at
9:42 PM
3 Comments:
Oh boy, c´mon, do you want persistence? It´s called JDO. Do you want MVC? It´s the analyst´s job to write the models, and there´s something called Swing to help you out. Do you want to cook a turkey? It´s called... Java! Java is truly multiplatform, and J2ME is there for your cooking abilities.
You say, "how .Net do this or that" but it´s only if you´re writing bytecode my friend, and I bet you aren´t. There´s a C# way of doing this, a VB.Net way of doing that, a ASP.Net of not doing anything, a "managed c++" way of doing nothing and even a J# way of doing I don´t even imagine what.
But wait, it´s not over yet, our circus is just beginning, you can even transmutate your code to something called C#+ASP.Net or VB.Net+ASP.NET!
They thought "code maintenance nightmare" was enough, but microsoft brought the newly avaliable "Code Maintenance Armagedom", only for you!
Hey man, nothin against .Net, I´m reading the same book, but if you don´t know what is best for your needs, you will have BIG trouble when you face something you´re not used to. If you always need someone else to say what is good or bad, you´re not going too far.
By
Anonymous, at 5:54 PM
wow...pretty harsh comments. I think hookum will go somewhere...maybe you should just eat-a-dick-up Mr. Anonymous!
By
Anonymous, at 9:26 AM
To the harsh pro-java poster, you obviously have no clue how .NET works do you? All of these languages are, put simply, choices that you don't have with java... Because once compiled, it's all MSIL. You're used to VB's synthax? No problem, we have VB.NET. Like java or C better? No problem, we have C#.
Another BIG advantage of .NET: the IDE. But hey, if you like to spend 10000 hours manually modifying complex XML files just to "hook" your pages to code, good for you! I'll be drinking a beer while you do so, since i finished that same project in .NET months ago...
By
Anonymous, at 3:20 PM
Post a Comment
<< Home