Replying to myself as this is somewhat a tangent. The other bone to pick on this topic is their efforts to place wireless service at the same level as wired service. They are two completely separate beasts, and in my book, wireless services (probably including WiFi and other non-cellular distribution, but I'd have to think/research before crapping out an opinion on that one) simply cannot meet all of my requirements for a fully usable internet connection. Basically, if birds, weather, RF interference, shared-medium congestion, or other factors largely outside the control of myself and the ISP can semi-reliably degrade the service, it doesn't fit my needs.
Personally, I am all for leaving it as it is, but I do agree it was a bit much of a leap (at the time), though the previous definition had been there for ~5 years. Their game, as I see it, is basically to rewrite it so that basically everyone already has broadband, in the interest of ISPs not having to do anything to catch up. Even if the leap in definition was arguably excessive, dialing it back after having worked with it for several years is indeed a regression. I will admit that it would be narrow-minded to not consider the points you have made, as I do often forget to travel those lines of thought. A progression like 4-10-20 at the same intervals would've been more palatable to more people, I suspect, but too much conflict leads to each side taking as much as they can whenever they can (which is another issue in itself).
Couldn't really determine if I should downmod (i don't downmod for factual inaccuracies) this, so I reply instead. Trust me, my comment here is worse than any downmod. I feel the actual content has been addressed by other commentators, but I will give a car analogy. This is similar to buying a car, and then having to deactivate 1 or 2 cylinders on the engine, or locking out overdrive, to avoid some undesirable situation. You're calling 'firing on all cylinders' an optional feature; cars don't need an engine in the first place, of course.
Spectre (speculative execution bug) affects them all, Meltdown (memory privilege check dodging) does not appear to affect non-Intel processors, but that could always change. The the vilification, at least from my perspective, stems more from their denialist (it's working as intended, hyuk!) attitude towards the thing.
I, for whatever reason, felt slightly mislead by the inability of the systems to operate at > 54 kbit/s. However, compression made 56K modems borderline tolerable in a pinch, even into the mid 2000s.
Forgot about 28.8 (same spec as the 33.6K, v.34), which is what my family had when I was growing up in the early 90s. 33.6 and later 56K v.92 seemed like a nice step up.
Adequate for you, but 'broadband' definitions should only ever escalate. Unless the notion that we're being run by a bunch of regressive bastards is true...
The ones that require JavaScript to display basic page content, where there was not some reasonable reason (e.g. highly dynamic content) to do so? Yes kinda. Trying to make semi-arbitrary remote code execution a requirement for viewing one's site makes me desire to avoid using their site.
Context: non-PMR laptop hard drive ca. 2003, I accidentally knocked over a speaker cabinet at the foot of my bed while sleeping, and like a dope just put the laptop back on top of it still lying down... didn't realize what i'd done until the next day. Hard drive's data was effectively destroyed within 12 hours, but had been accessible remotely ~8 hours after the incident. Somehow the servo track patterns survived, as the drive was usable after reformatting, and showed no defect via MHDD. Speaker was definitely not shielded, and the drive was perhaps 6 inches from the ~3" ring magnet. I believe PMR to be substantially more resistant to effects of random external magnetic fields.
That being said, the thing I've seen fail first in hard drives I've assaulted with magnets is the fluid dynamic bearing on the spindle; if you stick a powerful magnet directly on it, it drags the rotating shaft down into the thrust bearing (or equivalent)... ball bearings survive much, much longer in this situation, but do grind themselves up fairly fast. Anyhow, if a large demagnetizer won't do it, just stick some massive NdFeB magnets on the system/rack and see what happens.
Dumb pipes or bust. Most people don't need/want the dumb pipe it seems, but at least make it available. They could literally charge more for doing less, but they don't want to, I guess.
Slashdot Mirror
Replying to myself as this is somewhat a tangent. The other bone to pick on this topic is their efforts to place wireless service at the same level as wired service. They are two completely separate beasts, and in my book, wireless services (probably including WiFi and other non-cellular distribution, but I'd have to think/research before crapping out an opinion on that one) simply cannot meet all of my requirements for a fully usable internet connection. Basically, if birds, weather, RF interference, shared-medium congestion, or other factors largely outside the control of myself and the ISP can semi-reliably degrade the service, it doesn't fit my needs.
Personally, I am all for leaving it as it is, but I do agree it was a bit much of a leap (at the time), though the previous definition had been there for ~5 years. Their game, as I see it, is basically to rewrite it so that basically everyone already has broadband, in the interest of ISPs not having to do anything to catch up. Even if the leap in definition was arguably excessive, dialing it back after having worked with it for several years is indeed a regression. I will admit that it would be narrow-minded to not consider the points you have made, as I do often forget to travel those lines of thought. A progression like 4-10-20 at the same intervals would've been more palatable to more people, I suspect, but too much conflict leads to each side taking as much as they can whenever they can (which is another issue in itself).
Ceci n'est pas une commentaire.
There are some specific (very high-end) ARMs that are vulnerable as well.
Couldn't really determine if I should downmod (i don't downmod for factual inaccuracies) this, so I reply instead. Trust me, my comment here is worse than any downmod. I feel the actual content has been addressed by other commentators, but I will give a car analogy. This is similar to buying a car, and then having to deactivate 1 or 2 cylinders on the engine, or locking out overdrive, to avoid some undesirable situation. You're calling 'firing on all cylinders' an optional feature; cars don't need an engine in the first place, of course.
Actually, reading back through, apparently some very specific ARM stuff is Meltdown-compliant too. So AMD is the only one in the clear for now.
My deepest apologies, I was but a child at the time XD
Spectre (speculative execution bug) affects them all, Meltdown (memory privilege check dodging) does not appear to affect non-Intel processors, but that could always change. The the vilification, at least from my perspective, stems more from their denialist (it's working as intended, hyuk!) attitude towards the thing.
Grats on 0.9998356st post
I, for whatever reason, felt slightly mislead by the inability of the systems to operate at > 54 kbit/s. However, compression made 56K modems borderline tolerable in a pinch, even into the mid 2000s.
Forgot about 28.8 (same spec as the 33.6K, v.34), which is what my family had when I was growing up in the early 90s. 33.6 and later 56K v.92 seemed like a nice step up.
Adequate for you, but 'broadband' definitions should only ever escalate. Unless the notion that we're being run by a bunch of regressive bastards is true...
100% broadband penetration, ho! Took 'em long enough.
Unfortunately, cowards tend to live relatively long, comfortable (if unfulfilling) lives.
The ones that require JavaScript to display basic page content, where there was not some reasonable reason (e.g. highly dynamic content) to do so? Yes kinda. Trying to make semi-arbitrary remote code execution a requirement for viewing one's site makes me desire to avoid using their site.
I've seen some pretty sharp stones out there, perhaps moss?
Time to bust out my 486!
The gift that keeps on giving...
Something something, bistromathics.
... laws for thee and not for me ... the inversion.
You may note that I self-deprecated immediately after due to the absolutely awful comment; perhaps read follow-up replies to avoid redundancy.
Context: non-PMR laptop hard drive ca. 2003, I accidentally knocked over a speaker cabinet at the foot of my bed while sleeping, and like a dope just put the laptop back on top of it still lying down... didn't realize what i'd done until the next day. Hard drive's data was effectively destroyed within 12 hours, but had been accessible remotely ~8 hours after the incident. Somehow the servo track patterns survived, as the drive was usable after reformatting, and showed no defect via MHDD. Speaker was definitely not shielded, and the drive was perhaps 6 inches from the ~3" ring magnet. I believe PMR to be substantially more resistant to effects of random external magnetic fields.
That being said, the thing I've seen fail first in hard drives I've assaulted with magnets is the fluid dynamic bearing on the spindle; if you stick a powerful magnet directly on it, it drags the rotating shaft down into the thrust bearing (or equivalent)... ball bearings survive much, much longer in this situation, but do grind themselves up fairly fast. Anyhow, if a large demagnetizer won't do it, just stick some massive NdFeB magnets on the system/rack and see what happens.
Forgot to self-down-mod due to somewhat offtopic NN whining, if someone wants to take care of that.
Dumb pipes or bust. Most people don't need/want the dumb pipe it seems, but at least make it available. They could literally charge more for doing less, but they don't want to, I guess.
Bulk eraser comes to mind, BOFH style.