It is absolutely Emacs' fault that that the default keybindings are still set up for MIT Lisp machines (Super and Meta? In 2014? Really??).
It is also emblematic of the problems within Emacs' user community that they can say with apparent seriousness that the problem is every keyboard and OS since nineteen-seventy-fscking-five "breaking compatibility" with Emacs, instead of their own failure to adapt to a changing environment.
I'm an expert observer of my own environment, and have noticed that now that they're built into every phone OS it's been a decade since I was more than a few steps from the nearest calculator.
What value does being able to rattle off the old times table have when you're sitting in front of a computer (with a calculator app), with a smartphone in your pocket (ditto), and probably a desk calculator with some vendor's logo on it (since they're about $0.99 in bulk)?
Right, but all the sound reveals is whether the CPU is busy or idle (or more likely, how much current it's drawing). Adding random-length pauses exactly at the steps where knowing whether the CPU goes idle leaks part of the key would break this sort of listening attack.
With multi-core processors it might even be possible to mask the sound by starting up another thread to do useless work that sounds like encryption but isn't...
Because eventually they will. But when they do, they'll be a monopoly that's in the business of selling gigabit+ symmetric connections at a price mere private individuals can afford.
"Home" service from the current monopolies top out around 100 Mbits down and 10 up, and they show no sign of wanting to push those top speeds up, probably out of fear of cannibalizing the huge margins on their $250+/month "business" lines.
- 0 Counter negative points raised in "The Everything Store" and recent news stories about poor working conditions in Amazon warehouses. Steer the narrative about Amazon toward how they're building the shiny future instead of how they're out-Walmarting Walmart.
Not well, from what I can see. It requires buying/building hardware, and you have to remember to take the device if you want to access a stored password away from home. KeePass + Dropbox goes everywhere my phone does.
It's something else altogether, originally it was a project to put a multitasking kernel, TCP/IP stack, GUI, and web browser on a Commodore 64, and has since gone in a mesh networking internet-of-things sort of direction. There was a Slashdot article on the original desktop-oriented release, but the links are all dead.
Under Renault's scheme, you don't own the battery, just the frame
The worst of both worlds! In 5 years, instead of a car that's hard to sell because potential buyers don't know the condition of the battery, you'll have a car that's impossible to drive or sell because the battery was returned to Renault after the lease ended.
My example isn't "bad" just because you don't like the conclusion.
Define what "coding" means to you. There are two possible categories that definition can fall into: One so over-broad that it's meaningless but that includes nearly everyone, and one that fits what other people mean when they say "coding" but excludes a vast majority of reasonably happy competent people who hold jobs where 90% of their work day is spent using a computer.
Funny, when XP launched the Slashdot consensus was that it was 'goddamned Fischer-Price crap' for consumers who didn't care about the lack of signed drivers for (your favorite obscure ISA card here), and real big boy computers ran Linux, UNIX, or Win2k if you really needed Microsoft software.
It's really not, at least not unless you're going to expand the definition of "coding" to silly lengths that would include trivial stuff like Excel formulas. Those are mainstream job skills, proper coding is a niche skill.
Or to turn it around, if one absolutely must (FULL STOP!) know how to code to operate a computer, then operating a computer is self-evidently not a skill that everyone needs, as can be seen by the number of functioning adults who can't code "hello world" in python.
There's a lot more to "3D Television" than just a TV with a 3D capable panel in it.
How many of those people own the glasses? And a 3D blu-ray player (with the required HDMI 1.whatever cables)? And 3D discs (or if you want to get into really amazingly minuscule market share numbers, 3D cable/satellite programming)?
"Shuttleworth has neither given up nor been surpassed by another competitor in this area."
But he has been surpassed. Microsoft has already successfully foisted their clunky tablet UI on millions of desktop users who bought machines pre-loaded with Windows 8!
Rid of Flash and Silverlight? Netflix working properly on non-Windows systems?
The alternative was never "no more DRM on the web", it is (and would continue to be) "DRM that brings along its own bloated, proprietary, buggy application runtime along".
That said, I think it's worth asking: if machines are going to replace all our fast food workers, are we going to start paying our gourmet chefs minimum wage just because we can?"
Of course we are. In fact, we're already doing it. 20 years ago any restaurant or hotel of note had a pastry chef on staff, now they mostly serve premade desserts that come frozen from factories where machines and fewer low-wage workers do the former jobs of many well-paid chefs.
There isn't unlimited risk though. If a user is going to win a lawsuit, they have to show their data was leaked because of your negligence, not just bad luck. As long as you follow enough "industry best practices" (obvious shit like "have a firewall" and "don't give employees admin rights") to appear non-negligent to a jury of techno-illiterate old folks, you'll be fine.
You should. Short-circuiting AES-NI to return the plaintext XORed with the output of (weakened) rdrand would mean that the intended recipient can't decrypt the message. That's a lot of hard engineering work to tap a communication channel that nobody can actually communicate over...
When, in the course of the NSA revelations, have you gotten the impression that "if X became public knowledge... it would be the death blow to the current Y" was ever a consideration in whether or not they did X?
Slashdot Mirror
It is absolutely Emacs' fault that that the default keybindings are still set up for MIT Lisp machines (Super and Meta? In 2014? Really??).
It is also emblematic of the problems within Emacs' user community that they can say with apparent seriousness that the problem is every keyboard and OS since nineteen-seventy-fscking-five "breaking compatibility" with Emacs, instead of their own failure to adapt to a changing environment.
What punishment can we impose if they don't live up to that demand?
(Hint: nothing.)
I'm an expert observer of my own environment, and have noticed that now that they're built into every phone OS it's been a decade since I was more than a few steps from the nearest calculator.
What value does being able to rattle off the old times table have when you're sitting in front of a computer (with a calculator app), with a smartphone in your pocket (ditto), and probably a desk calculator with some vendor's logo on it (since they're about $0.99 in bulk)?
Oh for fuck's sake. Yes. Memorizing tables is not math, it's an exceptionally boring party trick.
Right, but all the sound reveals is whether the CPU is busy or idle (or more likely, how much current it's drawing). Adding random-length pauses exactly at the steps where knowing whether the CPU goes idle leaks part of the key would break this sort of listening attack.
With multi-core processors it might even be possible to mask the sound by starting up another thread to do useless work that sounds like encryption but isn't...
That's dinosaur thinking, though. If they were streaming, they could sell every viewer in every "slot" to the optimum advertiser.
Also, Mac OS X is essentially a fork of FreeBSD.
+5, Funny
Because eventually they will. But when they do, they'll be a monopoly that's in the business of selling gigabit+ symmetric connections at a price mere private individuals can afford.
"Home" service from the current monopolies top out around 100 Mbits down and 10 up, and they show no sign of wanting to push those top speeds up, probably out of fear of cannibalizing the huge margins on their $250+/month "business" lines.
...because it had been developed on Macs. Halo was mostly finished when MS borged Bungie.
You missed the major one:
- 0 Counter negative points raised in "The Everything Store" and recent news stories about poor working conditions in Amazon warehouses. Steer the narrative about Amazon toward how they're building the shiny future instead of how they're out-Walmarting Walmart.
Not well, from what I can see. It requires buying/building hardware, and you have to remember to take the device if you want to access a stored password away from home. KeePass + Dropbox goes everywhere my phone does.
It's something else altogether, originally it was a project to put a multitasking kernel, TCP/IP stack, GUI, and web browser on a Commodore 64, and has since gone in a mesh networking internet-of-things sort of direction.
There was a Slashdot article on the original desktop-oriented release, but the links are all dead.
Under Renault's scheme, you don't own the battery, just the frame
The worst of both worlds! In 5 years, instead of a car that's hard to sell because potential buyers don't know the condition of the battery, you'll have a car that's impossible to drive or sell because the battery was returned to Renault after the lease ended.
Anyone else reading that as "US Has Radically Advanced Facial Recognition Software, Wants To Phase In Use In Unclassified Programs In 2014-2018"?
Or has my Snowden Cynicism gone too far?
If you think Obama's policies are representative of any sort of a "left", you watch way too much American TV news.
My example isn't "bad" just because you don't like the conclusion.
Define what "coding" means to you. There are two possible categories that definition can fall into: One so over-broad that it's meaningless but that includes nearly everyone, and one that fits what other people mean when they say "coding" but excludes a vast majority of reasonably happy competent people who hold jobs where 90% of their work day is spent using a computer.
Funny, when XP launched the Slashdot consensus was that it was 'goddamned Fischer-Price crap' for consumers who didn't care about the lack of signed drivers for (your favorite obscure ISA card here), and real big boy computers ran Linux, UNIX, or Win2k if you really needed Microsoft software.
It's really not, at least not unless you're going to expand the definition of "coding" to silly lengths that would include trivial stuff like Excel formulas. Those are mainstream job skills, proper coding is a niche skill.
Or to turn it around, if one absolutely must (FULL STOP!) know how to code to operate a computer, then operating a computer is self-evidently not a skill that everyone needs, as can be seen by the number of functioning adults who can't code "hello world" in python.
There's a lot more to "3D Television" than just a TV with a 3D capable panel in it.
How many of those people own the glasses? And a 3D blu-ray player (with the required HDMI 1.whatever cables)? And 3D discs (or if you want to get into really amazingly minuscule market share numbers, 3D cable/satellite programming)?
"Shuttleworth has neither given up nor been surpassed by another competitor in this area."
But he has been surpassed. Microsoft has already successfully foisted their clunky tablet UI on millions of desktop users who bought machines pre-loaded with Windows 8!
Rid of Flash and Silverlight? Netflix working properly on non-Windows systems?
The alternative was never "no more DRM on the web", it is (and would continue to be) "DRM that brings along its own bloated, proprietary, buggy application runtime along".
That said, I think it's worth asking: if machines are going to replace all our fast food workers, are we going to start paying our gourmet chefs minimum wage just because we can?"
Of course we are. In fact, we're already doing it. 20 years ago any restaurant or hotel of note had a pastry chef on staff, now they mostly serve premade desserts that come frozen from factories where machines and fewer low-wage workers do the former jobs of many well-paid chefs.
There isn't unlimited risk though. If a user is going to win a lawsuit, they have to show their data was leaked because of your negligence, not just bad luck. As long as you follow enough "industry best practices" (obvious shit like "have a firewall" and "don't give employees admin rights") to appear non-negligent to a jury of techno-illiterate old folks, you'll be fine.
"I have my doubts"
You should. Short-circuiting AES-NI to return the plaintext XORed with the output of (weakened) rdrand would mean that the intended recipient can't decrypt the message. That's a lot of hard engineering work to tap a communication channel that nobody can actually communicate over...
When, in the course of the NSA revelations, have you gotten the impression that "if X became public knowledge... it would be the death blow to the current Y" was ever a consideration in whether or not they did X?