Interesting. But that air system addresses only the horizontal earthquakes. When the earthquake hypocenter is under the house, I'm not sure it'll work - it may even be worse than a regular house.
Anyway, people in Tokyo and region need something quick:
- today
- yesterday evening
I also think Google does a good job at searching the web. But, similar cases and more complex ones will emerge. Cases where Google will have a hard time to prove/show good faith. And good faith is sometimes not enough in front of a court. Search results that drive the behavior of millions of people, that can quickly build the success of a company, and thus may put another company at a disadvantage, how long such strategic and almost monopolistic feature can keep its core system hidden from external eyes and stay immune to some public investigation? Imo, not long. And I deplore it.
We are caught in a dilemma. While most people trust Google search indexes / algorithms and, thus, its results, Google is, nevertheless, a private company. As such, it will be regularly (probably more and more) attacked by some people for the same - apparently legitimate - reasons as the ones mentioned in this story ; Google being unable to prove the relevancy of such results without revealing the secret algorithms. The dilemma is, can we let/trust Google as an honest company that does the best it can to produce the fairest results? Or do we tend to have to rely, in the future, on a public/independent association/organization that will certify the results/algorithms are not rigged?
As surprising as it can be, I think we tend to the latter.
Jan 26, IBM creates 9nm carbon nanotube transistor
Oct 14, IBM Eyes Brain-Like Computing
Aug 18, IBM creates learning, brain-like synaptic CPU ...more here...
Is it only a recurring signal to motivate the shareholders, or is it intended to produce some tangible applications in a not-so-far future?
Of course computers have N times the speed and memory. Regarding computer science concepts and algorithms, where is the real progress in that field? Most of the concepts used today were designed before 1995 - and a lot of them even before the modern computers ever existed.
CPU and memory is a confortable progress - but is not a revolution. Still to come.
Ok, read that in another/. story (and, very recently, in TFS) but - maybe I'm a bit naive - I thought Mozilla spirit and all would be over that... (oh I just hear people writing replies to this - calm down!)
Quite likely it was the problem. Imagine the CERN saying, after almost a year, "Guys, LOL, that was a faulty cable. Move along...". No, they have to play it the drama way.
Nginx is not only the performance, it's also the configuration syntax ; everything looks much more professional, concise, and logically designed.
The code also deserves a special mention: it's like when you look under the hood of your car/computer for the first time, where everything is clean, all cables are numbered and arranged meticulously. This is a good old C code that doesn't need extra comments to be understood.
Apache improved? Show me the comparison charts between Apache and Nginx, in a many-users multi-cores-cpus and loaded configuration. To be honest, even if Apache would be a bit faster using a bit less memory than Nginx (while I have some doubts about that), I'd still be reluctant to go back to Apache and its setup.
The development head should only accept dev requests coming from the heads of other departments.
A weekly meeting with those dept heads and the dev head to discuss priorities.
This way, priorities are not your problem anymore. Dept heads "fight" / discuss / negotiate to be on top of list. Dev staff / budget issues come clear on the table.
It's a win win.
Slashdot Mirror
Likewise, it will not break satellites if they're unplugged?
...a Solar eclipse will happen at this very time.
((12 - 2)/12) / (2020 - 2012) * 12 % ?
And the French Minitel launched in 1982 had porn. It's all about competition.
Paradoxically, I think Javascript closure is something that should appear more natural, to the beginner.
Interesting. But that air system addresses only the horizontal earthquakes. When the earthquake hypocenter is under the house, I'm not sure it'll work - it may even be worse than a regular house. Anyway, people in Tokyo and region need something quick:
- today
- yesterday evening
I also think Google does a good job at searching the web. But, similar cases and more complex ones will emerge. Cases where Google will have a hard time to prove/show good faith. And good faith is sometimes not enough in front of a court. Search results that drive the behavior of millions of people, that can quickly build the success of a company, and thus may put another company at a disadvantage, how long such strategic and almost monopolistic feature can keep its core system hidden from external eyes and stay immune to some public investigation? Imo, not long. And I deplore it.
We are caught in a dilemma. While most people trust Google search indexes / algorithms and, thus, its results, Google is, nevertheless, a private company. As such, it will be regularly (probably more and more) attacked by some people for the same - apparently legitimate - reasons as the ones mentioned in this story ; Google being unable to prove the relevancy of such results without revealing the secret algorithms. The dilemma is, can we let/trust Google as an honest company that does the best it can to produce the fairest results? Or do we tend to have to rely, in the future, on a public/independent association/organization that will certify the results/algorithms are not rigged?
As surprising as it can be, I think we tend to the latter.
Jan 26, IBM creates 9nm carbon nanotube transistor
...more here...
Oct 14, IBM Eyes Brain-Like Computing
Aug 18, IBM creates learning, brain-like synaptic CPU
Is it only a recurring signal to motivate the shareholders, or is it intended to produce some tangible applications in a not-so-far future?
Of course computers have N times the speed and memory. Regarding computer science concepts and algorithms, where is the real progress in that field? Most of the concepts used today were designed before 1995 - and a lot of them even before the modern computers ever existed.
CPU and memory is a confortable progress - but is not a revolution. Still to come.
My post is indeed not very clever. I won't thank you, but thanks to your unfortunate post, mine looks brillant now. Relativity...
...rare Earth metals may come from the Moon. We didn't do that yet, because no one knows how to call them.
Do you know from where Mozilla gets their money?
Ok, read that in another /. story (and, very recently, in TFS) but - maybe I'm a bit naive - I thought Mozilla spirit and all would be over that ... (oh I just hear people writing replies to this - calm down!)
Ok, but why Firefox would care about Google?
That's what I always liked about Google, so far: they are pretty fair regarding search results and other contents in general.
They haven't proved anything yet.
Quite likely it was the problem. Imagine the CERN saying, after almost a year, "Guys, LOL, that was a faulty cable. Move along...". No, they have to play it the drama way.
Well, maybe it was not that funny after all.
Does the problem apply to Mac OS or Linux? Please be specific.
That's probably why he never played in a violent movie, to set himself up as an example.
Downgraded?
Nginx is not only the performance, it's also the configuration syntax ; everything looks much more professional, concise, and logically designed.
The code also deserves a special mention: it's like when you look under the hood of your car/computer for the first time, where everything is clean, all cables are numbered and arranged meticulously. This is a good old C code that doesn't need extra comments to be understood.
Apache improved? Show me the comparison charts between Apache and Nginx, in a many-users multi-cores-cpus and loaded configuration. To be honest, even if Apache would be a bit faster using a bit less memory than Nginx (while I have some doubts about that), I'd still be reluctant to go back to Apache and its setup.
is not the best way to keep a stable system / bandwidth, recently
The development head should only accept dev requests coming from the heads of other departments.
A weekly meeting with those dept heads and the dev head to discuss priorities.
This way, priorities are not your problem anymore. Dept heads "fight" / discuss / negotiate to be on top of list. Dev staff / budget issues come clear on the table.
It's a win win.
But I'm afraid they won't remove that law after the Olympics.
Why don't you learn braille? It's much easier for you to learn braille, than for blind people to learn how to read a newspaper!