Do you have any evidence to back that claim up?

There are a number of features in Chrome that optionally talk to Google. But you can change them all if you prefer. Do you have any proof that it "phones home" in any hidden way? It should be quite easy to prove; Wireshark is all you need.

FWIW, I know some of the guys who started the Chrome project. Actually, they didn't start Chrome, they started V8. The point was to prove that Javascript engines could be orders of magnitude faster than they were, and to push the rest of the industry to get better, so Google's apps would be able to do more, faster. The rest of Chrome was just to show off V8. Then it became successful, both at pushing Javascript engines to get better, and as a popular browser, and Google started to use it as a test bed for other ideas about how to make the web "platform" better. Security improvements like certificate pinning. Performance (and security) improvements like SPDY and QUIC. UI simplifications like the omnibox (which geeks like to hate, but non-geeks love). Better development tools (though Firebug was and is quite good). And so on.

I don't think "better tracking of users" has ever been a goal, stated or unstated, of the Chrome project. And, seriously, why would it? It's not like the normal web standards don't offer everything that's required for whatever tracking anyone would like to do.

Think of the countless small ways in which knowing some code, or scripting has been useful over your life - sorting simple lists, renaming things in batch, formulas in a spreadsheet... etc. etc.

Even if most people will not be doing code professionally, it will help them do little things for themselves. It will also help them understand to some extent why software driven things behave the way they do, and even to make more informed choices as to software driven hardware they buy (and that is the future).

It's not like a flood of really bad programmers will get through most hiring barricades, already famously difficult to storm. They will go on to do things besides programming, where light programming can help them.

I would mostly agree with parent. Soylent is fine execpt the community isnt big enough so the comments are barely there or worth reading, the name is kind of bad and the stories are routinely just old enough to be yesterdays news on Slashdot or Hacker news.

Their Twitter feed, which is where I get my news feeds, also puts these really annoying lame "from the deptâ attempts at humor in the tweets instead of just the title of the story and the link:

Razer Acquires Ouya Software Assets, Ditches Hardware from the kicked-down dept

They will even thorten the title to make room for the utterly stupid âoefrom theâ.

The best solution to replace Slashdot would probably be if Hacker news grafted the classic Slashdot look, commenting and moderation system on to their generally good stories and great community.

There is a high probably no Sunday talk show would have let him speak once they found out what he was going to say. They are all owned by giant media conglomerates you know. They wouldnt risk the wrath of the Federal government. Pretty sure Snowden went to Greenwald because he was one of the few journalists with the balls to do the story. The Guardian was hammered by the UK government for running it.

Remember when the CEO of Qwest defied the NSA plan to tap all data and phones lines after 9/11. The Federal government pulled all their contracts from Qwest, hammered their stock and then put him in prison for a phony securities rap. Qwest was a rare corporate hero among telecoms, long since swallowed up by CenturyLink who are just as bad as all the rest.

Death is one of the consequences of treason/espionage.

And yet Jonathan Pollard is not only still alive but will be released in November and given a heroes parade in Israel.

Any American, and I do mean anyone, who releases classified information or spies for another country should be given the death penalty. This includes those people whose actions you might agree with.*

However, like so many others, criminals are being coddled rather than punished.

* I may like the fact that Snowden exposed what most of us on here already knew, but his actions do not mitigate the fact he released classified information. As you said, death is one of the consequences of treason/espionage and the Founding Father knew their lives were on the line when they signed off on independence but rather than run, they stayed and fought in whatever manner they could.

It's not all that hard to stick with a toolkit version for a couple of months (or to be honest, even a project lasting up to 18 months is no big deal.

That depends on the system. If you are doing iOS development, while 18 months is possible it's not advisable due to every new version of XCode (one major, a few minor updates every year) having more advanced tooling, compilers, frameworks... furthermore you are going to have to use a beta version at some point to test and debug your software on for un-released versions of iOS that you have to make sure you work well on before they are released.

I see your point, I was more speaking to the attitude of people that want to spend years without upgrading the underlying technologies involved in building and running your project... the longer you wait the worse the transition is, and like I said in the meantime you are also missing out on things that could have made development easier or resolved bugs you had to fix.

Trial and error, I expect. Look at what other sites do. I realize that this isn't a very good answer. There isn't a good answer, just bad answers that are still better than passwords. Classic OpenID isn't the answer because users don't know how to use it and many RPs don't trust random providers. But as a practical matter providing login with, say, Google, Facebook, Yahoo and AOL will give better than 95% of your users the ability to log on with better security than the password-based model you'd build, and do it just by clicking a couple of buttons.

If you find that your user base tends to have an account with some other provider (no, I can't tell you how to find out who your users are or what they use), then add that.

Google developers do not understand how to design APIs.

Wrong. Wrong. Wrong! Google developers get paid buttloads of money, more than you or I could hope to make. These are the elites, the 1% of the 1%.

Because they are so highly paid the problem cannot lie with them since we are repeatedly told if you pay developers what they're worth you will get excellent results. Just like paying CEOs of companies who go running to Uncle Sam to protect them from their own incompetence.

The problem must lie elsewhere. Look harder.

On the other hand if you fall behind current dev tools, you miss out on the potential for a lot of community support, risk being crippled by the bugs that remain in the older system that are fixed the new, and hamstring your ability to work as effectively as you might because you cannot use newer tooling/frameworks to help with development...

Yes SE has a lot of stuff changing, it always has and always will. But cringing from the pain will not help, SE is not finding any kind of safe plateau (because there are none). It is moving ever forward at a reasonable pace, using nettles as handholds where you must grasp them firmly as you ascend, living with the brief pain to move forward.

Yes, the government should force the obese to get their act together, especially since that same government is now forcing me to pay for their medical care whether I want to or not.

The same for drug users, smokers and alcoholics.

If the idea is to make people more healthy by forcing them to hand over their money to a private company then to get the most bang for the buck forced government coercion to get people to live more healthy lives is the way to go.

When the services go down, you can't log in to the relying sites. Luckily, core infrastructure like the account systems is a very high priority for the engineers, and the big providers have plenty of resources to keep them up -- and they do. My bank's site is down far, far more often than Google's auth servers, for example. How much more often? I don't know... I've never seen Google's auth servers down.

Pick the top several and you'll cover nearly everyone. For the tiny percentage of users that remains, you have to either offer password auth (which means all of the work and risks of maintaining a password system, but at least when you screw it up only a tiny percentage of your users will be affected) or push them to get an account with one of the providers you support.

No its really the opposite. If you sell something and someone files a complaint you automatically lose. People won the auction but don't feel like paying so they file a complaint and you're on the hook for a refund even if they're wrong.

What eBay needs is competition.

You're promoting perpetuating a long-standing, widespread and hugely-damaging user security error in order to avoid a relatively obscure problem which can actually be fixed through purely technical means. Not a win.

What you describe as a problem is actually part of the solution. The problem with classic OpenID was that it was virtually impossible to get, say 1st Bank of MyButt, to use it, because absolutely anyone could be an identity provider. I personally agree with you that classic OpenID was better in that respect, but 1st Bank of MyButt doesn't. They're hemming and hawing about letting Google manage their user's identities, but they will at least consider it.