If you have music, we own it. If you have a computer with music on it, we own that too. If your computer is in your car, parked in front of your house guess what? ours.
B&N is coming to the "media" tablet party a bit late. They should have found a way to trim $50 off the tablet to directly compete with the Fire. By not doing so, they won't be converting too many of the faithful kindle crowd.
Maybe: - stick with your current phone for 4 years? - skip your next computer upgrade for 5 years? - settle on a 24" LCD instead of the 92" plasma?..Not a chance
It's disturbing that we've put our own neck in the noose but just keep tightening the rope.
Generally speaking, when your market share increases, so do the amount of devices you have in service. The more devices you have in service, the higher the percentage of failed devices. It's math, not magic.
Ok, for starters it's another innovation killer. By Apple bolstering it's control of the platform, in yet another authoritarian way, it raises the frustration level for the developer and many would-be developers. "Code. Build. Innovate.". Yeah, riiiight.
Secondly, if I'm a developer doing something new and cool, maybe I don't *want* to reveal how I'm doing it. Maybe I don't want to make it easy for anyone, including Apple, to copy my application. It's my code, not Apple's and there are several incidents where this has happened*.
Thirdly, when an entity controls the production, the platform and the software distribution, what you end up with is just monopoly. I'm sure Apple would love to be the only name in the game and that's exactly what they are shooting for. They want to be the Microsoft of the mobile world. If that happens you will have no choice but whatever choice is made by Apple for you. Obviously, some people really like being led around by a nose-ring or Apple wouldn't be so popular.
some legacy programs are still going to want/usr/local. what i see happening is a bunch of symlink workarounds that end up just confusing everyone. seems like there could be other things to spend time on improving.
It comes down to cost. Trying the plan for that last 5% of disasters that only happen 1% of the time is cost prohibitive. At some point, sad as it may seem, money does become more important than the consequences. I don't think Fukishama will be the last, nor the worst, disaster this population ever sees but it will make engineers a little more careful. For a while.
Follow the money, follow the greed, find the power, find the corruption. It's a pretty common theme and has been going on for decades. Most of you may be too young to remember (http://www.wnd.com/index.php?pageId=4314)
This should not happen on a high risk/high potential system. If it does, either your security team, or policy enforcer/makers, need to be replaced. Period.
People who get busted for parking in handicapped stalls should be forced to use a wheelchair for a week instead of a ticket. It's inconsiderate, lazy and just plain douchebaggery. Don't care who you are.
ftfpdf: "...Precipitation deposited a large fraction of 137CS on land surfaces...The plume was also dispersed quickly over the entire Northern Hemisphere, first reaching North America on 15 March and Europe on 22 March."
After reading this, I wonder what kind of impact Nagasaki/Hiroshima/Chernobyl had globally. It seems to me that until we have a good disaster plan in place we should stop building these friggin things. We need a better a way of dealing with the catastrophes other than just waiting around for it to burn itself out. I really like going outside on nice days and *not* having to sleep under a lead blanket.
It's one of the ubiquitous technologies which always seems to have something crippling it. Interference, noise, hardware compatibility, exploits, proprietary protocols. The 2.4Ghz problems will evolve the same way on the 5Ghz band. The only reason it's not a problem now is the reason stated in the article. Not that many devices are in the 5Ghz band.
That's more of an argument for security through obscurity.
Chrome implements Native Code Execution* in a web browser and it was a bone-headed move from the start. The only technology I can think of that may be more idiotic is executing code handed off from an email attachement. And look where that got us. Google assumed a huge liability implementing NCE and this proves you cannot take that kind of gamble because you simply cannot make a guarantee about absolute bug-free code.
Just want to say thanks for having the balls to go into a miserable situation and put your ass on the line for a bunch of people you don't know and then had to stay for reasons very few knew about.
I see what they are doing here with the "soon, Soon, SOON" business. The android project is obviously suffering from endless feature-creep. The project manager is trying to get the devs to implement every cool feature he sees in other systems. This is causing delays.
The android devs are clearly spending all the profits on booze, blow, hookers and Ferraris. Google will go bankrupt soon and be purchased by another mobile OS company. Said future owner will hurry-up-and-finish ICS to get the source code out the door.
> Because that's the real issue that most skeptics have been questioning of late.
It's too late for finger pointing as we are already in a positive feedback system* with global warming. We are headed for really uncomfortable living conditions within the next 50 years and whether it's been produced thorough anthropogenic, or natural, means isn't the first question to ask. We need to figure out what the next step is with millions of communities under water along with the land masses they used to produce food. That's not something we want to have to try and solve at the last minute (but historically speaking, we probably will attempt to).
Slashdot Mirror
If you have music, we own it. If you have a computer with music on it, we own that too. If your computer is in your car, parked in front of your house guess what? ours.
B&N is coming to the "media" tablet party a bit late. They should have found a way to trim $50 off the tablet to directly compete with the Fire. By not doing so, they won't be converting too many of the faithful kindle crowd.
Maybe: ..Not a chance
- stick with your current phone for 4 years?
- skip your next computer upgrade for 5 years?
- settle on a 24" LCD instead of the 92" plasma?
It's disturbing that we've put our own neck in the noose but just keep tightening the rope.
Let's just call it defunct.
Generally speaking, when your market share increases, so do the amount of devices you have in service. The more devices you have in service, the higher the percentage of failed devices. It's math, not magic.
http://www.eurodroid.com/2011/04/26/stats-android-now-10-ahead-of-iphone-in-us-smartphone-market-share/
http://www.techi.com/2011/08/android-ios-approach-70-combined-smartphone-market-share/
Why, at a technical level, is this so bad?
Ok, for starters it's another innovation killer. By Apple bolstering it's control of the platform, in yet another authoritarian way, it raises the frustration level for the developer and many would-be developers. "Code. Build. Innovate.". Yeah, riiiight.
Secondly, if I'm a developer doing something new and cool, maybe I don't *want* to reveal how I'm doing it. Maybe I don't want to make it easy for anyone, including Apple, to copy my application. It's my code, not Apple's and there are several incidents where this has happened*.
Thirdly, when an entity controls the production, the platform and the software distribution, what you end up with is just monopoly. I'm sure Apple would love to be the only name in the game and that's exactly what they are shooting for. They want to be the Microsoft of the mobile world. If that happens you will have no choice but whatever choice is made by Apple for you. Obviously, some people really like being led around by a nose-ring or Apple wouldn't be so popular.
[0] - http://articles.businessinsider.com/2011-06-10/tech/30007890_1_app-store-ios-idevices
[1] - http://www.itproportal.com/2011/06/11/apple-rips-off-developer-brands-app-as-its-own/
some legacy programs are still going to want /usr/local. what i see happening is a bunch of symlink workarounds that end up just confusing everyone. seems like there could be other things to spend time on improving.
Glad to know we're getting an unbiased opinion.
Nepomuk must be indexing the files on his server right now.
> stands no chance getting past the Republicans in the
> House (hell, he couldn't even get it through the Democrats in
> the Senate).
Can't blame the guy for trying. Maybe we need a new House/Senate?
It comes down to cost. Trying the plan for that last 5% of disasters that only happen 1% of the time is cost prohibitive. At some point, sad as it may seem, money does become more important than the consequences. I don't think Fukishama will be the last, nor the worst, disaster this population ever sees but it will make engineers a little more careful. For a while.
give encrypted files to siblings. give private keys to trusted friend(s).
39,731 is the exact number of milliseconds it takes to lose interest in an Apple fanboi blog.
Follow the money, follow the greed, find the power, find the corruption. It's a pretty common theme and has been going on for decades. Most of you may be too young to remember (http://www.wnd.com/index.php?pageId=4314)
Commits to open source, then commits to extinguishing it.
http://www.tuxmachines.org/node/45131
This should not happen on a high risk/high potential system. If it does, either your security team, or policy enforcer/makers, need to be replaced. Period.
People who get busted for parking in handicapped stalls should be forced to use a wheelchair for a week instead of a ticket. It's inconsiderate, lazy and just plain douchebaggery. Don't care who you are.
ftfpdf:
"...Precipitation deposited a large fraction of 137CS on land surfaces...The plume was also dispersed quickly over the entire Northern Hemisphere, first reaching North America on 15 March and Europe on 22 March."
After reading this, I wonder what kind of impact Nagasaki/Hiroshima/Chernobyl had globally. It seems to me that until we have a good disaster plan in place we should stop building these friggin things. We need a better a way of dealing with the catastrophes other than just waiting around for it to burn itself out. I really like going outside on nice days and *not* having to sleep under a lead blanket.
It's one of the ubiquitous technologies which always seems to have something crippling it. Interference, noise, hardware compatibility, exploits, proprietary protocols. The 2.4Ghz problems will evolve the same way on the 5Ghz band. The only reason it's not a problem now is the reason stated in the article. Not that many devices are in the 5Ghz band.
> The link indicates it is far from easy.
That's more of an argument for security through obscurity.
Chrome implements Native Code Execution* in a web browser and it was a bone-headed move from the start. The only technology I can think of that may be more idiotic is executing code handed off from an email attachement. And look where that got us. Google assumed a huge liability implementing NCE and this proves you cannot take that kind of gamble because you simply cannot make a guarantee about absolute bug-free code.
[*] - http://www.theregister.co.uk/2010/06/25/mozilla_on_npapi_pepper/
Just want to say thanks for having the balls to go into a miserable situation and put your ass on the line for a bunch of people you don't know and then had to stay for reasons very few knew about.
Seems to me Microsoft is now attempting to do with compilers what they attempted to do with the mobile phone.
I see what they are doing here with the "soon, Soon, SOON" business. The android project is obviously suffering from endless feature-creep. The project manager is trying to get the devs to implement every cool feature he sees in other systems. This is causing delays.
The android devs are clearly spending all the profits on booze, blow, hookers and Ferraris. Google will go bankrupt soon and be purchased by another mobile OS company. Said future owner will hurry-up-and-finish ICS to get the source code out the door.
> Because that's the real issue that most skeptics have been questioning of late.
It's too late for finger pointing as we are already in a positive feedback system* with global warming. We are headed for really uncomfortable living conditions within the next 50 years and whether it's been produced thorough anthropogenic, or natural, means isn't the first question to ask. We need to figure out what the next step is with millions of communities under water along with the land masses they used to produce food. That's not something we want to have to try and solve at the last minute (but historically speaking, we probably will attempt to).
[*] - http://www.agu.org/pubs/crossref/2006/2005GL025044.shtml
Wonder if you can get around it by relocating the server (and payment system?) to a state/country where it's legal.