The diagram below is what I came up with. I’ve tried to narrow down the most important flags that will solve 80% of JVM performance needs with 20% of the tuning effort.
(Full Story: Java Tuning in a Nutshell – Part 1)
Apart from being the second highest growth language on GitHub next to CoffeeScript, Java – already the language with the second most associated tags on Stack Overflow – outpaced the the median tag volume growth rate of 23%. This growth is supported elsewhere; on LinkedIn, the Java user group grew members faster than every other tracked programming language excepting C# and Java. This chart, for example, depicts the percentage of LinkedIn user group growth for Java and JVM based alternatives since November of 2011.
(Full Story: The RedMonk Programming Language Rankings: February 2012)
1. Distributed development, layers of frameworks, and Java’s modeling limitations make it easy to create bloated data designs.
2. In this environment, awareness of costs is essential for making informed tradeoffs.
3. Some tradeoffs can be made without sacrificing speed or sound design.
4. The concept of data structure health – the ratio of actual data to its representation – can illuminate where there is room for improvement, and point out aspects of a design that will not scale.
A presentation by Attila Szegedi titled “Everything I Ever Learned about JVM Performance Tuning @twitter” has been floating around for a few months. I’ve restructured much of the content into a set of notes. This covers the basics of memory allocation and garbage collection in Java, the different garbage collectors available in HotSpot and how they can be tuned, and finally some anecdotes from Attila’s experiences at Twitter.
(Full Story: JVM Performance Tuning (notes) : twitter)
Java is still pretty darn cool: consider the widespread applicability and excellent engineering behind the JVM platform, the clarity of syntax, the rich ecosystem of tools and libraries and the fact that Oracle says there are over 9 million Java developers out there
Method of reading / writing files should be the same no matter what the file format is.
Programmer should be shielded from the files format.
You should be able to edit files using the files description (Cobol Copybook, Xml or what ever).
Package should be flexible – easy to add new file formats or Record-Layout formats.
(Full Story: JRecord)
Flat files. Much as we live in an XML/SOAP/Web Services world, there’s still a ton of data being moved around between proprietary and legacy applications that consists of fixed length fields delimited by EOLs. Around about the time I wrote my 20th Java class who’s only purpose in life was to suck up a flat file, use String.substring to break it up into pieces, and then populate a bean with it, I decided there had to be a better way. This package represents the fruit of that frustration.
(Full Story: From Java to Node.js)
Here is Dice’s list of the top 10 software skills in demand as of January 2012:
Java/Java EE developers