Right now, it defaults to once, and if you don't unlock the phone, it does it again. I'd like to set it just to once ... period. I figure if they allow you to set it to once, why not to X with some suitable max value.

But I'd settle for once. I get a lot of texts while in meetings, and I don't need the confusing second notification in there making me think I got another. Right now, I just glance at the screen and see what's there without unlocking--it's annoying when I see it's the same text from before.

The update reverted Scalar::Util, which disabled the weak reference stuff needed by a lot of Catalyst libs. I just re-installed it and it worked again.

But on all my new machines, I just use a local lib instead of the system stuff. I don't need sudo access and then the whole lib gets backed up by Time Machine. If you just upgrade the system perl, you have to re-do it every time you restore from a Time Machine backup (it doesn't copy system stuff as near as I can tell).

Also, as some have observed, CPAN is a bad idea. I say this as someone who got screwed when Catalyst went to 5.7100 (I was at 5.7015). When I did a restore to a new machine, CPAN got all the new Catalyst libs and all my customizations blew up spectacularly.

If you are doing serious Perl development on your local Mac, use a local lib and do not rely on CPAN to automatically handle your dependencies. Install things by hand or create a (perl) script to handle the deps for you. That's what we had to do, as we needed to make sure the module version we used matched our production systems--where we do NOT use CPAN and where we upgrade manually and with careful thought.

When I moved across the US a year ago, I had a ton of older hardware and less room to move into (house to apartment). Basically, I gave everything away that I wasn't actively using.

Rather than muck about with secure erasing or degaussers, I just took the dozen drives out to the shed and beat the daylights out of them. Most of my machines were in various states of not running--so the amount of time I would have had to spend putting together a working machine, swapping around more than a dozen older drives, running secure erase on them ... well, it just seemed a lot simpler. There was no way I was giving intact hard drives to random people I did not know, especially drives that may or may not have been erased enough.

I recommend safety goggles. Some of the boards tend to shatter and send little bits flying everywhere :-)

Could some super spy possibly lift data? Maybe. But no ID theft script kiddie will. I saw it like using a paper shredder--only a lot more fun. Sure, some super spy agency might be able to re-assemble shredded documents or lift data from the mangled platters of my drives--but why should I be worried about them? They already have a current file on me, I'm sure--they don't need old drives ;-)

A friend of mine put it nicely: "There's nothing like the feeling of raw destruction you can wreak with a 10lb sledgehammer." It's right up there with using a proper chainsaw. Deconstructing stuff is *fun* :-D

If I am ever worried about super-spies, I look forward to discovering the wonderful destructive power of thermite :-)

The people making the app. Yes, I know that makes freedom folk really upset, but let's set aside the whole "inalienable right to hack" for a sec. You are a large company, and you need to make an app that works for a lot of people over a wide range of machines. If you want to be able to maintain that app, you need a way to make sure customers are using exactly the right version, maybe even have multiple versions specialized for troublesome platforms. And then there's security--how do you make an app secure, prevent data breaches, etc?

For that, you need control. Can it be abused? Sure. But if you have to plan apps for a corporation and your butt is on the line if the app fails, you start to look at issues of control and freedom a little differently.

I'm not saying that it doesn't get abused--it does. I'm just saying there are realities of securing, maintaining and testing applications on a budget that are very difficult, and they only get more difficult as you release more control over the app. Do corps go insane and go too far? Definitely. But if we look down to some of the real problems and the practical solutions to those problems, controlling exactly what the user is using and where that happens is an effective tool.

The "Back to the Mainframe" approach of web apps gives you this element of control.

Yep. And as I said in my original post, and here, that's a boon depending on your perspective. I'll grant you it gets abused, but if you are on a budget and you need a secure, maintainable customer facing application, you need a higher degree of control. And web apps are a modern way to do that.

As I've been trying to point out, your perspective is different from a VP of Tech for a bank or investment firm. And even if you weren't one of those risk adverse people, the advantages of a web app in terms of maintenance and upgrades is huge. Also from a development perspective, you have easily halved, if not quartered, your development costs. Cross platform development is very, very expensive. Cross browser development is expensive, but it doesn't even come close to Windows + Mac cross platform development, and never mind adding Linux to that mix.

I've done cross platform. The only way to keep it cheap(er) is to use something like Java. And then it looks like crap on ALL the platforms.

So, as a firm with a budget (and I think that excludes 99% of open source projects) web apps are very appealing. Unless there is a technical reason for why a web app just won't work, most firms choose it for those reasons. And even when it won't work, they choose the web app anyways and cut features to make it feasible--because the advantages of cheap, maintainable cross-platform development are not easily dismissed.

All that said, I can see why most open source people turn their nose up at web apps. It's not sexy, and it's often very difficult to do anything clever. And let's not talk about installation--now someone needs to setup databases and apache? Compare that to downloading a binary and just running, it can all be very tedious.

I've made my bread and butter off web apps. Heck, you could say web apps and Java bought my house! But the first real fun I have had in years was making an iPhone app. So I understand people who might not like web apps or regard them as a step back--I feel it too. But my next paycheck is coming in from a Perl, Catalyst-based web app that is customer facing.

So I work for the man to enslave the masses and maintain control during the day, and then I hack on my little apps at night :-D