C# over Java over C#...

Published 08-18-2007 8:55 PM | Agile_ph

Random thoughts...

No matter how hard I try (I'm probably not trying hard enough), I still go back to books or reading materials or anything about C# and .NET. I can't seem to study Java (seriously) even if my life depended on it. Stick out tongue

I'd like to think that there's just quite a few people out there who's brilliant at both C# and Java because of either preference or exposure to the language. Most of the time, you're good at one and not as good as the other...I might be wrong though.

On top of learning Java, I also have to learn the domain and adjust to married life and living on another country. "Whoever said it's going to be easy...but I never said it can't be done!"

Java doesn't have Get and Set accessors. What gives? I tried playing around with Java, I tried creating my own Jar and well...I said "that was quite easy. Of course, I haven't really tried the crazy stuff... "

Maven is a build tool while Ant is also a build tool. I will try to see why we're using one over the other and figure out how to use it.

Filed under: ,

Comments

# Lamia said on August 18, 2007 8:38 AM:

Consider yourself lucky to be even having to choice of using one build to over another. In my job, where most people are M$ fanatics I don't have much choice but to stick with their development tools(like SQLServer instead of Oracle). Yes, Java doesn't have the get/set method built-in in the language but you could create those yourself or have the IDE generate it for you with a few mouse clicks(Eclipse and Netbeans can do this). For me, having no default support for getters/setters is simplicity. And simplicity is beauty. :)

At this point of your life the only thing that matter now(I suppose) is how you will support your family. I know a little C# myself but then what I know is not enough to persuade me to switch to the .Net side.

Now this is a little misleading to say, especially from me who is complaining all the time why my company and my boss loves M$ so much. But "your technology should fit your company's' needs".