Yes, but they don't mind that. The great thing about Oracle is that they have convinced people that it is a virtue to pay through the nose for stuff. And before you say "that's not great" think of t from the point of view of Oracle shareholders, staff, subcontractors etc etc.
The first time the phone phones home, it uses a designated null id. The server generates a unique id and sends it to the phone which stores it in the user prefs. On each subsequent phone home the app uses the generated id.
A few hundred dollars? So you're texting and you run into the back of somebody else as a result. They get seriously injured. Is that a few hundred dollars?
Between 1998 and 2000 I used NT4. It was a perfectly serviceable operating system in the office environment. It ran Office, Visual Studio, Outlook, Netscape Navigator, etc etc perfectly well. It was also pretty stable with the right drivers.
Anyway, no matter how painful it might be for the person who reverted the patch, the issue does need to be investigated in order to find out how to detect other instances and how to stop it from happening again.
That is £637 per named user. That's great if you are the only person going to be using the application, but if that's the case, you'd probably be better off using sqlite which is £0 per named user.
On the other hand, if your application is going to be used by say 500 people in a local council, it's going to be about £30K worth of named users.
"Don't use Apple devices" is a piece of advice that most people can reasonably follow. You don't have to buy an iPhone, there are other mobile devices with equal or better capabilities.
"Don't use Windows" is not a piece of advice most people can reasonably follow because Windows is pretty much ubiquitous in the PC market.
Actually, the iPod thing has nothing to do with its ability to bring down the plane and everything to do with its ability to distract you from hearing urgent instructions from the flight crew that your life may depend on.
Actually, I don't think that's correct. I think, in an emergency, two pilots probably improve the odds dramatically over one.
If there is an emergency, with two pilots, one can concentrate on keeping the plane in the air while the other deals with how they are going to get themselves safely on the ground.
The fact that Apple is actively hostile to Linux when it comes to iTunes would be the main thing there
You are wrong there, it's much worse than that. Apple is actively hostile to Adobe (at least as far as Flash is concerned). They are totally indifferent to Linux.
Yes, what occurred was you made a false statement about Apple's computers and when you realised what you had done, you tried to claim you were really only talking about the iPod/Phone/Pad.
Blaming a failure on human cause is by far the easiest way to avoid having to fix anything. It also happens to be wrong in by far most cases, as when you look a little deeper you will almost always find issues such as lack of proper training,
Human failure
lack of sleep
Human failure
horrible UI design
Human failure on the part of the UI designer
lack of warning signals
A subsection of poor UI design therefore human falure
lack of communication
Human failure.
None of which are in the control of the human that is flying the plane.
Nobody said human failure = pilot error - except you.
Humans simply make mistakes and any robust systems has to be designed in such a way to handle those small mistakes, if it can't, it is the system that is at fault, not the human.
It's just a completely random dig at Microsoft for absolutely no reason.
Of course it is. The discussion was about how it's impossible to debug Windows with a graphical debugger especially when it's the Windows Manager you are debugging. The fact that the said Window Manager is tightly integrated into the system is irrelevant.
The fact is that, if it runs in the GUI, a debugger tends to be unresponsive when the GUI is stopped on a break point.
Slashdot Mirror
What?
Are you thinking of egcs? That fork was made somewhere around 2.7 and merged back in to gcc (or rather gcc was merged into it) at 2.95.
There hasn't been a fork since then.
So you really think that you had to hold a small briefcase up to your ear? If you look at the picture you will see it had an earphone on a wire.
It mattered to the men inside the tanks that the Germans liked to call Tommy Cookers.
Also, in any Slashdot discussion, the probability that an XKCD strip will be linked approaches 1 extremely rapidly.
Yes, but they don't mind that. The great thing about Oracle is that they have convinced people that it is a virtue to pay through the nose for stuff. And before you say "that's not great" think of t from the point of view of Oracle shareholders, staff, subcontractors etc etc.
Ah yes, the Watergategate conspiracy.
Generate your own unique id.
The first time the phone phones home, it uses a designated null id. The server generates a unique id and sends it to the phone which stores it in the user prefs. On each subsequent phone home the app uses the generated id.
A post that talks about Java caches on the iPhone gets modded insightful?
Bad luck for the passengers though.
A few hundred dollars? So you're texting and you run into the back of somebody else as a result. They get seriously injured. Is that a few hundred dollars?
Between 1998 and 2000 I used NT4. It was a perfectly serviceable operating system in the office environment. It ran Office, Visual Studio, Outlook, Netscape Navigator, etc etc perfectly well. It was also pretty stable with the right drivers.
I don't believe ridicule was mentioned.
Anyway, no matter how painful it might be for the person who reverted the patch, the issue does need to be investigated in order to find out how to detect other instances and how to stop it from happening again.
That is £637 per named user. That's great if you are the only person going to be using the application, but if that's the case, you'd probably be better off using sqlite which is £0 per named user.
On the other hand, if your application is going to be used by say 500 people in a local council, it's going to be about £30K worth of named users.
The only way I'd consider iOS for anything serious is if they remove the approval barrier entirely.
Why? Is your software really that bad?
"Don't use Apple devices" is a piece of advice that most people can reasonably follow. You don't have to buy an iPhone, there are other mobile devices with equal or better capabilities.
"Don't use Windows" is not a piece of advice most people can reasonably follow because Windows is pretty much ubiquitous in the PC market.
Actually, the iPod thing has nothing to do with its ability to bring down the plane and everything to do with its ability to distract you from hearing urgent instructions from the flight crew that your life may depend on.
Actually, I don't think that's correct. I think, in an emergency, two pilots probably improve the odds dramatically over one.
If there is an emergency, with two pilots, one can concentrate on keeping the plane in the air while the other deals with how they are going to get themselves safely on the ground.
The fact that Apple is actively hostile to Linux when it comes to iTunes would be the main thing there
You are wrong there, it's much worse than that. Apple is actively hostile to Adobe (at least as far as Flash is concerned). They are totally indifferent to Linux.
Yes, what occurred was you made a false statement about Apple's computers and when you realised what you had done, you tried to claim you were really only talking about the iPod/Phone/Pad.
Yes, but why would you want to print those things from an iPad when, if you have a printer handy, you probably also have a real PC handy.
Yeah, good put down. But what's the answer to the question?
Blaming a failure on human cause is by far the easiest way to avoid having to fix anything. It also happens to be wrong in by far most cases, as when you look a little deeper you will almost always find issues such as lack of proper training,
Human failure
lack of sleep
Human failure
horrible UI design
Human failure on the part of the UI designer
lack of warning signals
A subsection of poor UI design therefore human falure
lack of communication
Human failure.
None of which are in the control of the human that is flying the plane.
Nobody said human failure = pilot error - except you.
Humans simply make mistakes and any robust systems has to be designed in such a way to handle those small mistakes, if it can't, it is the system that is at fault, not the human.
Who designed the system - humans.
Please God tell me they didn't win.
Actually, what could Piper reasonably do? Should the seats have been welded in?
First time I've wished for mod points for 10 years. Fortunately, you are on 5 already.
It's just a completely random dig at Microsoft for absolutely no reason.
Of course it is. The discussion was about how it's impossible to debug Windows with a graphical debugger especially when it's the Windows Manager you are debugging. The fact that the said Window Manager is tightly integrated into the system is irrelevant.
The fact is that, if it runs in the GUI, a debugger tends to be unresponsive when the GUI is stopped on a break point.