Bzzt! You lose. For your "theory", lets say the government buys a $1000 widget. It didn't produce that widget, it spent the money to buy that widget. It didn't spend $1000 for that widget, it spent $1200 because the government has its overhead.
Bzzt! You lose. The government pays at least 400% markup on anything it buys.
Oh, wait... the SHA1 of "badg3r5" is actually 78a7ecf065324604540ad3c41c3bb8fe1d084c50.
(mushroom, mushroom)
I grok this to mean that a backdoor exists for customer service, which can be activated by a customer (by two factors: permission and network access), and that without action on the part of the customer, said backdoor is closed.
"Permission" isn't much of a safeguard against criminals. They tend to do stuff without it.
(Isn't that the very definition of "criminal", i.e. doing stuff they don't have permission to do?)
Let's face it, it's far more likely to be "HP1234" than anything as complex as l33t-speak.
This. They can end up going up to the point that only businesses can afford them.
On the plus side, we might be able to move away from the awful glossy-widesceen-with-awful-keyboard models that the public have been forcing on us for the last few years.
The PC is doomed, blah blah blah. All the grandma's are buying tablets. Anyone who does any real work are buying PC's or already have what they need. Nothing to see here.
Yep. Most computer users turned out to be media consumers who a) don't need the hassle of maintaining a PC, and b) like the size/shape of tablets.
The sky won't fall. This "fatal" decline will level off soon when everybody finally figures out which camp they're in.
You minimize dynamic allocations by staying away from generic data structures--e.g. for a linked list, you embed the sibling pointers in the object itself, rather than allocating a separate container node...
No, you don't. If you've got any brains you start using C++.
I can imagine them slamming on the breaks.
If they were mixing a dance track while driving, they're at fault.
from quick glance, multiple transfers and communications channels("streams" in the drafts lingo) can be put through the single connection, cutting tcp connection negotiations.
HTTP 1.1 can already do multiple transfers, browsers are already doing "streams". I doubt the gains to be made from doing that in binary are going to be noticeable.
It was much less bloated before Javascript and CSS started throwing up in every corner of every webpage everywhere.
That's HTML, not HTTP.
HTTP is the world's most popular protocol and it's bloated and slow to parse.
Do you even know what HTTP is?
Maybe you're thinking of HTML or something.
Ditto.
The HTTP header is miniscule compared to the HTML/images on the web page. Making it binary is a Stupid Fucking Idea.
I figure the reason this never happened is because the people in black SUVs went around visiting anybody who tried to make encryption the default.
The problem with encrypted email is that you can only send it to people who agree that security is important.
That's a problem with the email software, not the people.
A key exchange could easily be done in the background during the first few emails you send to somebody. After that you're golden.
Trouble is, almost everybody uses online email now, and I doubt Google/Microsoft/Yahoo/etc. will ever provide any security.
"God is a comedian playing to an audience too afraid to laugh." - Voltaire
