At this point the not quite stiff but still present competition from other OSes like Android will probably prevent any real inquiry from going forward.
Far more concerning is this push by Apple, quickly being followed by MS, to deny user-replaceable local storage and locally-loaded software. I'd hate to see the whole industry go that way.
I'm a big fan of the government not forcing people to do things against their will.
Good thing corporations aren't people, but legal fictions comprised of people whose sole goal is to generate profits for its shareholders. Considering how malicious they can be and how much more power over any individual or group of people that isn't absolutely massive, I have no problem letting the government force their hand, given they can show good cause.
Net Neutrality is something that must be forced, as they've already got huge swaths of the public bent over a barrel, telling us we've got the best service in the world while it's actually quite shit.
I've noticed something similar, pretty much every LCD monitor out these days at a reasonable price stops at 1920x1080, which is down from 1920x1200 a few years ago.
The flood of HDTVs on the market has basically locked everything at 1080p, with higher resolution displays nigh-upon impossible to find at a reasonable price, and nothing approaching a higher DPI is anywhere to be found except on mobile devices (which in a sense I can understand, but it's still disappointing.)
I guess it's no great surprise that in 2010 I am using a 1600x1200 display at work, which is the same that my laptop had in late 2001. Admittedly, I am using two...
At 8nm NAND will be lucky to function properly. MLC will be impossible.
SSDs will reach hard disk prices eventually, but not quite so soon. Rotating media isn't going anywhere for the time being, simply due to the capacity and how cheaply it can be had.
Linux is such a "me me me" culture where everything revolves around the sanctity of the kernel and how free and open it is, and no one appears to consider the ramifications of the actions.
What, they're WRONG for not allowing arguably more selfish proprietary driver vendors to decide the course for the kernel?
What's your point, that we should encourage closed drivers by setting the APIs in stone for years on end? Allow the non-open to dictate the actions of the open?
That's not -my- problem. It's theirs. They choose to stay closed, so when the APIs change no one else can fix it but them. They have no room to bitch about unstable APIs in an open kernel that is constantly changing, when they won't commit to being open themselves. Others do, and as a result don't have nearly the problems. It's a cost they must accept, or they can do as you suggest and stop.
It's complete and utter bullshit that cell phones are as powerful now as desktops were ten years ago sitting in the palm of my hand, and yet they have less than a third of the capability. And not a one of them is really interoperable with any other except on the most primitive level.
That's only because you're buying phones from your carrier, who demands they be crippled accordingly. Every once in a while you can get good, un-crippled phones from your carrier but they tend to carry higher fees.
The trick is to go to device vendors who recognize who their true customers are, namely the ones who use the phone daily. I bought an N900 and it gives Android a severe run for its money in terms of hackability and compatibility with existing Linux platforms. The catch is that you can't buy it in the US except at full price from Nokia, and most people stumble at spending $500 on a device they consider to be nothing more than a phone with a big screen.
The only people I've seen clamoring for a static, unchanging driver interface are those writing proprietary drivers. Last I checked, changes to the interfaces by someone puts the onus on them to fix all the calls to it in the kernel, which is why getting your driver into the tree is considered better than keeping it closed.
That said, if you're keeping your driver closed it's a problem you're bringing upon yourself.
Well, just removing the extra bullshit doesn't solve the fundamental problem of inhaling hot gases produced by the combustion of solid matter. You're still pulling things into your lungs they're capable of handling, but the regularity of it just overwhelms them.
I think the ALA here is seeing a "suggestiveness" due to the cigarette appearance, and it doesn't have anything to do with nicotine (I haven't seen them fuss about nicotine patches.)
I know, we shouldn't bother trying because some myopic anti-Pioneer has seen that IT IS IMPOSSIBLE and decreed it as such.
You're welcome to crawl into your little hole and die, if you wish. Others will, hopefully, not be torn down by the masses like you and at least make some effort to move out.
By that logic no one should publish software for the Mac, because someone could upload it. They should demand Apple implement a similar lockdown on the Mac.
Again, if "defending Apps from piracy" is their defense against an exemption, the utter lack of such protections on the Mac shows their standpoint is totally irrational and contradictory. Thus the obvious and rational explanation is that it protects their bottom line by keeping the gates closed.
What Apple objects to is people jailbreaking the iPhone to unlock apps so that they don't have to pay for them.
Apple is opposed to the proposed Class #1 exemption because it will destroy the technological protection of Apple's key copyrighted computer programs in the iPhone(TM) device itself and of copyrighted content owned by Apple that plays on the iPhone, resulting in copyright infringement, potential damage to the device and other potential harmful physical effects, adverse effects on the functioning of the device, and breach of contract.
Basically, they're full of shit. If ANY of that were a real justification for denying an exemption for jailbreaking, then they would have implemented the EXACT SAME SYSTEM OF LOCKDOWN ON THE MAC. The only reason against it is to prevent users (and developers) from bypassing the app store should they choose to.
Lack of lock-in means I can find and use an alternative without ads. Or better yet, use an open source alternative if one exists. iPhone users have no such choice.
The catch is that if it's easy to slap ads in your app, expect more to do so. And that's fine if Android follows suit, since you aren't locked into the Android Marketplace.
The multitasking method described is essentially identical to the one MS is using, with the process being halted in the background and the potential for it to be freed from memory at any time. The new addition is a background daemon or two that a program can contact to leave bits running while the rest is halted. Sort of a "low power multitasking." This is actually quite clever, and makes me wonder if it isn't using Grand Central closures to keep those bits spinning while the main process is halted.
The task switching method has apparently been cited as looking extremely similar to the way S60 switches. I wouldn't know, but that's pretty funny if true.
All in all, the critical juncture remains for me: The platform has been and will remain extremely closed. That alone is enough to ensure that I will stick with my N900 for the time being, and likely well into the future. I'll put my OS and developer interests behind MeeGo, and encourage openness.
IIRC, lithos down to 13nm are believed to be possible. NAND will start hitting terminal reliability problems below 20nm as the floating gates will likely hold 100 electrons (or less!) and far more susceptible to random drainage and bit errors way beyond what is currently experienced.
So we'll end up with more, higher-density, and fundamentally unstable nonvolatile memory. As I understand it, DRAM will be hitting this problem too, as the capacitors will become susceptible to spontaneous charge loss.
So basically the only way I can imagine this working is if they did something like putting a microswitch inside the USB connector, which is fine as long as you remember to unplug the cable at night, but that's hardly any different than unplugging the charger.
Actually that's hugely different. Instead of having to take the secondary action of unplugging the charger after unplugging the phone, detaching the phone cuts the charger out completely. One action, instead of two.
Slashdot Mirror
At this point the not quite stiff but still present competition from other OSes like Android will probably prevent any real inquiry from going forward.
Far more concerning is this push by Apple, quickly being followed by MS, to deny user-replaceable local storage and locally-loaded software. I'd hate to see the whole industry go that way.
Good thing corporations aren't people, but legal fictions comprised of people whose sole goal is to generate profits for its shareholders. Considering how malicious they can be and how much more power over any individual or group of people that isn't absolutely massive, I have no problem letting the government force their hand, given they can show good cause.
Net Neutrality is something that must be forced, as they've already got huge swaths of the public bent over a barrel, telling us we've got the best service in the world while it's actually quite shit.
I've noticed something similar, pretty much every LCD monitor out these days at a reasonable price stops at 1920x1080, which is down from 1920x1200 a few years ago.
The flood of HDTVs on the market has basically locked everything at 1080p, with higher resolution displays nigh-upon impossible to find at a reasonable price, and nothing approaching a higher DPI is anywhere to be found except on mobile devices (which in a sense I can understand, but it's still disappointing.)
I guess it's no great surprise that in 2010 I am using a 1600x1200 display at work, which is the same that my laptop had in late 2001. Admittedly, I am using two...
Thankfully, the DoJ isn't knocking on their door.
This is a Microsoft funded puppet whining about Google to the DoJ.
At 8nm NAND will be lucky to function properly. MLC will be impossible.
SSDs will reach hard disk prices eventually, but not quite so soon. Rotating media isn't going anywhere for the time being, simply due to the capacity and how cheaply it can be had.
What, they're WRONG for not allowing arguably more selfish proprietary driver vendors to decide the course for the kernel?
What's your point, that we should encourage closed drivers by setting the APIs in stone for years on end? Allow the non-open to dictate the actions of the open?
That's not -my- problem. It's theirs. They choose to stay closed, so when the APIs change no one else can fix it but them. They have no room to bitch about unstable APIs in an open kernel that is constantly changing, when they won't commit to being open themselves. Others do, and as a result don't have nearly the problems. It's a cost they must accept, or they can do as you suggest and stop.
That's only because you're buying phones from your carrier, who demands they be crippled accordingly. Every once in a while you can get good, un-crippled phones from your carrier but they tend to carry higher fees.
The trick is to go to device vendors who recognize who their true customers are, namely the ones who use the phone daily. I bought an N900 and it gives Android a severe run for its money in terms of hackability and compatibility with existing Linux platforms. The catch is that you can't buy it in the US except at full price from Nokia, and most people stumble at spending $500 on a device they consider to be nothing more than a phone with a big screen.
The only people I've seen clamoring for a static, unchanging driver interface are those writing proprietary drivers. Last I checked, changes to the interfaces by someone puts the onus on them to fix all the calls to it in the kernel, which is why getting your driver into the tree is considered better than keeping it closed.
That said, if you're keeping your driver closed it's a problem you're bringing upon yourself.
Hey retard,
Read the post I was replying to, which was pretty obviously referring to cigarettes themselves.
Well, just removing the extra bullshit doesn't solve the fundamental problem of inhaling hot gases produced by the combustion of solid matter. You're still pulling things into your lungs they're capable of handling, but the regularity of it just overwhelms them.
I think the ALA here is seeing a "suggestiveness" due to the cigarette appearance, and it doesn't have anything to do with nicotine (I haven't seen them fuss about nicotine patches.)
I know, we shouldn't bother trying because some myopic anti-Pioneer has seen that IT IS IMPOSSIBLE and decreed it as such.
You're welcome to crawl into your little hole and die, if you wish. Others will, hopefully, not be torn down by the masses like you and at least make some effort to move out.
Those are some pretty CG renderings, but a device with those specs and 3G would be receiving much more noise than, well... none.
It doesn't help that it claims to have a paltry 128MB of RAM and Android 1.6/
Why should you pay -more- to do something with your property that you should reasonably expect to be able to do anyway?
By that logic no one should publish software for the Mac, because someone could upload it. They should demand Apple implement a similar lockdown on the Mac.
Again, if "defending Apps from piracy" is their defense against an exemption, the utter lack of such protections on the Mac shows their standpoint is totally irrational and contradictory. Thus the obvious and rational explanation is that it protects their bottom line by keeping the gates closed.
Basically, they're full of shit. If ANY of that were a real justification for denying an exemption for jailbreaking, then they would have implemented the EXACT SAME SYSTEM OF LOCKDOWN ON THE MAC. The only reason against it is to prevent users (and developers) from bypassing the app store should they choose to.
Or how about the simple ability to pick an app that was denied entry into the App Store? Say, Opera Mobile if Apple denies it again.
Lack of lock-in means I can find and use an alternative without ads. Or better yet, use an open source alternative if one exists. iPhone users have no such choice.
The catch is that if it's easy to slap ads in your app, expect more to do so. And that's fine if Android follows suit, since you aren't locked into the Android Marketplace.
Couple things:
The multitasking method described is essentially identical to the one MS is using, with the process being halted in the background and the potential for it to be freed from memory at any time. The new addition is a background daemon or two that a program can contact to leave bits running while the rest is halted. Sort of a "low power multitasking." This is actually quite clever, and makes me wonder if it isn't using Grand Central closures to keep those bits spinning while the main process is halted.
The task switching method has apparently been cited as looking extremely similar to the way S60 switches. I wouldn't know, but that's pretty funny if true.
All in all, the critical juncture remains for me: The platform has been and will remain extremely closed. That alone is enough to ensure that I will stick with my N900 for the time being, and likely well into the future. I'll put my OS and developer interests behind MeeGo, and encourage openness.
I know, Government's right place is helping ISPs destroy the internet and screw the citizens of this nation. Right.
IIRC, lithos down to 13nm are believed to be possible. NAND will start hitting terminal reliability problems below 20nm as the floating gates will likely hold 100 electrons (or less!) and far more susceptible to random drainage and bit errors way beyond what is currently experienced.
So we'll end up with more, higher-density, and fundamentally unstable nonvolatile memory. As I understand it, DRAM will be hitting this problem too, as the capacitors will become susceptible to spontaneous charge loss.
Hey look, someone who's new here! Welcome to April Fool's Day, when Slashdot goes overboard.
Which leads directly into why Linus named the tool Git...
Actually that's hugely different. Instead of having to take the secondary action of unplugging the charger after unplugging the phone, detaching the phone cuts the charger out completely. One action, instead of two.
If this is what they're doing, it's pretty smart.