I think the big difference is that Bell Labs did much more fundamental research: basic science, physics, material physics, semiconductors. Google is putting a good deal of money into R&D, into engineering research like the self driving car and now robotics, but not basic science the way Bell Labs was.
I don't understand why you are dismissing it as "pure semantics." Semantics is the fundamental meaning of words. If you advertise "buy", but the license is is more akin to "rent", then that's lying. If you lie to someone, they won't be very amused if you say "well, 'truth' and 'falsehood' is just pure semantics."
You wouldn't say that you are "buying a revokable license to live in an apartment" when you sign a lease. You would say that you are renting. Why does it suddenly become buying if it's a digital good?
Another good habit to be in is never checking any kind of credentials into source control; even if it's some private personal project, just don't be tempted to check in your credentials to source control, because at some point you may find some portion of that that's useful that you import into a public project, accidentally preserving full history.
Sorry to the OP, hope that Amazon reverses those charges once you tell them what happened.
We know we shouldn't be committing password or personal key. But shit happens and it does happen very frequently, even top notched people do.
What we need is not to say "don't it", because no shit we shouldn't be doing that. instead we need defense mechanism. It would be helpful and interesting if git or hg has a plugin that detects when some credentials is leaking through and warn users "hey you better check this shit out" before doing a real commit.
The other thing is "don't commit key into a private repository". Don't chef and puppet users usually do that? How are people backing up their keys?
For rails, the Figaro gem is really helpful for managing environment variables, which is a good place to store credentials (the config file for Figaro is then added to .gitignore)
But how do you back up this set of environment variables. Yes, in practice I also use ignore file to prevent sensitive things leak into repository and I usually generate password dynamically on the fly or through some script.
What's the best way to handle api keys without storing them in a repository? A separate configuration file?
I've saved api keys to a repository, but only ones with no payment information attached and read only access. Mainly because I couldn't think of a better way at the time.
This is very convenient on Heroku, but on my own servers, I have to use a post-deploy hook to copy a file that has all of my API keys to the server. That works great, except I now have a separate file to manage outside of source control, it's not under its own source control, and it's difficult to share amongst my team.
I've had some luck with having a separate repo. I'll have a "public" (even if it's not public) with all of the usual source code, and a "private" repo, with passwords, fabric files, run scripts, etc.
Works well on teams, where the subset of developers that don't need to do actual deployments don't need the private repo anyway.
Why would it be expected that do-not-disclose agreements cover all employees or owners? Most top secret information is handled on a need-to-know basis; it is only given to people who are deemed to need to know it. Even within IBM (or any other large company that was involved in PRISM or other NSA programs), most people in the company wouldn't know about it. In general, there are only a few people within the company, who have a secret or top secret clearance, who get to know about what's going on.
Furthermore, owners don't know everything about a company either; shareholders in a public company have no greater insight into the company than the general public.
So, why don't they just have a policy that you have 24 hours to get a refund, like the original Android Market policy? Sure, I suppose if you are really dedicated you could play through a game in those 24 hours and get a refund to play for free, but that's a marginal enough case that it's probably not worth worrying about.
Or they could just limit the number of refunds you can get, to say 1 out of 10 games that you buy, and no more than one per month.
Or they could just refund you any time you want. Yeah, sure, a few people will scam them that way, but it's not like they have a huge per-unit cost for delivering the games to you. If it'll make users like the above more happy and more willing to buy from Steam, it's probably worth it in the long run.
Sure, I suppose if you are really dedicated you could play through a game in those 24 hours and get a refund to play for free, but that's a marginal enough case that it's probably not worth worrying about.
I think your underestimating the number of gamers who would pull all-nighters to play through a game as fast as possible in order to play games for free. Heck, plenty of people already do that without the ability to get a refund once they are finished.
Hell, if I was still in college I would seriously consider doing it as a broke student.
Allowing for refunds within 24 hours is effectively a free 24 game rental for any game in the library.
This is an open source project designed to be hosted on one of the "personal cloud" platforms that you can run yourself on your own hardware, or if you want, run on a VPS that you trust. That eliminates many of the concerns that people generally have about "the cloud," while still giving you the convenience of having it web-accessible from anywhere you want to check it.
Or I can use X11 forwarding over SSH to access GNUcash from my desktop which seems a lot safer than hoping that whatever VPS I have on the Internet is magically secure.
According to [this resarch](http://www.schallerconsult.com/taxi/taxifb.pdf), 57% of the fare (including tip) goes to the driver, 24% to vehicle and gas, 15% to the owner, and 4% to other expenses.
So, the driver is a pretty substantial portion of that. Taking the driver out of the equation would substantially reduce the costs. If you increased medallion availability as well, and the owners were able to work with lower margins (or they were cooperatively owned), you could get the cost down even further, to maybe 1/3 of what taxis currently cost. That would be a huge difference in affordability for everyday use.
When reading that article, while I don't have the background for all of it, I find that most of it sounds fairly plausible, until I get to this: "In 1995, Susskind, along with collaborators Tom Banks, Willy Fischler, and Stephen Shenker, presented a formulation of the new M-theory using a holographic description in terms of charged point black holes, the D0 branes of type IIA string theory. The Matrix theory they proposed was first suggested as a description of two branes in 11-dimensional supergravity by Bernard de Wit, Jens Hoppe, and Hermann Nicolai" at which point I start to suspect that this is all just made up technobabble.
Taxis are a lot more expensive than self-driving cars. The driver takes something like 60% of the fare you pay for a taxi; I'm sure insurance eats up another sizeable chunk, and if self-driving cars are ever allowed on the streets, they will have to be safer than human drivers, and thus will have lower insurance costs. Furthermore, eliminating the driver means that you could use even smaller, cheaper cars, or fit more people or belongings per car, making self-driving cars more efficient.
Taxis drivers also really frustrating to deal with (the majority in my city, at least); I can't count the number of taxi drivers who haven't been able to find my house, so I've had to play phone tag with dispatch while waiting 45 minutes for a cab that should have been there in 10, then finally hike down the hill, get in, and had them start the meter while they drove up it to pick up my belongings.
>Taxis are a lot more expensive than self-driving cars.
But they have the advantage of actually existing. Whatever relatively near-term possibilities there may be for cars to operate on "autopilot" on certain highways, an urban environment where taxis are most common is probably one of the last places you'll see self-driving cars.
Sure. I'm just pointing out how these hypothetical self driving taxis/car shares would be a substantial improvement over actual taxis, enough so that they would be able to displace more than just the niche that taxis currently occupy but also car sharing programs like Zipcar and probably a substantial portion of car ownership.
I think that I'll see them in my lifetime; I don't know if it'll be in 5 years (though I think that would be pushing it), 10 years, or 30 years, but I'm pretty sure they will come about, and will be a huge improvement over our current system of letting distracted, impatient people try to pilot cars through chaotic conditions.