@ewolff Of course they can; used to be the JCP was a good place to collaborate in an open fashion.
Sounds good RT @planetclojure: Clojure – good coding guidelines http://goo.gl/fb/Y6SOk #clojure
4
They do it again RT @mfeathers: Disturbing leak :-( http://bit.ly/hg8swH (via @gilesgoatboy)
3
I bet #wikileaks could use that ... uh, right. RT @jeffbarr: Amazon S3 Object Size Raised from 5 GB to 5 TB - http://bit.ly/s35tb - #aws
+1 RT @unclebobmartin: This is very impressive: http://bit.ly/hu3qLA
1
*sigh* "I have taken [...] the approach of turning the HTTP request/response cycle into plumbing ..." http://bit.ly/euyjmV #lift
2
1
On days like these, I think @robilad's job must really suck RT : Oracle Response to Apache Departure from JCP: http://bit.ly/hVNn92
3
1
"The JCP is destined to become the canonical antithesis of what a standards organization should be" http://bit.ly/g6uvWF
1
Love CS's comment: "The current battle around licensing term … reveals that Java never actually was an open standard." http://bit.ly/h9rbI1
1
. @MasoudMassi It will take a lot more to kill the ASF. The JCP seems to be a thing of the past, though.
Damn, knowing Scala would be nice: "Parameter '-Xstrict-warnings' is not recognised by Scalac." Now where does SBT hide that? #akka
@PaulSandoz AFACIT: no; receive suspends the thread, react creates an F/J task
RT @windley: Clay Shirky - Wikileaks and the Long Haul http://bit.ly/fZpN0J
3
@stilkov Answering my own question: Scala's actors are built on top of F/J.
1