billymeltdown

Dave writes:

> "there’s a much better - and cheaper - option just down the road. My library."

I disagree, I think coworking spaces are a far better option than the library! Far cheaper than office space, environment for working and actually talking to a co-worker or two, no social isolation, it just makes so much more sense.

That's good advice, Jacques! Most of these requests are about our time tracker (Tempo), not any secret project. We're a pretty small shop, so everyone's wise to it at this point.

Well, yeah, but you would not believe how often, brazen, and somewhat sycophantic it is. Some of these messages seem so... oblivious. They even admit that they are working on competing projects. It's starting to get weird.

Ha, that's kinda true, I suppose. Sun gave MySQL the kiss of death.

I plug postgres constantly, myself, and I do want to see it get more popular and have a larger community of support (heh, although more users can mean the inverse of supportive community!). I do think it's a superior technology to MySQL, but every tool has its place. Would be good for more people to know the elephant is out there, and all the cool stuff it can do :-)

This was an awesome presentation, it really was, and it ended up causing some good post-presentation debate in person and on the 'tubes. If you search for #futureruby in google and/or twitter you'll find some lively discussions of Jesse's talk.

Hi, Yan, curious if we can get more technical info out of Apple folks about how their new "hardware encryption" feature for iPhone actually works.

I wasn't getting snippy with you, dude. I was really wondering if you knew something we didn't beyond speculation. My comrade Stephen (author of article above) suggested pretty much the same thing.

Also, would love to know why you're pretty sure.

Hi Denis, are you at WWDC? It would be quite rad if someone were to start prodding the apple folks in sessions with regards to this. Inquiring minds want to know!

"I personally don't find it outrageous in the least. It's their platform to do with what they wish."

Well, I see your point about "their platform", although I can find it pretty crap policy if I like :-)

I think the EFF article is particularly interesting because I think in the end this will be one of those about-face situations for them, I think their policies and procedures may not actually match up with what they really want (or perhaps a better guess is that the might be blocking things they didn't really intend to block -- or maybe they just don't like the EFF!).

So the EFF rejection stands out for me. It's like blocking the NY Times app because there's a political cartoon shown in it -- which would actually match up with a lot of other rejected apps.

Anyway, it's sand in Apple's face, publicly. And many developers stay away from the platform because of these issues. It's good all-around that this is in the news, imho, it gives them more incentive to stop the lameness.

Hey look, we turned this into a discussion! Wee!

Axod, I don't think it's that bad (linkbait, wise), and:

I like to know about such things because I'm also an app developer. I also think it should be publicized because it's outrageous bull.

Even if I wasn't an app developer, I'd think this was interesting on grounds of knowing how people get content, and who can/does censor that access.

Also, there wasn't any whining in the EFF article.

I know all about cron, I was looking to see if people choose to just queue up all their jobs in a scheduler, if they fire up stand alone scripts, daemons, etc.

Yeah, I'm not feeling it either.

Although it is funny when the flame baiters start calling each other "wannabe" in the thread.

Oh it's totally show-and-tell time: I'm a big fan of the Stumptown roasters out of PDX, in particular, their "Hair Bender" roast.

Actually, we had 24 hours to change our code to adapt to the API change, and we were able to handle it quickly before it became a problem, we didn't end up with any duplicate tweets. The point of the article is that anybody who didn't see the announcement in time didn't really have a chance. It's a public API, there's a reasonable expectation here that a bit more notice would be given to such a change.