I do agree that malicious extensions could be a problem when allowed via sideloading. However, simply add an option to turn off the blocking from the client. Those that want to sideload can and, by default, others will be blocked. Seems like a logical way of handling this.

I do also like the suggestion of providing a "trusted list" that allows for alternative "App Stores". These options could make these actions more palatable.

Your off topic comment is my weekly rant. I HATE having to toss stuff out because someone decided to make the thing from a brittle plastic and heat seal it shut.

I've tried to buy higher quality. It just seems you cannot find it.

it's a good example. That's not the last I heard. I'm under NDA. But, I can enumerate the multiple bugs we've seen with chips. Your point is valid. It's more about the human/dollar cost of the bugs. As fab costs have fallen and the more use of FPGAs, the cost of mistakes are lower and, therefore, more bugs have crept in.

Make the bug expensive and more discipline will be given to the problem.

Wish I had mod points... This is the my primary barrier for learning Python (been doing PERL since '94). I like that it has lots of built-ins for web stuff. But, couldn't they use common practices when it comes to syntax and layout?

JS is the lingua franca for front end web use. I like the comparison to annoying relatives :)

Agreed. Seems the author is confused between users and Freeloader, in the traditional sense. The Freeloaders are those that incorporate their code into their product and offer that for sale and don't contribute back to the open-source community.

In a certain product for sale, I know of just under 50 open source components (not including core linux) included. All the licenses are complied with. But, few get patches submitted upstream. Some bug reports though.

Does the community need this kind of freeloader? I think so. But, there should be some community responsibility to contribute financially if you're not contributing code.

agreed. The method in which this is calculated really isn't described either. Even though I'm in a development role, we're pressured to demonstrate "research" when we're really just assembling code.

US/Europe need to actually produce real stuff. Anything else is just proprietary fodder for others to take.

Lap seat belts were optional on domestic cars from the early 50's through 1967. In 1968, they became mandatory. 1964 was the first year for required padded dashes. The big 3 offered them across the line much earlier though. Shoulder belts became required in 1971.

IIRC, Tucker released the first padded dash on a domestic car.

Looks like they didn't do much proofing. It was Starsky and Hutch's Torino. And, it was Green Hornet's "Black Beauty" ('64-66 Imperial).

Both are great cars with many great replicas built!

In other news, Fukushima Daiichi has created a new species of bio-luminescent cockroach...

HTC,
I went to the Verizon store to pick up a replacement recently. No HTC One? Really? Why?

How I used to love 'ya. I'm still using my HTC Incredible. It's been, well, pretty incredible. Well, until the latest updates came out. I've had more crashes since the last update than I had over the last 3 years.

My next phone won't be an IPhone. It won't be a Windows phone either. What does that leave me with? Motorola? They break promises with 1yr old phones; Should I look at the new RAZR models? Will they get JellyBean? Who knows?

That leaves Samsung.... Is it really so hard to create an Android phone that we can get excited about?

hey, it's only $1 a pin... What's your gripe?

I wish I had mod points. I think *THIS* is the primary problem here.

The Declaration of Independence is also a good example of the importance of free speech rights even in the era or the Internet. On July 4, 1776 the original declaration of Independence was signed by only two people, Charles Thomson as Secretary and John Hancock as President of the Continental Congress.