My argument is that regulation doesn't prevent anything.

Murder laws shouldn't be kept because they prevent murder - they don't. They should be kept because they provide just consequences for an immoral and harmful act. Taxi regulations do neither.

Pretty sure grocery stores do pay for repairs/stock loss/insurance through increasing the price of their goods. How else would they do it?

I know, right. That's why, ever since we outlawed murder, nobody has ever killed another person. Regulations my friend, regulations. They're like magic.

Average GTA player demographic?

And spiders can't? Maybe it's just because I'm an Australian, but spiders here can kill you, while a wasp sting is mostly just going to hurt like the blazes. I sort of assumed there were deadly spiders elsewhere, too.

FTFY

2 *known* in 1.2M. But yes, it's their future actions that will be the most important indicator.

This article is about such issues, though. If you have a walled garden, you're basically trading your freedom, for the ability to have someone else police the software, to presumably eliminate such threats.

That trade-off's value is entirely dependant on the quality of the policing done on the software inside the walled garden. Historically, Apple's been pretty good about it, too. But with people locked into the ecosystem by their prior app purchases, there's less and less incentive for apple to spend resources keeping the quality control high.

This could be just a blip that Apple will correct, and start maintaining high standards again. But it could also be the point at which the walled garden deal starts to turn sour, and people find they've been locked inside a garden nobody's looking after.

The thing is, Android is a capable of doing all those things (issuing refunds, punishing the vendor, etc) in it's store too, without a "walled garden" approach.

The walled garden metaphor refers to the iOS platform, where users can't install applications except through Apple's blessed appstore, not to the store itself.

The dev team didn't make any choices at all. The dev team doesn't write their own requirements.

Most of the JS that causes issues are third party scripts from various vendors, loaded from their sites. If their CDN chokes, it affects our site. All the assets we control are accessed via a CDN, and our pages are cached to the extent permissible by their content. It's the arbitrary crap loaded in from third parties (that can't be cached or handed off to our CDN because it's dynamically generated) that screws stuff up.

The javascript on the primary site I work on takes up about 50% of the page load time. None of it is to do with functionality - it's all analytics or A/B tests or performance measuring stuff. One day something broke with the tool the marketing guys use to insert all that guff, and the site performance doubled. Inspect the DOM tree after it's loaded, and there's 30-50 iframes and script tags that have been dynamically inserted on any given page.

I'm not against javascript; it's useful for making sites do useful things. But this sort of crap just drags everything down.

Pounds? I didn't even know Black Friday was a thing in Britain. It's not here in Aus.

I imagine there were three reasons:

1. You could intercept all three if you inclined the blade forward so you intercepted one in advance of the other two, then caught the others closer in. Alternatively, just sidestep one and deflect the other 2.
2. Items with mass could be controlled by force telekinesis
3. Nobody was particularly interested in killing Jedi when the only ones around were a mountain hermit and a swamp rat

On the other hand, this is twenty-five years after the Alliance victory. The Empire should be the underdogs now, so a bit less Goliath treatment for them might be appropriate.