82 karma · joined February 18, 2010
Being able to model business processes--some of which may take multiple _years_, and require human approval/rejection steps--using procedural go/java/js, and knowing that once that function starts executing, it is basically indestructible (barring the complete destruction of temporal's backend database), is just really cool. Being able to outsource a lot of the complexity involved in using event sourcing to manage distributed transactions frees up our developers to worry about just the high-end business logic.
Congrats to the team! I'm excited to see Temporal gaining some more traction.
I find the workaround of "just put some other random bullshit for the value" hilarious. And once developers start over-abusing that as well (they will), then what's the plan?
Do you realize that your Windows 8 license key will not allow you to download and do a clean install of 8.1? You need to download 8.0, install 64 or so important updates, and only then are you deemed worthy of being eligible to download 8.1 through the Windows Store. Who thought this up?
I went the clean install route after my upgrade from 8.1 preview stalled out on the "Almost There" screen for 15 minutes. I rebooted, and all references to my installed applications were gone.
All in all, the 8.1 upgrade wasn't a pleasant experience.
Considering Rails has always been about best practices--and background job queueing is definitely a best practice--I think this is a great move.
This will also allow other gems/plugins to have an easy way to push their own jobs into the queue rather than trying to support a bunch of different queue implementations.
http://en.wikipedia.org/wiki/Id_Tech_4#Games_using_id_Tech_4
Solution: I disabled backups of rdio data.
I get it. Encrypting locally is more secure, but they've made this system SO secure that it's actually irritating. I wish I at least had the option of foregoing this sync key business.
Anyway, now I know to put my sync key on Dropbox so this doesn't happen again.
Look at the screenshot of the camera app: http://www.apple.com/ipad/built-in-apps/camera.html
Notice the placement of the "record" button. Now imagine holding the device up to take a picture with two hands.
Even assuming another app developer will come along and fix this, who's going to use a tablet as a giant, awkward digital camera?
breath = noun breathe = verb
"Breathes" New Life
That is all. :)
http://www.dd-wrt.com/wiki/index.php/Optware#Installing_torr...
Also, it seems strange that they would include the new ID in string AND integer form in their JSON. I realize that they don't want to break existing javascript apps, but isn't there a significant bandwidth cost in adding that sort of kludge to the API when you're serving a quadrillion of these api requests every day?