Those differences are usually tax-related. Once you drive across the border into the higher-cost jurisdiction, you're going to be responsible for collecting the appropriate taxes from the end user (and selling the fuel without collecting the taxes is probably going to land you in a wee bit of trouble, because few things irritate the government more than failing to provide the piece of the pie you are mandated to).
...we have electric radiant heat.
In the ceiling.
In Vermont.
All is well and dandy when the first-floor tenants are open for business, but one of the first-floor shops is a hair salon that isn't open on Mondays...and in the winter, it's noticeably cooler on Mondays.
Rubbish. You could add a "This app may send your credit card info to third parties randomly or may turn on the camera when specific grunting or fapping sounds are detected on the microphone (which is always on)" permission to Android and 80% of the people who installed the app would click "OK".
That's part of my point—there's no incentive for app or OS developers to be more sensible as long as 80% (and that may be optimistically low) will click "OK, do it" for any permission requested. If people in general suddenly became more aware of the security risks, maybe that number would drop to 50% and there would be some incentive to do things right...
Any chance this means that mobile OS and mobile app developers might actually start setting up permissions structures that allow apps to function with the minimum necessary privileges?
The permissions framework on Android (and iOS) seems like a reasonable start, but when the norm for a flashlight app is to have full network access and full camera access, it becomes painfully obvious that we as users are not leveraging the frameworks to protect ourselves. If more people cared about Facebook asking for write access to your first-born's soul, they (and other app developers) might have some incentive to build apps that work within the narrowest ruleset possible.
Instead, we have the current disaster, where my stopwatch app requires full network access, Flood-It has full network access *and* access to the contents of the phone's USB storage, etc. Set up an API to allow ads to get pulled in without granting full network access, limit the access the apps have, and it won't matter if the NSA can access your Angry Birds game.
That doesn't always solve it. My personal address is on my personal domain, which is my name (dot com). My name is not particularly common, but not terribly uncommon, either, and on several occasions I've gotten misdirected email because someone got the domain wrong. My personal favorite was the Verizon FIOS signup info, because clearly the person who signed up screwed up his *own* email address.
I've given up on dealing with them, I just hit the GMail archive button.
(and yes, I could reduce the volume by turning off the catchall inbox feature, but I prefer to leave it on so that I can sign up for websites with unique email addresses and then know which jackasses sold (or lost) my info to a spammer down the road.)
Which DSLR goes for the price of a car?
Depends on the car.
If I traded my car straight-up for a Canon EOS 5d Mk III, I'd be getting a pretty good deal.
Unfortunately, you're out of luck on your MacBook for the time being...some of the libraries upon which Gnucash depends do not yet run on OS X/Intel. (see the Wiki entry on OS X installation). You may also notice the list of dependencies earlier in the wiki article, which is not short (and is the reason that using fink is the recommended course of action).
I cannot draw a cart, nor eat dried oats; If it be man's work I will do it.
