No of course the man is not opposed to making a profit, quite the contrary.
The man is against short term and short sighted policies, he prefers to have a future horizon that's more than 13 weeks ahead.BR>
A perfectly sensible thing to do.
1. When you buy a new computer Windows is on most pre-installed.
2. When a European, there are some 500 million, starts up a new Windows computer he needs to select a browser from a list.
3. The ~90% of Europeans that don't understand computers will like to get the best and select the browser with the highest number.
4. Conclusion, Mozilla needs to get to a higher release version.
There are well established international treaties governing the various responsibilities for collecting meteorological data, including access to each others satellite data.
I do believe a breach should only in exceptional en well controlled cases be allowed to continue.
But even when the breach is stopped there can be very good reasons to delay an announcement to the public until the appropriate authorities have had a fighting chance to go after the perpetrators.
When you notify the public you also notify the perpetrator limiting the chance of catching him.
And in case of a serious vulnerability you potentially invite more trouble.
Pulling the plug on the affected server is not always the best solution.
The pot was just an example on how any secretive filter list can end will be abused.
But yes, there are some basic novelties like 'about:memory' in FF5.0.
About Fedora's 6 months release cycle, maybe you missed Fedora is the cutting-edge development version of and for Red Hat?
But judging by his public statement we can safely assume he wanted a longer term goal while the Board wanted more focus on the short term results.
Surely they can replace FF4.0 by FF5.0 without exposing their net to Chinese hackers.
No of course the man is not opposed to making a profit, quite the contrary.
The man is against short term and short sighted policies, he prefers to have a future horizon that's more than 13 weeks ahead.BR> A perfectly sensible thing to do.
49 to go :)
I simply don't understand how you can equate a high version number to quality.
In other words, you'd be a bad computer salesman :)
You are running FF5.0 or newer right?
Low hanging fruit?
2. When a European, there are some 500 million, starts up a new Windows computer he needs to select a browser from a list.
3. The ~90% of Europeans that don't understand computers will like to get the best and select the browser with the highest number.
4. Conclusion, Mozilla needs to get to a higher release version.
Now there are plug-ins that cause memory grabs but that's a different group of developers.
Anyhow you can see for yourself, just type about:memory in the address bar to check where memory is used.
The world does not not agree on the name of any number beyond million, the Americans call it billion, the Europeans milliard and so forth.
http://en.wikipedia.org/wiki/Names_of_large_numbers
The first are physical and once used you have to buy more, the latter only requires sufficient infrastructure.
There is a cost attached to the infrastructure but once paid you can, save for maintenance, use it to your hart's content without added expense.
Lets hope someone at MS does not purposely introduce an incompatibility in the other versions.
Especially the heavy duty construction industry regularly needs to be able to plan ahead for several days.
Because the USofA has been over-spending for several decades and the accumulating interest payments are finally catching up.
Because the US is not the only one running these.
Doh, the subject was the Form Factor, not the present capabilities.
Several years ago a bean counter decided we could save money so it was recompiled from the trusted Unix platform to Windows.
Not a huge problem as in the day it wasn't exposed to the internet but today it is and now it's not just infected USB drives that do cause trouble.
About the users :)
So my question is does this old virus still run on Win7?
But at least we know who to call when they leak.
But even when the breach is stopped there can be very good reasons to delay an announcement to the public until the appropriate authorities have had a fighting chance to go after the perpetrators.
So you think this bill is stupid enough to relegate the solution to a local street cop.
When you notify the public you also notify the perpetrator limiting the chance of catching him.
And in case of a serious vulnerability you potentially invite more trouble.
Pulling the plug on the affected server is not always the best solution.