车东@FlickR posted a photo:

关于留言：
不发送（缺省），即时通知，每天通知，每周通知；

关于朋友的更新： 全部友邻 || 仅限朋友
不发送（缺省），及时同时，每天通知，每周通知；

今天是上海2008年春季英特尔信息技术峰会（IDF）的第一天。多少年来，每一次出席IDF，我都能感受到一种前进的强大力量，今年也同样如此。参会人数与届俱增，创新成果推陈出新，摩尔定律在延续。本届IDF上，全新的MID（也就是移动互联网设备）的发布，下一代Nehalem微处理器的披露……一系列激动人心的消息，让我和上海IDF的数千名与会者一样，兴奋不已。

上午9点多钟，我为IDF致了一个开幕词。其中有一个我自己非常喜欢的环节，那就是我满怀敬意地与大家一起，共同回顾了2500多年前的“越王勾践剑”。同时将“越王勾践剑”与英特尔的45纳米技术和产品进行了类比，这就是所谓的“芯剑传奇”。两者之间的吻合之处，在于都凝聚着当时卓越、创新的人类智慧，辉耀着挑战科技极限的创新光芒。上海IDF的主题叫做“芯动力，新世界”，其本意也是要揭示这一点。

1965年，承载着“卧薪尝胆”历史沧桑的文物“越王勾践剑”在湖北荆州出土。让人惊奇的是，这把青铜宝剑穿越了两千多年的历史长河，但剑身依然光芒耀世、丝毫不见锈斑。经过科学分析，发现铜剑之精良，主要在于其独特的复合金属材料和锻造工艺。它是用铜、锡，以及少量的铅、铁、镍、硫等材料制成，而且它通过复合金属浇铸工艺让剑脊含铜较多、剑刃含锡量高，使剑身更有韧性、不易折断，同时保持了剑刃的硬度和锋利。正是因为突破“刚”、“柔”相济极限的青铜配方，巧夺天工的复合金属铸剑工艺，才使“越王勾践剑”历经2500年地下埋藏与侵蚀而不锈，堪称是中国古代工匠的一大创造。

当今，英特尔“创芯”与越王“铸剑”竟有着相似的创新智慧和异曲同工之妙。45纳米的技术突破是怎样实现的呢？首先是一改使用了近40年的多晶硅栅极金属氧化物半导体（MOS）材料，创造性地使用了基于铪的高-K栅介质和金属栅极晶体管材料，在取得更高运算性能的同时，极大减少了漏电，从而功耗进一步下降，芯片散热问题也得到极大改善。其次是生产制造工艺方面的突破，英特尔45纳米双核处理器集成了4亿1千万个晶体管，四核处理器则集成了8亿2千万个晶体管，这么高的集成度，在十年前、二十年前简直不可思议。

正是归功于这些新材料和制造工艺上的革命性创新，英特尔才能不断突破集成电路的能效极限，推出尺寸更小、性能更强、能效更高的芯片，并最终促成了今天以互联网应用为核心、超便携、节能环保的MID的诞生。也正因为英特尔有这样的创新实力支撑，在今天上午上海IDF的讲台上，我才有足够的信心向大家承诺——英特尔将按既定计划推出下一代32纳米处理器系列，并在2010年前将英特尔处理器的平均耗电进一步降低50%！

从两千多年前的“越王勾践剑”，到今天的英特尔“酷睿芯”，两者都具有材料和生产工艺的独特性，相似的是创新的智慧，永恒的却是敢于突破、不懈创新的科技精神。英特尔公司成立40周年的历史，归根结底也就是持续追求创新的历史。今天，上海IDF全场闪耀着创新的光芒；未来，英特尔还将继续与产业界携手，不断在技术、应用和客户体验上传扬这一不变的科技创新精神！

In Infoworld’s article, Java performance improvements touted quoted:

As your program grows in size, the lack of strong typing basically kills your ability to handle a very large program and so you don’t find the million-line Perl program.

In response, chromatic said:

the reason that there aren’t many million-line Perl programs is that the people who are capable of writing and managing million-line Perl programs have better ways to organize their projects than glomming a million lines of Java into a single shared-everything instance.

My reflection and thoughts:

1. Interestingly, why the pick on Perl? not Python or Ruby or Lisp-flavoured ones?
2. s/Perl/PHP/g or s/Perl/Python/g etc. on chromatic’s quote still valid and sound;
3. Java => Strong typing? Not necessarily always;
4. IntelliJ IDEA is the only reason I still code in Java, Eclipse? that would be another post;
5. Vim (together with some bash scripts and esvn) has been my primary “IDE” for projects that involve php, python, bash and javascript;
6. I have written Perl applications before, and would be very happy to pick it up for my next project if everything else fits (e.g. the team factor);
7. When would I code in Java? most likely a project that:
   • being “enterprisy”, or
   • I am really interested to learn, explore and apply, e.g. Antlr.

We've always encouraged other developers to adopt Atom, the Atom Publishing Protocol, and the extensions that Google has created on top of those standards, but we realized the issue of patents may have held back some adopters. Well, those concerns end today as we are giving a no-charge, royalty-free license to any patents we have that you would need to implement Atom, AtomPub, or any of those extensions. Here is a link to the exact license text.

Now the official way to announce such a license for specifications under the IETF is to register them in the IETF IPR Disclosure Database. You can read the disclosures yourself in the IETF Disclosure Database.

Google's extensions are also covered by this patent license, and you can find a link to them on the bottom of the authentication schemes AuthSub and ClientLogin on our core Google Data extensions and Common Elements, and on the following Data APIs:

• Google Apps Email Migration API and Provisioning API
  
• Base Data API
• Blogger Data API
• Calendar Data API
• Code Search Data API
• Contacts Data API
  
• Documents List Data API
• Notebook Data API
• Picasa Web Albums Data API
• Spreadsheets Data API
• YouTube Data API

We hope this will encourage sites who want to expose APIs for things like photos, videos, calendar, or contacts to reuse our schemas where they can, rather than reinventing the wheel.