Future of Java
summary
Describes a randomized DSL test framework that runs billions of generated operation sequences against a control case and 42 bugs found which become regression tests, explains a startup acquisition process that picks priorities over top price, shows a production system processing 3 billion SMS/hour on 16 CPUs, and demonstrates Java work: value types cutting 600MB to 40MB and 7s to 2s, small-string ≈85% memory reduction, and proposals for 64-bit arrays and GC specialization.
AI-written summary · about
chapters (12)
- 0:00Start
- 5:00Powerpoint Magic
- 5:31The Seven Habits of Highly Effective People
- 5:42Begin with the End in Mind
- 9:25Fiduciary Responsibility
- 15:52What Is Dsl
- 32:27Embrace Criticism
- 34:19Golden Ratio
- 36:20Complexity Is the Enemy
- 42:08Always Do What You Know To Be Right
- 47:30This Is an Example from John John Rose Showing How Point Could Be Implemented It Looks Pretty Much like a Java Class Not the I Made a Bold near the by Value That's Kind of the Only Difference Really and the Fact that the Compiler Would Know that It's Immutable so I'Ll Give an Example with some some Work That We Were Doing in a Similar Vein We Did the Same Thing with Say Long Values Which Is a Pretty Obvious Easy One and You Can See 600 Meg's of Ram Down to 40 Megabytes Seven Seconds Ton to Two and a Half so some Pretty Dramatic Optimizations Are Possible and this Is all Done in Pure Java
- 48:22Now There Are Strings a Great Example of another Thing You Can Do with Value Type So Small String for Example Could Be Done Entirely in Line so no Separate Char Array for Example They'Re Still Figuring Out the Details of How They Could Do this but Check this Out Single Location so that Drops the Number of Objects in Half for Strings Single Cache Line because It's all You Know the String and Its Contents Are all in One One Cache Line if It's Small Enough and We'Ll Talk about Arrays To Out a Minute but Here's an Example That We Did with Strings It Wasn't As Good because It Was Actually Slower
