This is a detailed post explaining the reasons high groth of Orkut in India and why Facebook has now started gaining share in India. A must read for any one remotely interest in social networking.

I decided to move to KO3 and ditch the 2.3.x tutorial series. 1st part, configuring and creating a simple controller.

This is the home page for the First Class Methods (FCM) closures proposal for Java 7. The 'FCM' proposal consists of two parts - FCM and JCA. For clarity we recommend referring to the complete combined proposal as FCM+JCA.

Welcome to the first in a series of tutorials on Multi-Threading in C#. Before we even think about looking at any code, I think first, since this is the intro tutorial, we need to discuss what multi-threading is, and how it can benefit your application. We will also discuss some short falls in multi-threading capabilities.

This is a very basic review of active and available open source Java EE Application servers and Servlet container (Web containers) to let the community know which active containers are available and what is the general status of each container. The article can simply act as a start point for anyone need to select one of them for later use in development or product. Detailed comparison of these production cover many pages of a tick book.

One question that has been repeatedly asked is why JSR-310 wasn't simply the same as Joda-Time. I hope to expain some reasons here. Joda-Time as JSR-310? At its heart, JSR-310 is an effort to add a quality date and time library to the JDK. So, since most people consider Joda-Time to be a quality library, why not include it directly in the JDK? Well, there is one key reason - Joda-Time has design flaws. Now before everyone panics and abuses that line as a tweet, I need to say that Joda-Time is by far the best option curently available, and that most users won't appreciate the design flaws. But, I do want to document them, so the basis for the changes in JSR-310 is clear.

Today, Google announced the brand-new programming language, called “Go”. - golang.org This is a very impressive language for system researchers like me. It has pretty nice support for threading and networking. At first, I wrote the code to use “goroutine”, a light-weight thread prepared in Go. It only consumes several kilobytes per thread, so the programmer can create thousands of threads with littile overhead. This is very useful in writing networking codes (HTTPServer, ProxyServer, Crawler, etc.). I never want to write event-based server in C/C++.

Two computer programmers designed codes to falsify thousands of fake trade blotters and phantom records for swindler Bernard Madoff and took hush money to help keep the massive fraud going, U.S. authorities said. The FBI arrested Jerome O'Hara, 46, and George Perez, 43, at their homes on Friday morning on criminal charges of conspiracy for falsifying books and records at both the broker-dealer and investment arms of Bernard L. Madoff Investment Securities LLC (BLMIS) in New York. "The computer codes and random algorithms they allegedly designed served to deceive investors and regulators and concealed Madoff's crimes," said federal prosecutor Preet Bharara. "They have been charged for their roles in Madoff's epic fraud, and the investigation remains ongoing." O'Hara's attorney Gordon Mehler said "We intend to enter a plea of not guilty" after Manhattan federal court magistrate judge Ronald Ellis ordered the men released on $1 million bail each with travel restrictions.

After RubyConf 2006, I realized that Ruby was not on the right track for me. I went searching for a new language. I've been a JVM guy since '96, so finding a language that was as on the JVM was a plus for me. I was looking for a statically typed language with high performance, but with the syntactic economy of Ruby. I bounced around a couple of language listing sites and found Scala. Three years ago, I fell in total love with Scala. That love continues today. What is Scala to me?

MuleSoft released a brand new product, Mule Data Integrator, for graphical data mapping and transformation. Mule Data Integrator (MDI) is free for developers to use and includes an Eclipse-based designer that is fully integrated with Mule IDE.

jQuery is not just about Menus and Animation Effects. With jQuery you can also create attractive text effects and play with the text to communicate well with the users. With this collection, you can create text gradients, text fly effects, text glow and much more.

Countless times I’ve heard the argument that you should use the var keyword with caution, that it decreases readability of your code, or how it can be misused.

Gerrit, a Git-based system for managing code review, is helping to spread the popular distributed revision control system into Android-using companies, many of which have heavy quality assurance, management, and legal processes around software. HTC, Qualcomm, TI, Sony Ericsson, and Android originator Google are all running Gerrit, project leader Shawn Pearce said in a talk at the October 2009 GitTogether event, hosted at Google in Mountain View. The Gerrit story starts with the progressive escape of an in-house Google process and tool. Google requires code review for any change to company code or configuration files; there are a few exceptions, but those are subject to review after deployment. The code review process started out using lots of email, but for the past several years it has been automated. When Guido van Rossum, creator of the Python language, began working at Google in 2005, he started developing a tool, in Python naturally, to coordinate code reviews. The result, called Mondrian, lets users view the proposed change as a side-by-side comparison, and participate in comment threads attached anywhere in the code under review. An overview page shows a to-do list of incoming changes to review and reviewers' comments. Van Rossum presented Mondrian at a public talk in 2006.

There are 8 alternative Ruby VM's and 4 of them will hit 1.0 status in the upcoming year. A detailed look at the past year and where the community is heading (hint: it's an exciting time to be a Rubyist).

Google has released a release candidate version of GWT 2.0. They have also released a google eclipse plugin for GWT 2.0 which provides new UIBinder template support.

Bottlenecks to application scalability are a thorn in many architects' sides. Offloading the database and dumping the impedance mismatch with object caching is one answer, but that may require major changes to a company's data management environment. In an exclusive interview with DZone, Ari Zilka, the CTO and co-founder of Terracotta, Inc., explained how his company can solve scalability problems and ease the transition into the cloud.

This is why we jump out of our skin every time you tap us on the shoulder.

This morning I just installed Google OS Chrome on my Mac OS using Virtual Box. To my surprise, my first impressions are . . .

I created something at my job that has proven to be extremely useful that I think many people could benefit from. I like to call it Easy Partials, and the goal is to make using partials a bit easier (in case the name didn't make that glaringly obvious). The problem is that rendering a partial requires method calls when a little extra work will allow simpler and more readable partial invocation via convention. You are probably lost, so let me give you some examples. As it stands today, to render a partial you would do:

An interesting post about gzip compression on the web.

I'm not sure if I want all my data stored on the 'cloud'

Most commercial defect-tracking software vendors charge enormous licensing fees. Despite being “free”, these open source defect tracking systems have many features its expensive counterparts lack.

Users make mistakes, no matter how good your user interface is designed. But there is something you can do about it. There are approaches you can use to allow users to recover from errors, or even better to prevent errors. One such approach is called forgiveness. Let's explain it in more detail and see some inspiring examples.

Before we talk about Cloud, I want to quickly review where SOA came from. Most of us who started our IT careers in the 80s and 90s will clearly remember the pre-web Enterprise environment. Of course, so will everyone else - because that legacy is still with us. The typical systems were monolithic, complex applications that were completely self-reliant. Any interfacing with other systems was done through batch dumps. Applications grew and grew and grew into monsters because the only option was to enlarge the application - inter-application connectivity was too complex and unreliable to envisage.

In the relative short time that websites have been around, compared to other media, much has been learnt about web design. There aren’t any ‘rules’ beyond web standards and even then, they’re only guidelines. There are a number of other guidelines or rules that you should be adhering to when designing for the web