网上看到，或是收集的一些JavaOne 2005的照片。 无缘去JavaOne 2005，只能从blog或是flickr里面看看现场的情况了。
|
Happy Birthday, Java |
Gosling
|
|
The birthday Cake |
Microsoft
|
Bea
|
Nokia |
|
|
Java
|
Popularity: 13% [?]
第二天，就没有那么多的新消息发布了，更多的是大量有趣的技术主题报告。 主题发言中，最引人注目的，可能还是Sun的首席执行官，Scott McNealy 的演讲了。 Scott当然不会忘了Java是这次年会的主角（而不是他），所以，他尽量的阐述了如何利用Java技术（当然不仅仅是Java语言）来搭建这个被数字化割断的（"the digital divided"）世界之间的桥梁，如何使用Java技术在教育，医疗等方面提高生活的质量:
"He talked about all the efforts to apply Java technology around world (both from within and outside of Sun) to improve quality of life in such areas as education and healthcare. By providing great opportunities for people outside the company to participate and contribute to the technology via communities Sun has grown far beyond the physical boundaries of its corporate walls. "-- Steven Harris's Blog
为了表达对James Gosling的尊敬，放映了一部回顾James Gosling的短片，都是同事，家人和朋友对这位Java之父说的一些话。 James在他自己的blog中，写到：
"….was a video that some folks put together about me and the past 10 years. They got a pile of old video clips and photos, and they interviewed many of the people I've worked with and for. And they got my wife and daughters in on the scheme to contribute their own segments. I don't know how they managed to keep it a secret (particularly my 7 year old), but they did. Thanks everyone! --- James Gosling
Java这个计算机语言，在10年前不经意的创建了，如今10年过去了，它还是这样令人兴奋，并且极大的影响着这个IT界，真让人难以相信。
JavaOne的技术讲座安排的非常非常满，很多有趣的主题都在相同的时间段里面而互相重叠。 第二天的技术讲座包括了Sun刚刚开放源码的GlassFish系统，也就是Sun的Java EE Application Server Platform 9。 在Day 1的eBay做过了技术讲座之后，Day 2则是Amazone，主体都是和Web Service有关，而重点则是Java （以及Sun公司）对Web Service的支持（说实话，Java对Web Service的支持还是不够，或者说由于有JCP，对Web Service的反应有些慢，不如.Net平台，但是这次JavaOne2005页有Microsoft参加，主题就是讨论Java平台和.Net平台上，Web Service的互操作性问题。
Wicket，这是一个有趣的东西。 Wicket是什么？ 一个新的Web Application Framework （市面上的WebApp Framework这么多了，还要Wicket干什么？）。 是由几个原JSF团队（可能现在还是）的工程师设计的。 其主要的思想就是，把代码从HTML中剥离出去，象Swing那样设计页面。 简单的说：HTML+Swing的想法+一点点Tapstery的想法。 每个HTML文件对应于一个POJO，那些复杂的动态内容，form的处理都交给POJO，在Java里面处理。 在HTML中，使用特定的Wicket ID命名不同的HTML组件（比如一个label，一个输入框），然后POJO就可以控制这个HTML了。 早几天，我在Eclipse里面尝试过几个Wicket的例子，过些日子写些体会和感受。
更多关于JavaOne 2005的消息，可以通过Technorati查询JavaOne，你会得到很多关注JavaOne 2005的blog。
Popularity: 14% [?]
Happy 10th birthday, Java and JavaOne.
Java终于扔掉了那个名字中的2了。 不管是初学Java还是一个Jave的资深程序员，可能谁也不会忘记这个2字: Java 2 Standard Edition，Java 2 Enterprise Edition。 从1998年起，这个2字就加在Java的版本号上了，那为什么要加这个2呢？ 很多人曾经困惑过：Java 2 Standard Edition 5.0，到底是2.0版还是5.0版？
终于，Sun决定要把这个困扰了很多年的2字去掉了，而且要在这周的JavaOne 2005年会上，在Java 10周年的时候，给Java正正名了:
而且，将把版本号定位为只有一个数字。 也就是说，J2SE 6.0现在叫做： Java™ Standard Edition 6 或者 Java™ SE 6 （注意：这里没有那个2了）。 那么未来的版本呢？
出于其他原因，旧的版本还保持不变：比如J2EE 1.4, J2SE 5.0, J2SE 1.4.x, J2SE 1.3.x等等。当然，你也可以把J2SE 5.0（a.k.a Tiger）叫做Java SE 5（但是谁在乎呢？）
Sun关于改名的全文，见：Building and Strengthening the Java Brand
Goodbye "J2SE", Hello "Java SE"
Popularity: 11% [?]
这是Artima Developer的总编 Bill Venners对Erich Gamma的采访中的第四部分。在前三部分中，Bill和Erich讨论了如何思考和使用Design Pattern，灵活性以及可重用性和 如何对Interface编程以及使用使用object composition而不是类继承
在第四部分中，Bill和Erich讨论了设计模式如何与解决问题相配对，设计模式如何帮助你理解问题解决得意图，以及如何通过练习成为一个好的设计师。
[Update: 一些心得]:
如何成为一个好的设计师？理解这些设计模式是不够的，仅仅只读完了GoF这本书也是不够的。还需要做甚呢？你需要练习，需要看代码，看其它好的设计师是如何设计系统的。
In addition to reading books, you need to read and understand lots of code, see how existing systems solve a particular problem and what experienced designers did. Basically what design patterns do is to tell you what these developers have done. But, just reading about it isn't enough. You become a master by mimicking the work of excellent developers. ….. Not only do you learn about a particular development process you will also learn how to communicate about a design in a group of developers. As a good designer you not only come up with good designs you also communicate and defend them. You have to practice, like an apprentice in a way. Over time you'll become as experienced as experienced designers.
作为一个新手，就算理解了GoF中的所有设计模式，也还是不够的，重要的，要知道，在什么时候，什么情况下，使用什么样的patterns。 而这往往是非常难的。 通常只有完成了之后，仔细思考自己的设计和代码的时候才会发现需要使用某个模式，或者某一种模式使用错了。 这个时候，就需要使用"重构"技术，来应用你觉得正确的模式。 只有练习再练习。
记住这句话：look to the master, follow the master, walk with the master, see through the master, become the master…
Popularity: 9% [?]
Kirill Grouchnikov wrote an very interesting blog: "You say Eclipse, I say IBM". He gives some factors:
So, his conclusion is:
They can babble all they want about gazillions of members on Eclipse board, but the fact still remains - it's open source (as much as Sun's projects on java.net), but it's powered exclusively by IBM.
And he also mentioned that from 3.1M2, each milestone release and each RC release, the file size of the Eclipse-SDK is becoming bigger and bigger (from 88MB to 102MB). The 3.1RC3 is now more than 100MB. I also noticed this, but I am not surprise. Eclipse is not just an Java IDE, it is a platform, there're quite a lot plug-ins (including JDT, PDE, etc.) and the ZIPPed source code.
Kirill is an Eclipse user, "using Eclipse for 10+ hours each day for the past 2.5 years". His concern is interesting, and I also agree with him that the Eclipse should not be growing bigger and bigger. I guess Eclipse may learn something from Linux: The Linux kernel is small. But after packaged by RedHat or SuSE, the Linux distribution is very big. Leave the packaging work to other service providers, Eclipse may just provide the basic.
Reading the comments by others is another interesting thing. I do agree with some comments saying that "I think what you have uncovered is the often ignored fact that most major 'open source' projects are being developed by paid employees". Not only Eclipse, but other projects are doing the same way. For example, WTP now is mainly programming by BEA; BIRT is now mainly programming by Actuate; and others. Yes, I do believe that the major contributor is still IBM. And I am like to see IBM has so much contributions. IBM "created" Eclipse, and most of IBM's software product (WSAD, Rational, Lotus Notes) now are on Eclipse. IBM does want to contribute more, not only for Eclipse itself, but for IBM's products.
You may say IBM is dominating the Eclipse, but I won't say IBM is dominating the Eclipse Foundation. Eclipse is not a product, but a community. IBM will not and is not able to dominate a community.
Popularity: 13% [?]
