As you may have noted, Simple Thoughts sports an enhanced headline section with 4 tabs. They are: Headlines - Provides latest news we deem to be worthy of headline Hot Topics - Most popular news in the last 24 hours (from Google Analytics via free Gadging service) Most Voted - Most popular news ever based on your votes Most discussed - Most commented news in last 30 days

This blog is actively protected by Comment Guard Pro, WordPress Comment Spam protection plugin for pro-bloggers and semi-pro bloggers. We don't allow any spam, even apparently innocuous ones in this blog. Even with that, thanks to my readers, we are close to 10, 000 comments on this blog. There are currently 2,394 posts and 9,739 comments in this weblog.

When using enums in a switch, it is almost natural to assume they will be used like a regular switch. Unfortunately to accomodate enums, Java had to enhance its specification and enums in switch behave differently than regular switch statements in two significant and non-trivial ways.

Should we use to represent a constant String such as browser's user agent or simply use public static final String as before? Using public static final as enum has many problems, such as:

You may run Java processes in the foreground or in many cases they may be run using cron jobs or during system startup, as background processes. How can you find out stacktraces of any running Java process? But first how can you even know their name & process id's?