洋 的个人资料A Better Day照片日志列表更多  |  工具 帮助 |
|
7月18日 看了《我是传奇》 《我是传奇》镜头中多次出现蝴蝶，查了查才知道于原来蝴蝶是有寓意的。它是上帝身边九个堕
天使其中之一----昔拉的化身。他的能力很特殊，外形是一只蝴蝶，有着强大的攻击力，也是上帝用
来惩罚恶人，惩罚其他天使的“杀手”，他的力量大到让上帝怜悯被害者。
传说在第一次诺亚造方舟 ，他曾出现过一次，瞬间造出洪水淹没世上的一切。 还有，末日审判 前3天，他也参与并杀死人类总数1/3。 这个天使是危险，狂暴的，没人知道他的身世，人们说的杀
手的化身，就是昔拉。
他的力量就是让人绝望！ 它也就是大名鼎鼎的“杀戮天使”——KillingAngle 看《我是传奇》时，全片充斥着一种绝望的末日气氛，无论是纽约荒废的街道和黑夜的诡异，“绝望”两
个字贯穿着影片始终，当安娜向Neville说还有一个安全地时，Neville绝望的向她大吼到：“不可能！
全死光了！”
当Neville送全家人上车准备离开纽约时，他的小女儿做了一个手势并说道：“ mummy，look at it. It's a butterfly. ”（妈妈，你看，是一只蝴蝶），这里的蝴蝶想必便是昔拉的寓意了。
影片进行到Neville驾车经过纽约市区时，一幕很有趣的镜头出现了——一辆坦克上闪过一个蝴蝶的海报， 旁边标注着一行字：“God still loves us”，是的，上帝依然还爱着人类，只是上帝抛弃了人类，上帝
怜悯但绝不同情。
影片到了最后，那个吸血鬼老大在玻璃上撞出一个蝴蝶图案时，很明显的昭示出那个吸血鬼BOSS 其实就等同于昔拉的化身，人类不断僭越上帝的禁区，从克隆到基因改造，终于因为超越大自然本身的自然
进化而受到了惩罚。
还是不错一部电影。呵呵 至少，我知道了 昔拉。
梦断代码 和摩天大楼、水坝等永久性建筑一样，桥梁体现了人类对物理世界的技术把握。在过去半个世纪里，软件成为构建这个
世界的虽不可见但却深入渗透的人造物。“人类文明运行于软件之上”，广为应用的计算机语言C++发明人比昂纳·斯卓思柯普
（Bjarne Stroustrup）这样说道。
初听起来，这像是奇谈怪论或是自卖自夸。即便没有Microsoft Windows，人类文明也会同样延续，对吧？然而，
软件并不只是用来发电子邮件或写报告的程序那么简单；它已经不声不响地渗透到生活的每个角落。它存在于厨具里、
汽车中、玩具里、建筑中。商业和银行、选举和新闻媒体、电影和交通网、医疗和国防、科研和基础公共服务——人类
生存之所需都系于计算机代码这根易断的细线上。
而且我们要为其脆弱埋单。根据国家标准和技术学会（National Institute of Standards and Technology）
2002年的研究，软件错误每年造成美国595亿美元的经济损失，三分之二的项目明显延误或超出预算，甚至干脆无疾
而终。
人类文明运行于软件之上。但是，软件创建艺术却隐于暗处，即便对于专家们也是如此。在历史上，我们从未如此地
完全依赖于这样一种人类自己不知道怎么才做得好的产品。在对软件系统的加速依赖和踱着方步学习怎么做好软件之间，
有一条巨大且有时叫人恐惧的壕沟。对软件的依赖以指数级增长，而做软件的技能——和应用技能的愿望——却进展缓慢。
7月9日 我们说好的好吗 一句话就哽住了喉
城市 当北京的海市蜃楼 我们 像分隔着一整个宇宙 再见 都化作乌有 我们说好决不放开相互牵的手 可现实说过有爱还不够 走到分岔的路口 你向左我向右 我们都倔强地不曾回头 我们说好就算分开一样做朋友 时间说我们从此不可能再问候 ......
这是无可救药爱情的荒谬 ================================
看了虫虫的blog,发现一首好歌。copy过来了。。。 别姐去了法国，
白兰去了西安。
都一路平安！
莫愁前路无知己
天下谁人不识君
 mark丫头出差了。 7月2日 Java developers should learn RubyOkay, it doesn't have to be Ruby. Pick some other language. Pick Erlang, or even JavaScript. It doesn't matter really matter, as long as it's different enough from Java that it actually requires some effort, and that you keep your mind open to new things. Why bother? Because learning other languages will make you a better Java developer. Seriously.
Learning another language forces you to dive into a different community. You'll find different ideas and different approaches to many of the same problems. They may not be better ideas and approaches, just different. Other communities often have a fresh perspective on similar problems. And sometimes it will even make you appreciate what we really do have in the Java community (like a huge number of really great libraries).
Learning another language can teach you new idioms. Some you may be able to use in Java, and others you won't. Ruby blocks, for example, are Ruby's form of closures and are widely used in most Ruby programs. They're extremely useful for running predefined code that delegates (perhaps repeatedly) to the block for custom behavior. Here's a simple example of iterating over an array and doing some custom behavior (printing the element):
animals = ['lion','tiger', 'bear']
animals.each {|animal| puts animal } Unfortunately, Java doesn't have closures. Not really. The closest thing in Java 6 is to pass an anonymous inner class in much the same way that listeners are often used in GUI applications. All we need is a predefined interface and a method on a class that accepts the implementation and that performs the iteration (like the "each" method in Ruby). So pretend that java.util.List has an "each" method that takes an implementation of an OnEach:
public interface OnEach<T> {
void run(T obj); } public interface List<T> ... { void each( OnEach<T> action ); } Then our example would look something like this:
List<String> animals = Arrays.asList( new String[]{"lion", "tiger", "bear"} );
animals.each( new OnEach<String>() { public void run( String animal ) { System.out.println(animal); } }); Kinda gross, huh? But even though it's not as easily done, it's a pattern that you can use in your designs to allow custom behaviors without requiring subclasses. There are several closure proposals for Java 7, but none are as easy as in Ruby or JavaScript. By the way, Alex has the best resource for all things Java 7.
Learning another language also forces you to use different tools and processes. One example in Ruby is RSpec, which is a Behavior Driven Development framework focused on specifying and verifying behaviors. BDD is a rich topic that I'll explore in another post.
Another example is autotest, a great little tool from ZenTest that takes continuous integration to a whole new level. It works on your local machine (rather than a remote continuous integration server), and it simply monitors your development environment's file system for changes to source files and runs the unit tests corresponding to any changed file(s). If those tests pass, then it runs all of the tests. It's simple, elegant, and allows you to focus on changing the code, yet still get feedback from your tests. It's like JUnit or TestNG Eclipse plugins that automatically run your unit tests as you work on the code.
The bottom line is that the Java community doesn't have the market cornered on good ideas. Java is great and will continue to be, but it does need to evolve. Java first appeared over 13 years ago, and some of us have been developing primarily in Java for most of that time. Go exploring, and I'll bet you'll become a better Java developer for it.
Have you changed how you develop Java after learning another language?
|
|
|
