Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
Ever struggle with what to write? No worries, we've got you covered. Here's a list of Java prompts and article ideas to help cure even the worst cases of writer's block. So, take a moment, check out the prompts below, pick one (or more!), and get to writing.
Also, please feel free to comment on this post to bounce around ideas, ask questions, or share which prompt(s) you're working on.
I had the opportunity to meet with Georges Sabb, V.P. Software Development, Java Platform Group; Donald Smith, Sr. Director Product Management; Sharat Chander, Sr. Director Java Product Management and Developer Relations; Chad Arimura, V.P. Developer Relations, all with Oracle, and Aimee Lucido, Java Engineer, and author of Emmy in the Key of Code, following the announcement of the general availability of Java SE 13 (JDK 13) as part of the six-month feature release cadence.
After four-plus years of trying to get Oracle to provide insights for the Java Research Guides I've been conducting for DZone.com, I was pleased that they want to reengage with the developer community.
Hi, Spring fans! Welcome to another installment of This Week in Spring. This week, I’m in sweet San Francisco, soaking up the sun and enjoying the fun of summer. Sure, I’ve got a few meetings, and appearances, etc., but it is very nice to be home. By the way, I’ll be speaking at the upcoming San Francisco Java User Group — come hang out and say hi!
Anyway, lots of good stuff (as usual), so let’s get to it.
The Java VM flag -XX:+AggressiveOpts was deprecated in JDK 11 [see JDK-8199777 and JDK-8199778] "because its behavior is ill-defined." The "Problem" section of JDK-8199778 further explains (I added the emphasis):
AggressiveOpts has been used as a catch-all method of enabling various experimental performance features, mostly targeted to improve score on very specific benchmarks. Most things it affected have been removed or integrated over time, leaving the behavior of the flag ill-defined and prone to cause more issues than it'll solve. The only effect that the flag currently has is setting AutoBoxCacheMax = 20000 and BiasedLockingStartupDelay = 500. Both can be done manually by setting the corresponding flags on the command line.
According to the document "Java HotSpot VM Options," the -XX:+AggressiveOpts flag was added with J2SE 5 Update 6 to "turn on point performance compiler optimizations that are expected to be default in upcoming releases."