One of the biggest challenges in pursuing a career in software development is to figure out which language you want to work. In addition to commonly used software programming languages like C, C++, Java a lot of new programming languages such as Python, Ruby on Rails have surfaced especially because they are used by a lot of consumer based start-ups these days.

With so many front and back end languages, the choice of learning Java is a failsafe decision and mastering Java can ensure that you have a bright future in software programming.

What is Java

Java is a computer programming language that is designed to be platform independent meaning that the language can virtually run on any hardware platform. This platform independence and an object oriented framework make Java the preferred language of development especially for client-server web applications.

I remember the day like it was yesterday. Pac Man had finally arrived on the Atari 2600.  It was a clear and sunny day, but it was slightly brisk. My dad drove us down to the video store about three miles from our Michigan house. If I remember correctly, the price for the game was $24.99.  It was quite expensive for the day, probably equaling a $70 game in today’s market, but it was mine. There *was* no question about it. If you purchase a game, it’s your game… right?

You couldn’t be more wrong.  With all the licensing agreements in games today, you only purchase the right to play it. You don’t actually “own” the game. 

Today, game designers want total control over the money that comes in for a game. They add in clauses that keep the game from being resold, rented, borrowed, copied, etc. All of the content in the game, including the items you find that are specifically for you, are owned by the software developer. Why, you ask, do they do this? It’s all about the money.

This need for greed started years ago, when people started modifying current games on the market. One of the first games like this was Doom. There were so many third part mods made, but because of licensing agreement, none of these versions were available for resale. The end user, or you, had to purchase Doom before they could even install the mod.  None of these “modders” were allowed to make any money off their creation.

In May 2012 Google Chrome hit a milestone. It kicked Microsoft's Internet Explorer into excess phone oh that oh that second place as the most used browser on planet Earth.
With Microsoft being in second place, it makes a dark hole for Firefox coming in at number three. Google likes to trumpet three key reasons: security, simplicity and speed.
Available for free on Android, Linux, Mac, and Windows. It gets its speed from the open source JavaScript engine written in C++ known as V8.
In my daily use I use Microsoft's Internet Explorer version 10, Apple's Safari (on OS X) and chrome on both Windows 8 and OS X.

Admittedly people do not know anything about Internet Explorer version 10 since you can only get it on Windows 8/RT.

I do not need a crystal ball to know that the Mother of All Browser Battles is set to begin in the fall of 2012 and beyond.

I have said this before and I'm going to say it again.

The Zen of Python, by Tim Peters has been adopted by many as a model summary manual of python's philosophy.  Though these statements should be considered more as guideline and not mandatory rules, developers worldwide find the poem to be on a solid guiding ground.

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!