Today we have Java yielding, thread ranting, REST lecturing, and identity insight.
Yield! · On the Chaotic Java weblog, Java “yield return” code published. Anyone who’s gotten comfy with Ruby’s yield/block idiom quickly starts to wish that every language had it. I haven’t had the time yet to do a deep-dive on this, but that’s definitely on the to-do list.
Threads ewwwwwwww · Roman Shaposhnik has The problem with threads, a nice succinct explanation of why, from a programmer’s point of view, they pretty well suck. I freely admit that since coming to Sun, my opinion on this has shifted 180°, from “threads are tough but worthwhile” to “Let’s find some combination of functional programming and message passing so ordinary people never see threads”. Roman has some of the reasons why.
REST Hard? · Patrick Mueller (who’s appeared here before) has how RESTy need we be wondering, how far down the path of pure REST, as notably taught by Joe Gregorio, we need to go. The question is worth asking, but I think Patrick goes off the rails, claiming “Here's my thought on the lack of adoption of REST: it’s complicated for anything but the GETs.”
Um, evidence please? I just finished building a 100%-pure-REST data store; it’s only a few thousand lines of code and a few weeks work, and that’s coding in pure grim unforgiving C, using the poorly-documented and without-a-safety-net Apache module API.
Identity Lock-in · Dave Winer’s been saying this really smart thing for years and years: “People come back to places that send them away.” For an example, think of Google. In Lock-in and the web, day 2 he applies the principle to the identity world. The conclusion: “A vendor will come along and they’ll store your identity but give you complete freedom to move it where ever you want when ever you want at no cost. They’ll make it easy to do so. And they'll get rich doing it, if they want to.” Yup.