It should be configurable in both directions... you should be able to tell it that a single space after a period is an error, two spaces after a period is an error, or turn it off entirely. Otherwise, they are just taking sides.

Because typically what you are saying is incorrect. If you are writing an application, you are usually free to choose any license you like. LGPL was created so that you can link against libraries without worrying about giving up your secret sauce. The glibc library is an example of this. Granted, you need to take care, in some people's minds, to avoid GPL'd libraries, but it is your choice to use or not use GPL'd libraries.

Don't like it? Don't use them.

"I personally have seen companies who had to re-engineer a whole embedded controller from Linux to Windows CE just so they did not bump into GPL v3 issues."

Too bad for them, since most of Linux isn't GPL v3. The kernel certainly isn't and huge portions of userspace aren't either... ESPECIALLY in the embedded space, where people use slimmer versions of things like libc.

You're missing one key thing in your argument: There isn't a huge pile of cash laying around each year to pay for things. The operating model of our government, and most others is:

1) Pass a budget to determine what you are going to pay for that year.
2) Start spending against the budget
3) Pay for emergencies that come up (floods, earthquakes, etc.)
4) Collect taxes

Notice that the income, in general, doesn't come in until the end. The country lives on credit. Normally, this works. Our problem is that we have let the spending versus revenue get out of hand. One, the other, or both have to change to fix things.

What is stopping them is the fact that you have to be one of the appropriate telex destinations to even tell that a telex message is passing by. If you don't know the appropriate parameters, you can't tell that the SSL connection even has a telex message inside, much less tell what the message says.

(Reposted because I forgot to log in)

The problem with your first statement is that having a "good and valid reasons for leaving a wifi network unpassworded" doesn't mean that those reasons afford you an expectation of privacy, and so, is irrelevant to the discussion.

As to Google's sniffing being more intrusive than a reasonable person would expect, there is no need for the metaphorical telescope. This situation is more akin to going around your neighborhood, telling everyone that they are free to use your windows and doors, and then acting surprised when someone sees you in the shower. The people who are utilizing open WiFi are sending out beacons saying "I'm here, I'm unencrypted, feel free to use me."

Keep in mind, the WiFi Alliance has mandated that Access Point ship with encryption enabled by default for something like a decade, which is longer than the expected lifespan of most wireless gear. The vast majority of people utilizing Open networks have, at some point, made a choice to have their network be unencrypted and accessible by anyone who cares to join.