NVidia should have spent more money on engineering and less on advertising. All the Tegra chip sets overpromised and underdelivered. I see no reason why this one should be different.
We always suspected that submitters and editors do not understand maths, but now we know it.
The key word is "percent", not annualized. There is nothing sneaky about annualizing - they just compare one quarter to the same quarter next year. But putting it into relative growth figures makes it look impressive.
Personally I think we will see tremendous growth in 1Gb connections for a while. It is a standard technology transition process, and it is clearly entering the rapid growth phase.
This is the key problem. Only experts are able to assess the risk of a password manager and use it appropriately. How can a normal user know whether a password manager is trust worthy? Do any of the big web sites recommend a trust worthy password manager?
The only viable solution for a normal user is SSO. Login in Facebook, Google, Microsoft Live, that is the way forward. 3 accounts are easy to remember, and it would also be faster to detect suspicious activity. But does any bank offer SSO?
No, of course not. In fact my bank requires me to remember 4 PINs, 3 passwords and one user ID. How idiotic is that?
That is a very good question. And I wonder whether 3rd party libs do anything else illegal - such as spying on the user, stealing passwords etc...
> IMO There is NEVER a valid reason for ANY entity to hold onto an unpatched vulnerability
How about profit? Maybe even legal profit, and certainly lots of it?
Defence in the depth is the only option we have - relying on a single piece of software to be "secure" is obviously more than optimistic.
But even defence in depth fails if the government throws enough money at a hacking company. They will just buy the exploits and string them together to take over the flash player, escape the sandbox, escalate privileges, and then jump across the network. Defence in depth makes this a tedious, expensive and uncertain exercise, but by no means impossible.
> Pedestrians have the right of way, which is true.
> Far too often I see pedestrians step into the crosswalk in such a way as to make it all but impossible for the left turning car to safely stop.
I think you fail to understand the concept of right of way. If you are going too fast to safely stop, you are going too fast.
To be honest, the idea that anybody who can see your credit card can take your money is not really security at all. Usually transactions require additional evidence - either the physical card, the PIN, the address, or the security code.
Maybe that is the problem, or maybe the Skype group has been sabotaging the modern style ("metro") Skype app. I thought it was simple, but perfectly usable, except for one problem: you could not log into a different account. Not at all. You can only ever log into one account: the one you are logged into the desktop with.
That is just silly - most people will have at least a private and a professional account. And asking your admin at work to get your private account setup on the PC is just plain silly.
> were you seriously being held back by having to name the function before passing it on as a parameter?
The point of Lambda-functions is not to avoid a name, but to include the function definition inline in another function call. it makes much shorter code that is much easier to read.
Sure. And we could go on emitting CO2 like it is nobodies business, and maybe wreck this earth. That would be evidence, but not proof, that climate change is man made. For proof you would want to wreck at least 3 earth, and have another 3 control earth that are just fine without humans.
The problem is "Google Play Services". Once you sign up with your Google account, it starts phoning home and reporting your GPS position. Especially on older hardware that causes serious battery drain.
So it is ok that the attacker cracked your password, just because he can only use it for a few weeks? That is an odd idea of security.
Actually, the basic argument is flawed.
Brute force password cracking is a guessing exercise. So a password can be cracked in 25 years - that sounds not too bad, right?
But actually there is 4% chance the password can be cracked within 1 year, a 1% chance it can be cracked in 3 months, a 0.03% chance it can be cracked in a day.
And these probabilities are the same whether you change your password or not!
So you need a better mitigation against password cracking. Not losing your hashes would be a good start, limiting retries is another, monitoring activity a third.
If somebody is spending 25 years of their life to crack your password, you may have other problems...