No worries. I clearly should have articulated my point better. I’m always worried about over explaining or sounding pendantic.

I agree wholeheartedly, alas we live in an imperfect world. It sounds like you’ve waited for an update or two that took longer than expected.

I’m not arguing that the source code shouldn’t be made public. If someone posses the right skills they should definitely be able to take full control over the devices they depend on to keep them alive. It’s a invasive feeling knowing you depend on a gizmo to not die.

The author of this article is glossing over a lot of steps by implying that open sourcing the apps and firmware is a fix for delays in app store approval or other common problems that are inherent in the software/hardware ecosystem. It not really a flawed argument, it’s just not what I would’ve lead with.

I think you’re making a good case against an Internet enabled pacemaker ;-)

Then we disagree. Think about it, you’re patching the OS so what you now have is an untested configuration, and you’ve replaced a working system to get there, on the theory that you might be preventing an unknown bug in the future.

In one instance the vendor even explicitly recommends disabling OS updates until they have tested them.

Not if the existing software functions properly. If there’s a fix in it you need then sure, once the vendor has tested and approved it you should migrate.

I can’t with this article… there’s a very legitimate argument to be made here, but instead they are whining that stuff stopped working after an iOS update. If you’re running something life-critical you do not install every single update the moment it comes out.

5 points for the awk command.

10 points for a perl script.

;-)

Inner thighs and labia :-(