since you own the device

LOL, you naive fool! Don't you know there's a "War On Property" going on, where copyright holders everywhere are trying their damnedest to make their Imaginary Property rights superior to your right to control the physical device that their Imaginary Property happens to be in?

"Your" computer? You don't own it. "Your" cellphone? You don't own it. "Your" TV? You don't own it. Even your car? Fuck, you're lucky they even let you open the hood without being a "Manufacturer Certified mechanic!" (It'll already allegedly void the warranty -- even though the Magnuson-Moss Warranty Act says it shouldn't -- but at least it isn't entirely illegal... yet.)

And the "Internet of Things?" Well, the manufacturers have realized that if a device doesn't have Imaginary Property in it, then "consumers" will still own it, and that's intolerable. So what's their solution? Infect every product with Imaginary Property! Pretty soon, the only place you'll be able to buy anything without being forced to electronically consent to some bullshit contract of adhesion will be places like Goodwill and Craigslist... at least until the Copyright Cartel finishes making it illegal to resell used goods.

(You know, a few years ago if I read something like the above I'd think the writer was a paranoid lunatic. But now I'm forced to believe it. Fuck.)

There is a free and a paid version, the difference being the number of maps you can download.

And, if I understand correctly, the F-Droid repository has a free version (named OsmAnd~) with the limitations removed so that it's equivalent to Google Play's paid version.

I was expecting more of a stationary time lapse vid covering five years

Here ya go.

As the saying goes: "There are four boxes to be used in the defense of liberty: soap, ballot, jury and ammo. Please use in that order."

But treaties circumvent three of those boxes.

Guess which one is left.

Comcast don't have to let you buy theirs, but they shouldn't be able to stop you from buying one from a third-party (e.g. a TiVo or an HDHomeRun + HTPC). Of course, their bribery has convinced the FCC to allow them to encrypt, which means you still have to get a CableCard from them.

You say "small pickup" as if you think such a thing still exists....

Allowing customer-owned equipment is required by law! The issue is that the FCC can't be bothered to enforce the law. (And by "can't be bothered," I mean "bribed not to.")

as a bay area resident, I'm an ignorant bigot who thinks everywhere in the South is like a scene out of the movie "Deliverance."

FTFY.

FYI, Atlanta and other urban parts of the South (which are where the programming jobs are) are just as liberal as Silly Valley, and I'm sure rural/small town California (e.g. Redding) is just as conservative as the rural South. The only real difference that makes California "blue" and Georgia "red" is that California has a larger proportion of urban population.

I get value from the area I live in and I can relate to the people in my area

Yeah, I get value from my walkable, transit-friendly area and can relate to my hippie / hipster / gay / progressive / multiracial / environmentalist / whatever neighbors too.

I would have nothing at all in common with typical southern attitudes

What, you Californians think you have some sort of monopoly on enlightened values? You need to check your hypocrisy, mister "more-tolerant-than-thou!"

It's similar to you saying you built a piano and I ask you to play some Chopin or Bach for me. But you never claimed to know how play it, you just built in. If I wanted to know about your ability to build pianos I should ask questions about the construction and internal workings of it.

How do you know if the piano you built works (or indeed, that it is even a piano at all) without playing it?

I'm not saying playing some Chopin or Bach is necessary, but you should at least be able to manage something like "Chopsticks" or "Twinkle, Twinkle Little Star."

How many deployment avenues don't use cryptographic signatures? Usually you're either producing downloadable code, in which case the packages or tarballs are generally signed, or deploying to an HTTP or similar server, in which case you should at least understand what the purpose of TLS is.

Okay, so you've explained why the couple of guys who are responsible for deployment need to understand cryptography. Why should the other several dozen programmers in the office, who are neck-deep in business logic (or whatever little corner of the system they're responsible for is) 99% of the time, have to care about it?

Mod parent up. Is there some part of West Bumfuck in the state of Nowhere that has a horde of kick-ass programmers that is unemployed? If so, clue us all in and companies will shower them with six figure jobs.

Yes, they're everywhere that isn't northern California.

I, for one, would be perfectly happy to work for some stereotypical silicon valley tech company... but I'm not about to trade my $100k 3-bedroom house in Atlanta for a million-dollar shoebox-sized shithole to do it. You want my skills? You come to me.

You clearly aren't master of the obvious, since you missed the fact that forcing someone to accept "terms" to use his own goddamn property is offensive and downright dangerous to society (because it's attacking the very concept of property rights).

You can always turn

ret_type function_1(type1 param1, type2 param2, ... typeN paramN) {...}

into

typedef struct function_1_params {
type1 param1;
type2 param2;
...
typeN paramN;
} function_1_params;

ret_type function_1(function_1_params params) {...}

In fact, you would (ideally) notice that the params in your struct have something in common (other than merely being arguments of the same function), name your struct accordingly, and then start using it in other places where it makes sense. You can also even group your N arguments into M structs, where 1 < M < N and the arguments within each group are more related to each other than to the arguments in the other groups.

Though the number of arguments to the new subfunction may be an argument against doing it that way.

If your function takes too many arguments, then you're probably suffering from a lack of encapsulating data structures (or trying to do too much in one function).

Heap allocation is unsafe.

Once again it depends. I've spent a large part of my life writing code for tiny little processors with limited memory. The general rule, especially for the military stuff, is that you are not allowed to run out of memory while executing. So either your binary image fits on your device after compilation or it doesn't. It must not fit, and then run out of memory days later during execution. The only way to ensure this in a formal manner is to have no malloc or equivalent calls.

For that, "no heap allocation" is necessary but not sufficient. You also need to prove that your stack doesn't overflow.