If you’re interested in building modern websites or applications which use ASP, XML, or mobile technology, you’ve heard of Visual Studio .NET.  It is one of the more popular suites of development tools available to aspiring programmers, as it consolidates several different tools and languages into the same development environment, which helps in turn to integrate this code across development languages.  Here are three important benefits to using the visual studio suite:

·         Use of Visual J# - This development tool is specifically oriented towards people who already are familiar with basic Java syntax, and is designed for use by those people to build apps or services which will then run on the Microsoft .NET Framework.  This is useful because it fully supports Microsoft Extensions, among other reasons.  Visual J# was developed completely independently by Microsoft.

·         Utility for Smart Devices – Another huge benefit of using visual studio .NET is the ability to immediately integrate your programming efforts with deployment across a variety of smart devices.  PDAs, smartphones, Pocket PCs, and any device which has a limited amount of resources all require a compact framework for the programming of applications it is designed to run.

·         XML Web Usage and Support – Because XML services aren’t married to any particular technology or programming language, they can be accessed by any system, and this broad-based utility has made the services increasingly popular.  Visual Studio .NET takes advantage of this by fully integrating with XML services, including the ability to create and edit them from scratch.

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.

Although the index is an important itemized guide of what people are searching for on the internet, it’s arguable that certain languages getting recognition is a direct result of early adopters posting tutorials and filling up discussion boards on current trends. Additionally, popular tech blogs pick up on technological shifts and broadcast related versions of the same themes.

When does the popularity of a software language matter?

1. If you want marketable skills, knowing what employers are looking for is beneficial. As an example, languages such as Java and Objective C are highly coveted in the smart-phone apps businesses.
2. A consistently shrinking language in usage is an indicator not only that employers are apt to pass on those skills but fall in danger of being obsolete.
3. Focusing on languages that are compatible with other developers increases your chances to participate on projects that companies are working on.

I will begin our blog on Java Tutorial with an incredibly important aspect of java development:  memory management.  The importance of this topic should not be minimized as an application's performance and footprint size are at stake.

From the outset, the Java Virtual Machine (JVM) manages memory via a mechanism known as Garbage Collection (GC).  The Garbage collector

• Manages the heap memory.   All obects are stored on the heap; therefore, all objects are managed.  The keyword, new, allocates the requisite memory to instantiate an object and places the newly allocated memory on the heap.  This object is marked as live until it is no longer being reference.
• Deallocates or reclaims those objects that are no longer being referened. 
• Traditionally, employs a Mark and Sweep algorithm.  In the mark phase, the collector identifies which objects are still alive.  The sweep phase identifies objects that are no longer alive.
• Deallocates the memory of objects that are not marked as live.
• Is automatically run by the JVM and not explicitely called by the Java developer.  Unlike languages such as C++, the Java developer has no explict control over memory management.
• Does not manage the stack.  Local primitive types and local object references are not managed by the GC.

So if the Java developer has no control over memory management, why even worry about the GC?  It turns out that memory management is an integral part of an application's performance, all things being equal.  The more memory that is required for the application to run, the greater the likelihood that computational efficiency suffers. To that end, the developer has to take into account the amount of memory being allocated when writing code.  This translates into the amount of heap memory being consumed.

Memory is split into two types:  stack and heap.  Stack memory is memory set aside for a thread of execution e.g. a function.  When a function is called, a block of memory is reserved for those variables local to the function, provided that they are either a type of Java primitive or an object reference.  Upon runtime completion of the function call, the reserved memory block is now available for the next thread of execution.  Heap memory, on the otherhand, is dynamically allocated.  That is, there is no set pattern for allocating or deallocating this memory.  Therefore, keeping track or managing this type of memory is a complicated process. In Java, such memory is allocated when instantiating an object:

String s = new String();  // new operator being employed
String m = "A String";    /* object instantiated by the JVM and then being set to a value.  The JVM
calls the new operator */