In this tutorial we are going to take a look at how you work with strings in Python. Now, any language worth its salt will have a number of options for working with text and Python is probably one of the best to use when it comes to processing text.

If you are new to programming in general you may be wondering what a string is. In terms of programming, a string is classed as any sequence of characters you can type with your keyboard, and let’s face it, if you want your application to be of any use to yourself or other users then you need it to tell you what it’s doing or to prompt you for an action, and that is where strings come into play.

They are your applications way of communicating with the user. Without the ability to enter and display text or software would be pretty useless.

So, how would you create a string in Python? Take a look at the following code:

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!

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 */

Computers. They’re a part of our everyday lives. Most of us couldn’t imagine living a day without them. We use them for school, work, and fun and use them to stay connected to those we love and care about. Since the invention of the web cam, millions of us use webcams to communicate with loved-ones and business contacts far away.

Web camera use has leveled the playing field for business entrepreneurs and given teenagers a fun way to chat with friends. However, solid citizens aren’t the only ones who make use of this popular modern technology. Recently, there have been reports of criminals using a type of webcam spy hack to insert themselves unseen into the living rooms and bedrooms of millions of unsuspecting users.

The Webcam Spy Hack

The most popular way criminals gain access to your webcam is through innocent-looking emails. You may receive an e-card from someone in your contacts list. When you click on it, you’re directed to another website to view the e-card. While you’re listening to music and watching animated puppies scroll across the screen, a Trojan horse is silently installed into your computer’s hard drive.