Actually you'd write something like this: Collections.sort(list, SomeClass.COMPARATOR); So readability and maintainability is better than your closure example. SomeClass would be in its own .java file like this: public class SomeClass { public static final Comparator COMPARATOR = new Comparator() { ... } }

Hey, the Russian went to space first anyway, it's not like americans were at the bleeding edge.

Yes I did, for android specifically I worked on Android Notifier (http://code.google.com/p/android-notifier/) and we got *dozens* of emails about simple things but it's manageable. It's better than letting every app do everything like the current situation right now, people don't read permission listings too ;)

They won't because the app will get a PermissionDeniedException and almost always show a message to the user explaining that it didn't send an SMS message because the user blocked it. It could even know if it's permanent and just give up that feature completely after the first warning.

You could make it remember your choices.

Humans make mistakes, it's tech's responsibility to help the user to not make them.

Exaclty what J2ME does.

Maybe they could copy the J2ME security model. Everytime the app tries to send an SMS, the OS asks the user "Steamy Windows wants to send an SMS, is it allowed to do so?", if the user denies permission the app receives a PermissionDeniedException and handles it as it sees fit. This way the user will go "Why my wallpaper is trying to send an SMS!?!?". Of course, the user can make the OS "remember" his permission and never ask again.

But you don't get IDE auto-completion and syntax coloring.

Using strings instead of compiled code is too fragile. org.apache.commons.lang.Validate or com.google.common.base.Preconditions are much better for this kind of validation.

Did you read the project description on the link I provided? Here it is:

I didn't know caching system has been redefined to be nosql... Now java.util.HashMap is a nosql implementation!

Memcached is a distributed in-memory cache implementation, it has nothing to do with noSql. See: http://code.google.com/p/memcached/

Leave them solve this by themselves. You have a huge amount of work to solve US problems already.

Isn't that the Android Notification bar in the first picture in Ars' article? http://arstechnica.com/gaming/news/2011/01/ngp.ars

This is not the first time NYTimes goes against wikileaks: http://twitter.com/wikileaks/status/30359666491920385 They didn't get the cablegate data because of some issues on Iraq data. So I don't think NYTimes is the wikileaks' preferred US outlet

I'm glad I use two machines, one for dev work and another for browsing the web which is such a heavy task!