Somehow, even though the actuaries would say you're right, the PR people would tell you you'd be a dead company. Today a billion dollar satellite explodes, the public doesn't really care. Tomorrow, when a school teacher dies with her students on a rocket, and if that company is found to be grossly liable, they're dead.
No, this paper is explicitly stating that the theory is flawed. If this attack is expanded, SSL traffic will essentially be as secure as rot13. That's very different and much worse than heartbleed or any key generation issue. My applications were not affected by either of those coding mistakes, but they and everything else using the same algorithm would be by a break in DH.
"Popular implementations of SQL commonly omit support for basic features of Standard SQL, such as the DATE or TIME data types. The most obvious such examples, and incidentally the most popular commercial and proprietary SQL DBMSs, are Oracle (whose DATE behaves as DATETIME,[30][31] and lacks a TIME type)[32] and MS SQL Server (before the 2008 version). As a result, SQL code can rarely be ported between database systems without modifications."
Well, right now Spacex is only shipping cargo, and they have competitors. The cost to launch includes insurance on the cargo, wich is set by the success rate. If they have more failures than their competitiors, the insurance cost will go up.
The problem would be if they were a monopoly on launches, where the cost of a failure would go down if they didn't have any competitiors.
If they do start ferrying people, well then they open themselves up to higher liability with a failure. Worse reputation, higher payouts to families.
That's not to say it couldn't happen, but there are some monetary things working in their favor to prevent it. You just have to make sure that who ever in the compnay might profit from a successful launch will also suffer for a failure.
If you don't want confusion, you do things people expect in a way they expect.
If you have a giant red button that says STOP on a piece of machinery, but it actually speeds things up ( by stopping the speed restrictor from working) that will cause issues, regardless if there is a label above it saying "speed restrictor".
That's essentially what KDE did with a 4.0 release that they never inteded for wider distribution.
No, you're forgetting the beauty of the backend. KDE 4 was all about plasma. In Plasma worskpaces nothing is special. Everything is a plasmoid widget. Nothing is special about the dock, the desktop, or an icon. They all have the same back end object, and can be placed and dealt with in the same way. It was seen as a way to increase the flexibility and configuration of the desktop.
That was job #1, converting everything to plasma. Job #2 was making it pretty, then everything else.
4.0 was poorly explained that it *wasn't* really ready they just called it a.0 to get people to beta test it. I know that makes no sense at all. It was really stupid. KDE was ready for distros and actual end users right around 4.4.
It looks like they've learned their lesson by calling this the beta that it is. Hopefully, distros will be a bit more pragmatic in upgrading this time.
That might produce some additional revenue. They're suing the makers of a look a like solution for the iphone. Why not just take a cut of everyone that wants to do it, and help them do it as well? It might revitalize physical keyboard handsets.
Damn it! I always forget the time traveling antiparticle! Is there nothing cooler in existence? Its like forgetting to get ice cream at the worlds greatest ice cream store.
The older headline 1.0 headline of "Windows 8.1 Pre Update 1 Reduction of Update Availibility arives mid 2nd quarter" has been obsoleted and will not recieve any more updates, which required an update to a headline 2.0 compliant headline.
Averting the consequences of climate change require people en mass to change their behaviors. No such change in behavior is required for Nuclear disarmament. Plus many large wealthy company will have to be satisfied making slightly less money, they aren't thrilled about that. Also some Jobs may be lost as a result of those diminished profits.
All of the nuclear weapon creation jobs are long gone. All the work around them is related to maintenance and dismantling them. Some people are benefiting from the dismantling, very few are suffering.
For some people. For others, they really see things in binary. It must be great, or it must be terrible. Thumbs up or Thumbs down. awesome sauce or lame.
Its called lowering standards. If you expect bad movies, its easier to actually enjoy them. If you expect great movies, its easy to be disapointed. Most people aren't very good at approaching a given subject with objectivity.
That's all very useful information, thank you for sharing that. It doesn't change my opinion really as I've worked with early FORTRAN, but its pretty interesting for those that were not aware of that history.
I mean Basic isn't difficult either, but I really don't understand the perspective at the time that FORTRAN was so complex that BASIC and COBOL were really needed for their syntax changes alone. All of the explinations I've read about them, invariably have the line somewhere about FORTRAN being so difficult to understand that only scientists could master it. I understand they were all invented for different problem domains and that's kind of a good reason in and of itself, but sheesh, its not like it was brain fudge.
I try to use the names authors give to their products, just like I try to use the names people would be preferred to be called, out of respect for them. If Bradly want's to be called Chelsea, well, KDE can be called KDE Plasma Workspaces, Platform, and Applications.
Second of all, Linux *does* include drivers for new and old stuff. It does not generally speaking, include closed source drivers. So, if you are using open source drivers that are in the kernel today, you're A-Ok.
I've had several cheap motherboards that never worked with windows XP or above due to sound issues, but all of them worked perfectly in Ubuntu Linux. They were set up back in 2006, and are still working with the most current version of Ubuntu. That's pretty good I'd say. Of course you mileage may vary, depending on the motherboard, and the open source drivers available for it.
And then you have the various governments that have moved over from windows:
I can't add much to Martin's sage words, but basically the term doesn't have much meaning in and of itself. Its the tech equivilent of stamping a "Natural" label on a box. What does that mean? Almost anything.
If its going to take less than a minute to break in, then yes. Other wise I'd throw the person in my car and drive them to the hospital less than a mile away.
I've done the whole "drive person experincing an anphalictic shock to the hospital" routine before.
Depends on the date of expiration on the epi pen, the door, the coworker, the time to the nearest hospital, any near by door destroying weaponry, and on how many appendages I have at the moment and their current status.
Yeah, I agree. Its UX desgin. Which most programmers at small companies have to do themselves. It gets more complex in games, sure, but its not that different.
When ever I hear game designers try to explain what they do I always think of John Romero and ion storms issues with Daikatana. Too many game/level designers not enough engineering and art talent.
Somehow, even though the actuaries would say you're right, the PR people would tell you you'd be a dead company. Today a billion dollar satellite explodes, the public doesn't really care. Tomorrow, when a school teacher dies with her students on a rocket, and if that company is found to be grossly liable, they're dead.
No, this paper is explicitly stating that the theory is flawed. If this attack is expanded, SSL traffic will essentially be as secure as rot13. That's very different and much worse than heartbleed or any key generation issue. My applications were not affected by either of those coding mistakes, but they and everything else using the same algorithm would be by a break in DH.
http://en.wikipedia.org/wiki/S...
"Popular implementations of SQL commonly omit support for basic features of Standard SQL, such as the DATE or TIME data types. The most obvious such examples, and incidentally the most popular commercial and proprietary SQL DBMSs, are Oracle (whose DATE behaves as DATETIME,[30][31] and lacks a TIME type)[32] and MS SQL Server (before the 2008 version). As a result, SQL code can rarely be ported between database systems without modifications."
That's why its cute.
Well, right now Spacex is only shipping cargo, and they have competitors. The cost to launch includes insurance on the cargo, wich is set by the success rate. If they have more failures than their competitiors, the insurance cost will go up.
The problem would be if they were a monopoly on launches, where the cost of a failure would go down if they didn't have any competitiors.
If they do start ferrying people, well then they open themselves up to higher liability with a failure. Worse reputation, higher payouts to families.
That's not to say it couldn't happen, but there are some monetary things working in their favor to prevent it. You just have to make sure that who ever in the compnay might profit from a successful launch will also suffer for a failure.
If you don't want confusion, you do things people expect in a way they expect.
If you have a giant red button that says STOP on a piece of machinery, but it actually speeds things up ( by stopping the speed restrictor from working) that will cause issues, regardless if there is a label above it saying "speed restrictor".
That's essentially what KDE did with a 4.0 release that they never inteded for wider distribution.
No, you're forgetting the beauty of the backend. KDE 4 was all about plasma. In Plasma worskpaces nothing is special. Everything is a plasmoid widget. Nothing is special about the dock, the desktop, or an icon. They all have the same back end object, and can be placed and dealt with in the same way. It was seen as a way to increase the flexibility and configuration of the desktop.
That was job #1, converting everything to plasma. Job #2 was making it pretty, then everything else.
4.0 was poorly explained that it *wasn't* really ready they just called it a .0 to get people to beta test it. I know that makes no sense at all. It was really stupid. KDE was ready for distros and actual end users right around 4.4.
It looks like they've learned their lesson by calling this the beta that it is. Hopefully, distros will be a bit more pragmatic in upgrading this time.
That might produce some additional revenue. They're suing the makers of a look a like solution for the iphone. Why not just take a cut of everyone that wants to do it, and help them do it as well? It might revitalize physical keyboard handsets.
Damn it! I always forget the time traveling antiparticle! Is there nothing cooler in existence? Its like forgetting to get ice cream at the worlds greatest ice cream store.
Its headline 2.0 compliant.
The older headline 1.0 headline of "Windows 8.1 Pre Update 1 Reduction of Update Availibility arives mid 2nd quarter" has been obsoleted and will not recieve any more updates, which required an update to a headline 2.0 compliant headline.
Me? I'm more worried about GM being ready. I'm not the one actually doing the work or being financially responsible for any failures.
Averting the consequences of climate change require people en mass to change their behaviors. No such change in behavior is required for Nuclear disarmament.
Plus many large wealthy company will have to be satisfied making slightly less money, they aren't thrilled about that.
Also some Jobs may be lost as a result of those diminished profits.
All of the nuclear weapon creation jobs are long gone. All the work around them is related to maintenance and dismantling them. Some people are benefiting from the dismantling, very few are suffering.
For some people. For others, they really see things in binary. It must be great, or it must be terrible. Thumbs up or Thumbs down. awesome sauce or lame.
Its called lowering standards. If you expect bad movies, its easier to actually enjoy them. If you expect great movies, its easy to be disapointed. Most people aren't very good at approaching a given subject with objectivity.
That's all very useful information, thank you for sharing that. It doesn't change my opinion really as I've worked with early FORTRAN, but its pretty interesting for those that were not aware of that history.
I mean Basic isn't difficult either, but I really don't understand the perspective at the time that FORTRAN was so complex that BASIC and COBOL were really needed for their syntax changes alone. All of the explinations I've read about them, invariably have the line somewhere about FORTRAN being so difficult to understand that only scientists could master it. I understand they were all invented for different problem domains and that's kind of a good reason in and of itself, but sheesh, its not like it was brain fudge.
Oh God, please let it be true. Deliver us from the Scourge of Comcast, and make haste unto thy busom of Charter.
Then they lanched a new phone right before microsoft bought them. The Nokia X.
http://en.wikipedia.org/wiki/N...
Well, we'll just have to disagree.
I try to use the names authors give to their products, just like I try to use the names people would be preferred to be called, out of respect for them. If Bradly want's to be called Chelsea, well, KDE can be called KDE Plasma Workspaces, Platform, and Applications.
But KDE isn't a single program or even a set group of programs, its a community of people that develops those things in a highly customizable way.
So *my* "KDE" might not use much resources at all, while yours might consume more than CERN. It depends.
First of all, this story is about BSD, not linux.
Second of all, Linux *does* include drivers for new and old stuff. It does not generally speaking, include closed source drivers. So, if you are using open source drivers that are in the kernel today, you're A-Ok.
I've had several cheap motherboards that never worked with windows XP or above due to sound issues, but all of them worked perfectly in Ubuntu Linux. They were set up back in 2006, and are still working with the most current version of Ubuntu. That's pretty good I'd say. Of course you mileage may vary, depending on the motherboard, and the open source drivers available for it.
And then you have the various governments that have moved over from windows:
http://linux.slashdot.org/stor...
This is relivant:
http://blog.martin-graesslin.c...
I can't add much to Martin's sage words, but basically the term doesn't have much meaning in and of itself. Its the tech equivilent of stamping a "Natural" label on a box. What does that mean? Almost anything.
If its going to take less than a minute to break in, then yes. Other wise I'd throw the person in my car and drive them to the hospital less than a mile away.
I've done the whole "drive person experincing an anphalictic shock to the hospital" routine before.
That's a terrible analogy. A modern mobile device is a superset of the old capabilities.
Its more apt to calling your notebook an Analytical Engine. Which, I'm going to start doing now that I've thought of it.
Depends on the date of expiration on the epi pen, the door, the coworker, the time to the nearest hospital, any near by door destroying weaponry, and on how many appendages I have at the moment and their current status.
Yeah, I agree. Its UX desgin. Which most programmers at small companies have to do themselves. It gets more complex in games, sure, but its not that different.
When ever I hear game designers try to explain what they do I always think of John Romero and ion storms issues with Daikatana. Too many game/level designers not enough engineering and art talent.