Attempting to create an intelligent entry about Linux for such a wide ranging audience is a bit like trying to compare a presentation on quantum mechanics for physicists while being readable by somebody with a junior high school education.

If you are a *NIX expert, then I suggest you keep on reading so you know how to explain this world to mere mortals.

I called it *nix for a reason. It represents a family of thinking. It is not unlike the difference between the language C and C++. Are there differences between the two? Certainly. And it is not like the difference between COBOL and C.

Years ago when I ran my own vo-tech school I would teach the students there are only two things in life. MS and *NIX. A friend of mine, a genius developer in her own right was aghast.

Memory management is always a priority in pretty much any programming language you would want to use. In the lower level languages such as C, there are a number of functions which help you manage the memory your application uses, but they are not the easiest to use. Some of the more modern programming languages such as Python, Ruby, Perl, and of course the subject of this article, Javascript all have a built in feature called garbage collection.

Garbage collection essentially means that the languages compiler will automatically free the memory being occupied by unused variables and objects, but there is no telling when this could occur. It is purely down to the compiler to decide when the garbage collection process should be initiated.

As part of our Java Tutorials program, we will list a number of interview questions to aid in a better understaing of Java and J2EE and, hopefully, provide a greater likelihood of getting a job.  Let us begin with the basics:

1. What is meant by J2EE?

J2EE is an abreviation for Java 2 Platform Enterprise Edition

2.  What is the purpose of J2EE?

The purpose of J2EE is to provide a component based platform in a multitier application model with transaction management, web services and reusable component support.

3.  What is the tier structure of the typical J2EE application?

A typical J2EE application consists of the following tiers/machines:  the client machine (browser/non-browser application), the J2EE server (an application server such as Oracle, JBoss, GlassFish, Tomcat) and a database.

With the skyrocketing popularity of Android and iOS operating systems, software developers got a whole new arena opened up. Many of the programmers have progressed to concentrate solely onto Mobile Technology Development. This is mainly due to the high demand as well as numerous lucrative ideas left to explore in the Mobile App world.

Exponential growth of smartphone users

As per the survey by eMarketer, the number of smartphone users across the globe crossed 1 billion almost two years ago. The expected number of smartphone users by 2014 end is 1.75 billion.

With smartphones, iPads and Tablets getting more accessible and less expensive day by day, the development potential for mobile apps is truly vast. The under-penetration in emerging markets like India and China in Asia shows that there seems to still a lot of steam left in the mobile app development industry.