No static classes, they are facades.

I have mixed feelings about Laravel's use of the facade pattern. On one hand it brings a really simple API, which is great for new users and rapid development. On the other hand, it's hiding away dependencies and making testing slightly more complex. It's seems a bit like hiding behind multiple global service locators.

This is pretty much exactly how I do it.

I still sometimes get that sinking feeling in the stomach that I have screwed something up, usually just after I hit the 'execute' button. And I really don't want to have to take the site down to run the restoration.

Broder went in with a preconceived notion, and did everything in his power to make that notion come true.

Its not only Aus.

Example: price of Creative Suite® 6 Design Standard is USD1,299 versus GBP1,227, despite the fact that the exchange rate is around 1.55.

For some stupid unknown reason, Adobe will usually charge the same unit price in GBP as they do in USD. They will quote "cost of operating" is higher in the UK, but 55% higher? Bullshit.

Don't forget the 20% VAT which is included in the British price. The US price doesn't include any tax.

though VAT makes up for some of the difference, it doesn't make up for nearly 1:1 USD:GBP pricing.

If they can charge it, they will.

That assumes all companies charging an extra percentage are actually paying their VAT bills as well.

VAT is avoidable, but the tax man makes that sure that no one is going to.

However, corporate tax and a few other bits and bobs payable on overall revenue are perfectly avoidable if you channel it out and about.