However due to the way that information is compartmentalized within the NSA, it is entirely possible that Snowden has more information than a senior NSA official may be aware that the NSA has. There is a wel known security policy that states that information should only be provided to eople on a need to know basis, and it is entirely possible that up to now the senior NSA official may not have had a need to know just how much data the NSA collects. For that matter, it is possible that the official may still not have a need to know, or never have it.
What morons - the tweeters, that is. On Github, starring a project means that you want to keep track of it, not that you endorse it. Out of over 100 starrers, at least some of them surely followed it so that they could watch the conversation unfold or even track active participants.
Refusing to hire someone because they're listening to a conversation makes you a world-class moron. Ironically, it may be that they're listening because they have the exact same opinions on it that you do.
They wrote it in ASM, using bios calls on a per character basis. It's really tight code.
As long as you live in her basement, or it costs less to call you than call the manufacturer's tech support, you'll be your mother's first line tech support person. You know what to do about the first situation. The latter situation may just be an extension, except that she will save up tech support problems for your next visit. You do plan on stopping in for Dad's Birthday, right?
Not really, it was written in assembly.
That's a miniscule part of it. My company's base infrastructure is n servers. During heavy load, we routinely need to scale up to n*20, maybe n*50 capacity. We pay out the ass for a few hours then drop back down to the cheap n size. Because we share a cloud provider with many thousands of other companies, we can do that scaling for a tiny fraction of what it would cost us to support our maximum capacity on our own. When our needs are peaking, our neighboring companies are scaling down and going dark for the night. When they're at top demand, we're done and "idling".
If we needed to keep n*50 capacity online 24/7/365, it'd be cheaper to host ourselves. That's not the case, though, so we're very willing to pay a higher rate for those short periods of time when we need to meet above-average demand.
I can't overexaggerate how much I love the zone of silence in my daily bus and train rides, or the pristine calm of the city sidewalks.
Give me a fucking break. Suddenly the Senate is concerned for my delicate ears? More likely: an airline was cutting a deal with a carrier to sell AirTalk (tm) in-flight voice at $3.99 a minute and doesn't want to be undercut.
The noise is now above the signal. We're screwed.
Wake me up, when September ends.
Note to Wall Street investor types: the best guy in the business is scrupulous to the point of rigorously avoiding even the appearance of impropriety. Warren Buffett became a gazillionaire without bending the rules and throwing ethics aside.
If you feel you have to cheat to get ahead, then openly admit that you're not very good at your job. Go ahead: look in the mirror and say "I suck too much to play it honestly". If you can't do that, then maybe you need to evaluate your decision making.
A market approach would have individuals producing their product, and seeing which one the market accepted. The Soviets largely went on which bureau chief had the most political pull in the Politburo.
Re Go being statically linked: great! It's meant to be a language for writing services. Those are typically deployed by creating a giant tarball of all the artifacts needed to deploy a service, copying it to all the hosts that will run it, extracting in place, and restarting. In this case, the tarball is the compiled executable. You can copy it to its server and have everything required to run it in a single tidy package.
Contrast with a Java deployment where the tarball will contain many JAR files, etc. Rolling back to a previous version either involves a symlink shuffle and restart or updating CLASSPATH to point to the old version. The Go equivalent is stopping the service and running the previous binary.
Static linking would be a pain in the ass for replacing everything in
I think an important aspect in the US is that the politicians told NASA to go for it and then stepped aside (at least until after the first couple moon shots), while the politicians were micromanaging all the way through the Soviet program.
We also just chucked money at NASA and said "Make it happen." The Soviets had rocket experts with their own bureaus and their own goals competing for funding and support from the Kremlin. For example, Korolev vs. Chelomei.