Won't someone please think of the old ladies?
That (4) is a much bigger influence than you imply. What Medicare and Medicaid cover and do not cover, at what levels and under what conditions they cover things have an enormous impact on the healthcare of the rest of us.
I download my TV shows wirelessly. It's very high bandwidth, too. I *NEVER* wait more than an hour for a one-hour 1080i episode (though I never wait less than an hour either), and I can download several episodes at once without slowing down or impacting other users of the network in the house.
The best part? There's no monthly fee, and it's *LEGAL*.
OTA, it's the future.
Ugh, unless you're on a gbit wired connection, why bother? Sure, wireless can work, but it can be shit too.
Oh, you forgot to wire jacks in your house? That's a problem.
My $99 "radio thermostat" (Mine's the cheaper one from THD) does it. Doesn't need the internet, though it can work over it, when I'm at home my phone talks directly to the thermostat, doesn't need any external servers.
Glad it helped you. Is it your argument that you are typical of welfare recipients?
Chew on that for a bit.
Historically, Persians were Zoroastrian, not Muslim, right?
Tabs are simply not a good choice for indentation *regardless* of language because there is no standard for how to use them.
That's a stupid thing to say. Replace "Tabs" with "Spaces" and it's just as true.
If we use tabs, I can make them 1, 2, 4, 8, or 32 wide, whatever I prefer. If we use spaces, I have to agree with and accept whatever the team prefers. Seems pretty simple to me.
If you make a standard for how to use any character or set of characters for indentation, then there's a standard.
Oh, and while you're right, I haven't written much Python, I have written a WHOLE LOT of code in brace languages. I use IDEs that brace-match for me, so in the really hairy cases, I have a little help. How do you brace-match spaces?
It's a major design flaw. It was made even worse when (allegedly) Guido said that if he were going to do it over again he'd require spaces instead of tabs. Because everyone agrees on how many spaces looks good, right?
And it's fun to count columns to figure out where the "if" block ends, right?
Also, while we're at it, any language with an "unless" statement is deeply flawed.
That's because local government is small enough to be manageable. State governments probably aren't, and the federal government, well, just look at it.
As a counter-example, look what happened to Utopia here in Utah. They spent gobs and gobs of money, and will be in debt forever, and for those very few who can get it, it works, but for most people, nothing.
Also, look what happened to Provo. Their FttH project failed so badly they ended up keeping the tens of millions in debt and handing everything over to Google to get it working.
Muni isn't a guarantee of success.
I want to live where you do. In my area, Comcast raises prices every year or so, just because. Hell, after three years, I ended up with a 15mbps/3mpbs plan that THEY DON'T EVEN OFFER ANYMORE, and was paying $79/mo for the privilege. New customers, even without the new-customer discount, would get 20mpbs/5mpbs for $69/mo. Would they give it to me? No, but they would upgrade me to some shitty TV service for an extra $10/month.
I switched to Centurylink (DSL, used to be Qwest) and now I get 40mbps/7mpbs for $44.95/mo for a year. We'll see where I go from there when that ends.
And instead take up...?
So wait, let me get this straight, we Americans already spend more per capita than other developed nations on healthcare to no positive effect, and you propose as a solution to our problems moving some money from the military to health care?
Missed the point, didn't we?
Fair enough. Here's the argument, sans sarcasm:
To assume that one or another tool is better for me without understanding my problem is foolish. In my particular case, I only HAVE transactional data, and this data is life-critical, as in, people may die if a transaction fails to be written to disk.
"No-SQL" (in its common meaning, i.e. non-fully-ACID document stores) is not appropriate for my problem, and I would guess that you would agree.