Skip navigation

jst

9 posts
We all know that the JDK is big and it ought to be smaller. The question is how to make it smaller and still keep backward compatibility with existing applications. 

I think I know how to do it, I did something similar to NetBeans APIs five years ago. Thus I started a little experiment to split JDK into pieces. As that might influence the shape of your favorite libraries, I welcome you to help me or share your thoughts.

Visit Modular Java SE to join!

I have just finished the bridge between Spring and Lookupand prepared a demo application to demonstrate what it can be useful for. In my opinion this is the kind of component injection as JDK6 likes it. Your opinion?  

For a while I was desperately expecting an important moment. Since I wrote the Practical API Designbook, and since its amazon page was created, I've been waiting for first customer review. Almost daily, at least at the beginning, I was watching whether it had already appeared or not. I always opened the book's page being afraid of what I would find. I feared to see something like unreadable, boring, not interesting for Java programmers, unreadable for English speaker. Yet, at the same time, I could not resist to expected the first review, hoping it will not be so cruel. Today I have found out that the first review is there.

I no longer remember what exactly I was expecting, but this reviewcompletely exceeds any of mine expectations. Thanks mathboyfor your evaluation. I like how the reviewstarts, I like how it progresses and I like how it ends. For those who do not have time to read ithere is short summary: Just get the book now, until it is out of stock!

I guess I can now be satisfied to have written the book. And thanks for teaching me about Scrooge.

jst

Accept Unacceptable Blog

Posted by jst Jan 10, 2009
When you maintain some code and you get a patch that you do not like, what can you do? Is the only option to refuse the change, or is there a better way? Of course, as this was just a rhetorical question, there is better solution: Just create a code slot!  

3 Sides to Every API is my reaction to excellent Beauty matters summary provided PetrHejl. It is my attempt to agree with him, while defending Practical API Design's often proposition that beauty does not matter...

NetBeans Performance team is proud to co-contribute to the success of NetBeans IDE 6.5, the latest and greatest release of NetBeans IDE of all times. Although the performance was not a major theme for the 6.5 release we are glad we managed to do improvements in various visible areas. We are also fond of stiffening the verification framework that we use to prevent regressions, so the likelihood of losing all those hardly extracted milliseconds and kilobytes is lowered for current and future releases. Read more and enjoy NetBeans 6.5...  
The longest, most detailed and insightful review I have seen so farhas been written by Tim Band for Lambda The Ultimate.  
jst

Cultural Context Leakages Blog

Posted by jst Oct 20, 2008

Recently I've been warned that my sidebar in Chapter 4, Ever Changing Targets talks about events that are completely ununderstandable for international readers. That made me write a short essay about leakages of cultural contexts and the similarities with the API Design.

Today I am ready to announce a really nice addition to the collection of weird examples of APITypes. Did you ever suffered with compiler optimizations? Did you ever thought about them as being an example of an API?