Never forget that the US was capable of cranking out one major ship a week 70 years ago when someone got us started.
Never forget how many shipyards have closed in the USA during the last 70 years. And how long it takes to train new workers to construct that kind of ships.
'Once every 500 years' is not equal to 'with 500 years interval'. The next Carrington Event could be tomorrow.
Worse, even events less powerful than the Carrington Event occur more frequently than the Carrington Event and can cause significant damage to our high voltage infrastructure.
What seems more amazing is that a simple software check pre-launch (i.e. "do all the sensors think they are pointed up?") was not part of the SOP. Given that their exact function is orientation detection, skipping the opportunity for self-test via that function is somewhat baffling.
No - the sensors were 'angular velocity sensors'. They do not measure orientation but change of orientation. Is a bit more difficult to check pre-launch than an orientation sensor.
If there is spyware on a machine, doing it's dirty thing without the users knowledge or consent, then any piece of event logging, keystroke logging or pictures taken is suspect. It could be produced by the user, by other spyware, or by a hacker with access to the machine.
The very fact that the 'evidence' is collected by spyware is full evidence that spyware is performing activities the user is unaware about. It implicitely proofs the machine is not under full user control. It therefore proofs not all actions performed at the machine are endorsed by the user.
Since one piece of spyware/malware managed to get installed on the computer means users anti virus and anti malware software is not up to its task. If that is the case, then the installation of other spyware/malware packages is very likely. Meaning there is reasonable doubt about who or what did a download.
And you can not convict a suspect if there is reasonable doubt - not yet anyway.
A picture of the user sitting at the keyboard is no evidence if other software/spyware capable of downloading copyrighted has been installed (without user knowledge or consent) at the same computer.
All the picture proofs is that said user was using the computer at a certain point in time. It doesn't proof the user was doing the download of the copyrighted material. If there was other spyware running at the computer, then that other piece of spyware could be performing the download. All recorded keystrokes, mouse clicks and other logged event are suspect if spyware packages are running at the a machine.
If such a picture were to be accepted as 'evidence' in court, then hackers could easily frame anybody they dislike. Just install the hackers spyware package, spoof some 'evidence' towards the corporate spyware and another sucker gets owned.
Spyware like this can prove that someone did indeed commit acts of copyright infringement as alleged.
No, it can't. Since the TFA talks about "a group of 13 industry associations", we would get every one of these industry associations to install it's own spyware package on your machine.
So if copyrights were to be infringed from your machine, who can prove that YOU were to one to do it, and not one of the spyware packages? All one can prove is that it happened from your machine, not WHO or WHAT did it. A compromised system is by definition out of your control.
You need an OS plus development software plus (possible) database software and webserver software to build your software product. Each of these software products you use has its own end-of-support data. You should never promise support on your product beyond the end-of-support date for a software product needed to support your product. E.g.: if fixing an issue with your product requires fixing an issue with the OS, and the OS is out of support, then you are out of luck.
Any support on your product beyond the end-of-support date for a product needed to perform this support should be on a best effort basis, never on result commitment basis.
Also consider increasing your hourly rate by 10% for each year beyond the end-of-support date of the products you use - this encourages your client to buy an upgrade to a new version of your product, build with current tools.
Secunia PSI tool ( http://secunia.com/vulnerability_scanning/personal/ ) is very usefull, I agree. It knows the most common software products, so I have to manually take care over a rather small list of software products. IMHO it should come preinstalled on every new Windows machine.
Fixed price contract for custom software - so no competitors for that project, and no other clients for that piece of software.
A better argument would be: Delivering a B would hurt our long term reputation. Works only with managers who think long term (next project and beyond), not short term (next bonus).
It all comes down to managing your manager - this can be much harder than writing level A code:-) .
Lazy programmers aren't writing efficient code, they're just relying on Moore's Law to push them through.
Wrong.
It's not about lazy programmers, it's all about calculating managers.
To cite one of my managers during a project review: Next time you're not going to perfect our code like you did on this project. If we measure software quality on an A to F scale, and if our client is satisfied with quality level C, then stop improving your code once you hit that C level. Going for the A will only increase project cost, but not our revenues..
If they were smart they would put 3-4 floors above ground to help with this problem
That's hardly sufficient to counteract the upward buoyancy of the 65 subterranean levels.
Think about 20-30 levels above groundlevel to get the job done - which is not an option given the laws against highrise buildings mentioned in TFA.
Ground water will cause a lot of buoyancy for this building - how will they prevent it from 'floating' upward? Other than using very thick walls from heavy construction materials?
the east of France is also threatened of earthquakes since Basel, a border city in swizerland was once almost completely destroyed in 18..hundred-something
They'll still work just as well as they did the day you bought them if you haven't wrecked them.
Some of the first CD's I bought have become unplayable due to CD rot. Contrary to what the CD manufacturers want you to believe CD's won't last for ever. Nor will DVD's.
It's sad to see some folks rather have the certainty of global environmental damage due to using fossil fuels instead of the possibility of localised environmental damage due to accidents with nucleair reactors.
For a nice demo of what to expect from using then HTML5 CANVAS tag have a look at http://www.rgraph.net/
BTW: there's only limited HTML5 support in IE8, so use a better browser...
Slashdot Mirror
My first home computer was a Grundy NewBrain https://en.wikipedia.org/wiki/... Bought it second hand in '83, for 1000 guilders.
Never forget that the US was capable of cranking out one major ship a week 70 years ago when someone got us started.
Never forget how many shipyards have closed in the USA during the last 70 years. And how long it takes to train new workers to construct that kind of ships.
'nuff said
Worse, even events less powerful than the Carrington Event occur more frequently than the Carrington Event and can cause significant damage to our high voltage infrastructure.
Only for one axis of rotation. That's not enough.
What seems more amazing is that a simple software check pre-launch (i.e. "do all the sensors think they are pointed up?") was not part of the SOP. Given that their exact function is orientation detection, skipping the opportunity for self-test via that function is somewhat baffling.
No - the sensors were 'angular velocity sensors'. They do not measure orientation but change of orientation. Is a bit more difficult to check pre-launch than an orientation sensor.
The very fact that the 'evidence' is collected by spyware is full evidence that spyware is performing activities the user is unaware about. It implicitely proofs the machine is not under full user control. It therefore proofs not all actions performed at the machine are endorsed by the user.
Since one piece of spyware/malware managed to get installed on the computer means users anti virus and anti malware software is not up to its task. If that is the case, then the installation of other spyware/malware packages is very likely. Meaning there is reasonable doubt about who or what did a download.
And you can not convict a suspect if there is reasonable doubt - not yet anyway.
All the picture proofs is that said user was using the computer at a certain point in time. It doesn't proof the user was doing the download of the copyrighted material. If there was other spyware running at the computer, then that other piece of spyware could be performing the download. All recorded keystrokes, mouse clicks and other logged event are suspect if spyware packages are running at the a machine.
If such a picture were to be accepted as 'evidence' in court, then hackers could easily frame anybody they dislike. Just install the hackers spyware package, spoof some 'evidence' towards the corporate spyware and another sucker gets owned.
However, I hate the problem more than I dislike the solution.
Spyware like this can prove that someone did indeed commit acts of copyright infringement as alleged.
No, it can't. Since the TFA talks about "a group of 13 industry associations", we would get every one of these industry associations to install it's own spyware package on your machine.
So if copyrights were to be infringed from your machine, who can prove that YOU were to one to do it, and not one of the spyware packages? All one can prove is that it happened from your machine, not WHO or WHAT did it. A compromised system is by definition out of your control.
Any support on your product beyond the end-of-support date for a product needed to perform this support should be on a best effort basis, never on result commitment basis.
Also consider increasing your hourly rate by 10% for each year beyond the end-of-support date of the products you use - this encourages your client to buy an upgrade to a new version of your product, build with current tools.
Secunia PSI tool ( http://secunia.com/vulnerability_scanning/personal/ ) is very usefull, I agree. It knows the most common software products, so I have to manually take care over a rather small list of software products.
IMHO it should come preinstalled on every new Windows machine.
Fixed price contract for custom software - so no competitors for that project, and no other clients for that piece of software.
A better argument would be: Delivering a B would hurt our long term reputation.
Works only with managers who think long term (next project and beyond), not short term (next bonus).
It all comes down to managing your manager - this can be much harder than writing level A code :-) .
Lazy programmers aren't writing efficient code, they're just relying on Moore's Law to push them through.
Wrong.
It's not about lazy programmers, it's all about calculating managers.
To cite one of my managers during a project review:
Next time you're not going to perfect our code like you did on this project. If we measure software quality on an A to F scale, and if our client is satisfied with quality level C, then stop improving your code once you hit that C level. Going for the A will only increase project cost, but not our revenues..
If they were smart they would put 3-4 floors above ground to help with this problem
That's hardly sufficient to counteract the upward buoyancy of the 65 subterranean levels.
Think about 20-30 levels above groundlevel to get the job done - which is not an option given the laws against highrise buildings mentioned in TFA.
Ground water will cause a lot of buoyancy for this building - how will they prevent it from 'floating' upward? Other than using very thick walls from heavy construction materials?
the east of France is also threatened of earthquakes since Basel, a border city in swizerland was once almost completely destroyed in 18..hundred-something
That quake was on october 18th, 1356.
They'll still work just as well as they did the day you bought them if you haven't wrecked them.
Some of the first CD's I bought have become unplayable due to CD rot. Contrary to what the CD manufacturers want you to believe CD's won't last for ever. Nor will DVD's.
It's sad to see some folks rather have the certainty of global environmental damage due to using fossil fuels instead of the possibility of localised environmental damage due to accidents with nucleair reactors.
If you build the right type of nuclear fission power plants, then they can 'burn' the waste products from uranium burning plants. See http://en.wikipedia.org/wiki/MOX_fuel , http://en.wikipedia.org/wiki/Thermal_breeder_reactor .
They are in fact thinking
Why do you say politicians are thinking, given all the evidence to the contrary?
I'd feel much safer in a current model soyuz than a current model space shuttle
There is no current model space shuttle, only a retired model space shuttle.
Betelgeuse will most likely go supernova within 5000 years, it's a red super giant at the end of it's life.
Yep. In IE9.
For a nice demo of what to expect from using then HTML5 CANVAS tag have a look at http://www.rgraph.net/ ...
BTW: there's only limited HTML5 support in IE8, so use a better browser