Profile_bird

Hey there! cretzel is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What's happening? Join today to start receiving cretzel's tweets.

Already using Twitter
from your phone? Click here.

cretzel

  1. ... I'd had two or three other frameworks (apart from fork-join, see http://trunc.it/3lwwj) that would benefit from closures ...
  2. Seems like the main reason for them to introduce closures in #java7 is to remove boilerplate code from the fork-join framework ...
  3. Nice article by Brian Goetz on fork/join in #java7: http://trunc.it/3l7y6 http://trunc.it/3jju0. Dates back to Nov 2007, folks!
  4. Using #Guice for #GroovyBot
  5. RT @stilkov: @AdamBien AOP solves a problem that doesn't exist in more powerful languages
  6. http://trunc.it/3gfra RT @StefanRoock: RT @stilkov @codemonkeyism Web applications can be handled on multi-core without fancy new features
  7. @puredanger Isn't that BGGA? This 'official' document says it's FCM http://trunc.it/3efrc.
  8. @jodastephen @glaforge Looks like this is the official closures definition announced at #devoxx: http://trunc.it/3gjkd
  9. @DavidBaum Thanks. I noticed that the agile people like #prezi and gave it a try. Was surprised about how easy it is to use.
  10. Anybody who knows some details about the announcement at #devoxx that Java 7 will contain closures? #java7 #closures
  11. Nice presentation tool. "Prezi" http://trunc.it/3ffoe
  12. New Blog Post: "Concurrency is not such a big Deal ..." http://trunc.it/3cmy0.
  13. For me, concurrency is secondary. It's more about expressivenes. #scala #clojure #groovy #ruby
  14. When it comes to web apps, concurrency is not an argument in the debate about which language would be the best Java successor, right?
  15. @skohler #JRebel, ftw!
  16. @njbartlett By the way, we had to make a decision for/against OSGi about a year ago. I loved it, but for some reasons we decided against it.
  17. @njbartlett Also, I think, many people to not value modularity as much as they should. Same for OSGi dynamic services.
  18. @njbartlett There's definitively the need for modularity. But it seems for many people this need is not huge enough to make them adopt OSGi.
  19. @mosmann Don't know really. Probably it's startup time, speed, simplicity, ... And also, I'm too commited to Google's apps and services.
  20. @njbartlett Yeah, but feels like adoption of #osgi has somehow suffered from the jigsaw/osgi debate/flame war. Just a personal feeling.