HN user

jmcnevin

82 karma

[ my public key: https://keybase.io/jmcnevin; my proof: https://keybase.io/jmcnevin/sigs/e9dk8txl5fpNZg9jRPJgpp4NDtI8CiV8NTG1ePGg5ho ]

Posts4
Comments41
View on HN

We've been using Temporal for the past year and have found it to be an absolute joy.

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.

Would you ever want autocomplete on, say, a field where you're inputting a 2FA response? Probably not, since any suggestions would be useless.

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?

I find this story highly suspect, unless the writer happened to find a company run primarily by sociopaths.

I'm not sure why MS decided that the release of a free upgrade of their product that's trying to address pain points with Metro would be great opportunity to shove the Windows Store down users' throats. I can't even open Windows Store on my media center PC (hooked up to a 720p television) without increasing my screen resolution past native. That's just irritating.

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.

I don't believe the intent here is to replace Resque (Resque is awesome), but provide a slim API at Rails.queue that Resque/Delayed Job/BackgroundDRB/Torquebox/etc. could tie into, similar to how Rails.cache works now, in addition to adding a simplistic default implementation.

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.

As an rdio subscriber, a streaming video service that offered some sort of integration with rdio would be pretty interesting. A single subscription plan that would allow for unlimited streaming of music AND movies could be huge.

For the record, I almost immediately filled up my allotted iCloud backup space because of rdio, because I have 4.6 gigs of music synced for offline use, and it wanted to back that up.

Solution: I disabled backups of rdio data.

Is it possible that a user could use Instapaper to save a document that they wouldn't be able to download later, even if they had access to an internet connection? If that's possible, I think Instapaper would have every right to store things in the Documents folder, since you're asking it to create something more akin to an archive than a temporary cache of data.

Firefox 4 is here 15 years ago

I just noticed that FF4 also has shiny new javascript confirm and alert popups, complete with a lightbox effect. Nice!

Firefox 4 is here 15 years ago

I'm a little conflicted about the Firefox Sync feature. On the one hand: yay! On the other... it's a lot more difficult to set up sync in Firefox than in Chrome. I got to work today and was dismayed to discover that I couldn't simply login to Mozilla's server and sync up my bookmarks from home, but that I needed the sync key from my computer at home to get this working. Boo. That, or you need to have the devices you want to sync in the same place and use a Netflix-like "Add Device" feature.

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.

They must have had some room to spare in that case to bother putting in a rear camera.

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?

Being in that majority of people who haven't built Twitter-scale systems in the past, could someone explain to me why Twitter is moving to a new form of twitter ID in the first place? What is wrong with their current system?

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?