Most British plug sockets have per-socket switches, but I haven't seen glowing LEDs (which would be quite annoying surely in bedrooms!). I have seen a couple of plugs with LEDs, but never a switch. The British plugs have thicker prongs, but have three-prongs as standard.
All for $700. But you can use it as a digital photo frame, or output to a HDTV via HDMI.
I'd prefer a slower, cheaper CPU and more storage for when you can't access "the cloud". Indeed I think that netbooks targetted at the cloud should be using ARM Cortex CPUs and be priced under $250.
In most situations, visual effects implemented using the GPU use less CPU resources overall than even simple CPU-based compositing with no effects.
And Gnome is running on Compiz, so it has them anyway. KDE is no different. I haven't read anything about instability or resource hogging with KDE 4.3. Gnome has some odd behaviours however, and incredible desktop switch sensitivity. In addition the virtual desktop manager often refuses to hide the hovering window descriptions once displayed (and it will display them even if you don't put the mouse near the virtual desktop manager, when you switch desktops).
My problem is that UIs for Gnome applications are primitive, clunky and poorly laid out, which is actually a bad thing for work. It's like they use Duplo blocks instead of pixels sometimes, they're that clunky.
I can barely make out the network and audio icons any more in the taskbar.
Gnome is just out of date. It's akin to XP when the competition has moved to Win7/SL. The UI is simply CRAP. This translates directly to Ubuntu.
The upgrade seemed to go okay for me, but there were problems with PostgreSQL and VirtualBox-ose. Also the upgrade terminal was full of DBus errors. These are things that would terrify a normal user (granted they wouldn't have installed PostgreSQL probably). The upgrade process wasn't automated, so you couldn't leave it alone to do its thing.
Firefox is updated, but has no options, and comes with an annoying default tab behaviour.
Empathy seems to work, but it is a really primitive chat client. This is probably due to using Gnome.
I think I'll wipe and try Kubuntu instead. KDE 4.3 is meant to be good.
I've used Ubuntu with Gnome for around 30 months as well. Gnome is going nowhere though, and it's looking more and more dated to me (not in terms of looks, a nice theme isn't the problem, it's the design of UIs that seems rather archaic, or in Empathy's case you just need to compare it to Adium on Mac OS X to see how clunky it is.
Indeed they should be able to come out and say "in terms of the existing law on distracted driving, the following activities are classified as distractions or dangerous: (1) talking or texting via a mobile phone, (2) adjusting a non-mounted GPS, MP3 player or other handheld electronic gadget, (3) lewd behaviour with a passenger or by oneself, (4) listening to right wing propaganda radio stations, (5) sleeping."
This just stops the arguments in court that it wasn't dangerous. It should be the law saying "no arguments are possible in these situations". Saves the public purse, and it lets people know where they stand. Odd that they make them separate laws though...
This is why I think Tesla should market to Europe more - smaller countries, smaller distances driven, and far more green-friendly governments and policies.
Also you would hope that the GPS would be linked to capacity and tell you if you can make it, and where recharge stations are en-route.
However I'm a fan of having an on-board small-capacity traditional engine that is used solely as a generator rather than being tied into the complexities of the car propulsion system. If that would generate enough charge to let me limp those ten miles it might be okay.
And in ten years, when the technology is affordable, hopefully the technology will have matured to a point where none of this is an issue. Even to the point of solar roofing options for trickle charging during the day (and simultaneously keeping the car cool inside). Not that this option would help me in Britain...
"it requires you to take your hands off the wheel"
Sucks if you drive a manual then. No changing gear for you!
Why are people in the position to make laws so small-brained? How do they fail to see the grand picture? Driving carelessly should already be an offense, changing GPS target or tweaking the stereo or heating/AC as your drive through a busy junction is already careless or dangerous driving! Doing it on a straight road with sparse traffic isn't, as the time your eyes are off the road in front of you is minimal and you'll have checked for relevant hazards.
On the other hand, modern cars have a lot of controls on the wheel itself, including gear change and stereo control. Wonder if this pretty much makes these "optional extras" mandatory in that state? Wonder if any car companies made a campaign contribution?
"The Cortex-A9 power-optimized hard macro implementation delivers its peak performance of 4000 DMIPS while consuming less than 250mW per CPU when selected from typical silicon."
A Cortex A5 core (inc L1 cache) is 1/9th the size of an Atom core (inc L1 cache). It will use far far less power. It is probably slower, clock for clock (I believe that A8 is competitive, clock for clock, and A9 beats Atom handily).
A5 and Atom aren't competing however. A5 is in the market that Atom would like to be in in 3 or 4 generations. It's 0.9mm^2 in area!
However ISA is getting less and less relevant. Android has applications run via a JIT,.NET is a JIT, Java has been JIT for years. The native platforms are probably Apple (but it's completely portable, and supports fat binaries on the desktop, but I reckon they could migrate iPhone ISA within a year if they wanted to), Nokia (Maemo), and legacy.
So you exclude the.NET applications (as.NET would be ported to ARM by Microsoft).
And you stop considering the system calls (as they would be native ARM anyway).
Then you consider that technology on the old Alpha (FX!32) could do x86 to Alpha translation at a speed that was acceptable for most applications. That was a long time ago.
Older applications will not feel slow on an binary translated (not interpreted) x86.
Leading-edge games will fail. Serious software will be turgid. Neither will be run on Atom systems anyway.
Microsoft can use it to leverage.NET (i.e., migrate developers to newer technologies).
But yes, an x86-to-ARM JIT recompiler is required. There are companies that specialise in such things like Transitive (who provided Apple's Rosetta technology for PPC on x86). I don't think this would be a roadblock.
First, 2GHz dual/quad ARM Cortex A9s are required.
As the A5 is a lesser CPU than the A8, I expect the iPhone to never utilise it, but to migrate to the A9, and potentially dual-core A9, with the next release in July next year.
You would think that in certain territories they would come to an arrangement with a native provider.
Going with AT&T is strange. T-Mobile, Vodafone, Telefonica, Three all have large international networks and one of these would be a far more logical provider for Europe than AT&T.
Instead they're going to make the product worthless and expensive.
Maybe those 40 other companies licensed them as part of a broader licensing package, rather than specifically. Without someone doing an analysis of the patents involved, and how Apple have implemented the similar features (patents protect a specific way of doing something, not the something), we won't know.
It'll end up with Apple paying a nominal fee and cross-licensing their multitouch and other mobile patents, so Nokia won't have to worry about them in the future, and thus can remain a relevant company in the mobile marketplace.
It seems the momentum is with Android for "OEM handsets", the handsets that would previously have used Windows Mobile have migrated en-mass to a cheaper, more modern, sellable phone OS.
It just convinces me that Windows Mobile 6.5 is too little, too late, and it doesn't offer much anyway. Windows Mobile 7 - presumably their next-generation mobile OS - is horribly delayed and will be feature-poor (generation 1) in comparison to Android, WebOS and iPhone OS. Maemo is on the sidelines too, for Nokia.
The past ten years have been gutting for the platform. Poor owners of the trademarks, poor hardware that was late, late delivery of the new OS (although bringing an OS from 1991 on to a new platform ten years later isn't easy), community splits (Genesi, MorphOS), and more killed it.
The hard work of the OS developers and a few small hardware companies have kept the platform trundling along. Now the OS developers own the OS rights, maybe things can be done to move forward. A port to ARM Smartbooks seems the most logical step (or creating PowerPC Smartbooks using embedded PowerPC cores), the competing platform are Android and Chrome OS, Windows Mobile, and netbook remixes of traditional Linux platforms.
The Amiga Inc company was running the brand into the ground via incompetence and very weird behaviour (asset switching between companies to avoid bankruptcies, etc). Hyperion have been trying to develop the market for a long time, so it is good that they have control now. I hope they port to ARM for upcoming Smartbooks.
It's well worth reading reviews c. 1985 - 1992 of the Amiga, to see how special it was back then. Hardware-wise, any modern PC in the last ten to fifteen years has been Amiga-like, with dedicated co-processors for graphics, audio, etc. OS-wise, AmigaOS is behind modern systems, but it had some niceties, I found the filesystem layout nice for example, nicer than Unix. In 1985 to 1995 it was simply far ahead technically. Lack of investment killed it though.
However my Amiga related shortcuts live in a bookmarks folder alongside my 8-bit computing links - the folder's called "Retro". I wish them all the best of luck, but I think they're five years too late. Actually, in 1998 I made a post here saying that AmigaOS would be perfect for a Palm-like device. Shame.
I have to agree. Many people, in general, are quirky, weird, different. Not just developers.
The reasons for this might be different. I believe a lot of us, due to social exclusion early in life (i.e., early weirdness causing disenfranchisement?) discovered the computer.
I've also seen amazingly sane normal people in the field (and other fields).
Namely to pre-mix DRIVE THROUGH sales with milk and sugar as per customer requirements. Therefore lid doesn't have to come off the cup, and spillages won't happen.
And it isn't 24 million drive through coffee sales. The majority of coffee sales will be in-store. Extending that to drive through sales without a risk analysis of giving people in a car scalding hot drinks that require complex manipulation (lid off flexible cup held between legs in car seat to add milk and sugar) with risk of spillage was foolish - as I said, you don't need to be Einstein to work out what would eventually happen.
They had previously paid out $500,000 for those accidents, and they hadn't done a single thing to assess how to reduce them.
Stop sucking up to big corporations and excusing them for their mistakes and lack of foresight.
So they sold 24 million cups of coffee to people in cars via the drive-through counter, as with this case? The accident wouldn't have happened if the milk and sugar was added beforehand, and all those posts here talk about how the milk and sugar addition reduces the temperature for consumption. Yet to add the milk/sugar, she had to remove the lid on the coffee, which caused the accident. It was bound to happen sooner or later. The case seems perfectly reasonable, there was no aspect of "getting rich" about it, unless you think having your genitals scalded off is an acceptable price to get for a few hundred thousand dollars.
They sold scalding coffee to customers via the drive-through kiosk. The customers then added their own milk and sugar afterwards, which required pulling off the lid - you know, those awkward lids you get on styrofoam cups of coffee.
You don't need to be Einstein to work out what would eventually happen.
All over your groin so you need two years of surgery, skin grafts on your penis, probably no sex ever again in your life.
All for a measly few hundred thousand dollars.
All because McDonalds thought that serving scalding hot coffee to people in cars (it was a drive-through) where they had to add the milk and sugar themselves (thus taking the lid off, which causes spills if you've ever done that with a coffee cup lid in such a place, it's difficult even on a steady table) was an acceptable practice.
Stop being a mouthpiece for McDonalds and accept that they were in the wrong, they were punished for it, they adjusted their working practices, and things are better now.
It's scalding hot so that the process of serving it means it is the right temperature when it is drunk. This includes factors like a MUG that absorbs some of the heat to get the coffee down to drinking temperature.
When it is still scalding hot at drinking time due to using insulating polystyrene cups amongst other factors such as McDonalds keeping the coffee too hot after brewing it, there's a problem.
I take you want your genitals scalded off by a minor accident caused by an everyday action?
In addition in normal coffee outsets people take the coffee and sit at a table. In a McDonalds there is a reasonable expectation that the coffee will be taken out, as it was in this case:
"ordered a 49 cup of coffee from the drive-through window of a local McDonald's restaurant. Liebeck was in the passenger's seat of her Ford Probe, and her grandson Chris parked the car so that Liebeck could add cream and sugar to her coffee. She placed the coffee cup between her knees and pulled the far side of the lid toward her to remove it"
How are McDonalds not at fault here? They served scalding coffee through the DRIVE-THROUGH, expecting the customer to take the lid off to add the milk and sugar. This is going to be done in the car seat. The lid is on too tightly, increasing risk of spills. Clearly McDonalds should have served the coffee with requested milk and sugar so this couldn't happen.
Did all these marketing emails from the stalkery creeps in the marketing agency include an opt-out statement, and other identifying statements that indicated that it was not real and who the source of the emails was?
I would be willing to bet that they weren't present.
As you say, consent should be revokable at any point, but if there is no mechanism to revoke, nor any method to identify the source in order to revoke by other means,
Never mind that "informed consent" surely means giving consent when informed of how the marketing campaign would actually work, i.e., that there would be stalkerish creepy emails.,
Sorry, the court case, which heard all the details, found her 20% to blame. So your opinion is just irrelevant and invalid. You can't just say ""Shares the blame". No, she IS to blame." as if you're some higher force of knowledge and wisdom.
McDonalds sold a product for consumption within a car that was horrendously unsafe for said scenario by being too hot for that scenario. The situation could have also been changed by having a cap that reduces spillages (and contains aromas as a side-benefit), and a sturdier container that didn't deform under mild pressure. There is an argument that they couldn't have anticipated this situation, but they had 700 accidents recorded over ten years, so...
Slashdot Mirror
Most British plug sockets have per-socket switches, but I haven't seen glowing LEDs (which would be quite annoying surely in bedrooms!). I have seen a couple of plugs with LEDs, but never a switch. The British plugs have thicker prongs, but have three-prongs as standard.
The shutters on UK plug sockets are built out of distilled Chuck Norris.
That's why the metal bits on the plugs are so fat and butch.
You can kill someone with a UK plug, and not only by leaving it lying around for someone to step on barefoot.
However it is a big plug, and a big socket. Someone did design a thin version though.
I liked Denmark's happy face design myself.
1280x800 display, 1.86GHz Atom, 1GB RAM, 2GB storage.
Yes, 2GB.
All for $700. But you can use it as a digital photo frame, or output to a HDTV via HDMI.
I'd prefer a slower, cheaper CPU and more storage for when you can't access "the cloud". Indeed I think that netbooks targetted at the cloud should be using ARM Cortex CPUs and be priced under $250.
In most situations, visual effects implemented using the GPU use less CPU resources overall than even simple CPU-based compositing with no effects.
And Gnome is running on Compiz, so it has them anyway. KDE is no different. I haven't read anything about instability or resource hogging with KDE 4.3. Gnome has some odd behaviours however, and incredible desktop switch sensitivity. In addition the virtual desktop manager often refuses to hide the hovering window descriptions once displayed (and it will display them even if you don't put the mouse near the virtual desktop manager, when you switch desktops).
My problem is that UIs for Gnome applications are primitive, clunky and poorly laid out, which is actually a bad thing for work. It's like they use Duplo blocks instead of pixels sometimes, they're that clunky.
Gnome does make a good netbook desktop however.
I can barely make out the network and audio icons any more in the taskbar.
Gnome is just out of date. It's akin to XP when the competition has moved to Win7/SL. The UI is simply CRAP. This translates directly to Ubuntu.
The upgrade seemed to go okay for me, but there were problems with PostgreSQL and VirtualBox-ose. Also the upgrade terminal was full of DBus errors. These are things that would terrify a normal user (granted they wouldn't have installed PostgreSQL probably). The upgrade process wasn't automated, so you couldn't leave it alone to do its thing.
Firefox is updated, but has no options, and comes with an annoying default tab behaviour.
Empathy seems to work, but it is a really primitive chat client. This is probably due to using Gnome.
I think I'll wipe and try Kubuntu instead. KDE 4.3 is meant to be good.
I've used Ubuntu with Gnome for around 30 months as well. Gnome is going nowhere though, and it's looking more and more dated to me (not in terms of looks, a nice theme isn't the problem, it's the design of UIs that seems rather archaic, or in Empathy's case you just need to compare it to Adium on Mac OS X to see how clunky it is.
Indeed they should be able to come out and say "in terms of the existing law on distracted driving, the following activities are classified as distractions or dangerous: (1) talking or texting via a mobile phone, (2) adjusting a non-mounted GPS, MP3 player or other handheld electronic gadget, (3) lewd behaviour with a passenger or by oneself, (4) listening to right wing propaganda radio stations, (5) sleeping."
This just stops the arguments in court that it wasn't dangerous. It should be the law saying "no arguments are possible in these situations". Saves the public purse, and it lets people know where they stand. Odd that they make them separate laws though ...
This is why I think Tesla should market to Europe more - smaller countries, smaller distances driven, and far more green-friendly governments and policies.
Also you would hope that the GPS would be linked to capacity and tell you if you can make it, and where recharge stations are en-route.
However I'm a fan of having an on-board small-capacity traditional engine that is used solely as a generator rather than being tied into the complexities of the car propulsion system. If that would generate enough charge to let me limp those ten miles it might be okay.
And in ten years, when the technology is affordable, hopefully the technology will have matured to a point where none of this is an issue. Even to the point of solar roofing options for trickle charging during the day (and simultaneously keeping the car cool inside). Not that this option would help me in Britain...
"it requires you to take your hands off the wheel"
Sucks if you drive a manual then. No changing gear for you!
Why are people in the position to make laws so small-brained? How do they fail to see the grand picture? Driving carelessly should already be an offense, changing GPS target or tweaking the stereo or heating/AC as your drive through a busy junction is already careless or dangerous driving! Doing it on a straight road with sparse traffic isn't, as the time your eyes are off the road in front of you is minimal and you'll have checked for relevant hazards.
On the other hand, modern cars have a lot of controls on the wheel itself, including gear change and stereo control. Wonder if this pretty much makes these "optional extras" mandatory in that state? Wonder if any car companies made a campaign contribution?
ARM recently released a 2GHz dual-core A9 hard-core for TSMC's process (40nm). I forget the power consumption, but it was quite low compared to Atom.
http://www.electronicsweekly.com/Articles/2009/09/16/46955/arm-produces-hard-cortex-a9-for-high-performance.htm
ah... http://www.arm.com/news/25922.html
"The Cortex-A9 power-optimized hard macro implementation delivers its peak performance of 4000 DMIPS while consuming less than 250mW per CPU when selected from typical silicon."
A Cortex A5 core (inc L1 cache) is 1/9th the size of an Atom core (inc L1 cache). It will use far far less power. It is probably slower, clock for clock (I believe that A8 is competitive, clock for clock, and A9 beats Atom handily).
A5 and Atom aren't competing however. A5 is in the market that Atom would like to be in in 3 or 4 generations. It's 0.9mm^2 in area!
However ISA is getting less and less relevant. Android has applications run via a JIT, .NET is a JIT, Java has been JIT for years. The native platforms are probably Apple (but it's completely portable, and supports fat binaries on the desktop, but I reckon they could migrate iPhone ISA within a year if they wanted to), Nokia (Maemo), and legacy.
So you exclude the .NET applications (as .NET would be ported to ARM by Microsoft).
And you stop considering the system calls (as they would be native ARM anyway).
Then you consider that technology on the old Alpha (FX!32) could do x86 to Alpha translation at a speed that was acceptable for most applications. That was a long time ago.
Older applications will not feel slow on an binary translated (not interpreted) x86.
Leading-edge games will fail. Serious software will be turgid. Neither will be run on Atom systems anyway.
Microsoft can use it to leverage .NET (i.e., migrate developers to newer technologies).
But yes, an x86-to-ARM JIT recompiler is required. There are companies that specialise in such things like Transitive (who provided Apple's Rosetta technology for PPC on x86). I don't think this would be a roadblock.
First, 2GHz dual/quad ARM Cortex A9s are required.
iPhone 3GS uses an ARM Cortex A8 at 600MHz.
It's the older iPhones that use ARM11 at 412MHz.
As the A5 is a lesser CPU than the A8, I expect the iPhone to never utilise it, but to migrate to the A9, and potentially dual-core A9, with the next release in July next year.
You would think that in certain territories they would come to an arrangement with a native provider.
Going with AT&T is strange. T-Mobile, Vodafone, Telefonica, Three all have large international networks and one of these would be a far more logical provider for Europe than AT&T.
Instead they're going to make the product worthless and expensive.
Maybe those 40 other companies licensed them as part of a broader licensing package, rather than specifically. Without someone doing an analysis of the patents involved, and how Apple have implemented the similar features (patents protect a specific way of doing something, not the something), we won't know.
It'll end up with Apple paying a nominal fee and cross-licensing their multitouch and other mobile patents, so Nokia won't have to worry about them in the future, and thus can remain a relevant company in the mobile marketplace.
It seems the momentum is with Android for "OEM handsets", the handsets that would previously have used Windows Mobile have migrated en-mass to a cheaper, more modern, sellable phone OS.
It just convinces me that Windows Mobile 6.5 is too little, too late, and it doesn't offer much anyway. Windows Mobile 7 - presumably their next-generation mobile OS - is horribly delayed and will be feature-poor (generation 1) in comparison to Android, WebOS and iPhone OS. Maemo is on the sidelines too, for Nokia.
There's about a thousand or so users I guess.
The past ten years have been gutting for the platform. Poor owners of the trademarks, poor hardware that was late, late delivery of the new OS (although bringing an OS from 1991 on to a new platform ten years later isn't easy), community splits (Genesi, MorphOS), and more killed it.
The hard work of the OS developers and a few small hardware companies have kept the platform trundling along. Now the OS developers own the OS rights, maybe things can be done to move forward. A port to ARM Smartbooks seems the most logical step (or creating PowerPC Smartbooks using embedded PowerPC cores), the competing platform are Android and Chrome OS, Windows Mobile, and netbook remixes of traditional Linux platforms.
The Amiga Inc company was running the brand into the ground via incompetence and very weird behaviour (asset switching between companies to avoid bankruptcies, etc). Hyperion have been trying to develop the market for a long time, so it is good that they have control now. I hope they port to ARM for upcoming Smartbooks.
It's well worth reading reviews c. 1985 - 1992 of the Amiga, to see how special it was back then. Hardware-wise, any modern PC in the last ten to fifteen years has been Amiga-like, with dedicated co-processors for graphics, audio, etc. OS-wise, AmigaOS is behind modern systems, but it had some niceties, I found the filesystem layout nice for example, nicer than Unix. In 1985 to 1995 it was simply far ahead technically. Lack of investment killed it though.
However my Amiga related shortcuts live in a bookmarks folder alongside my 8-bit computing links - the folder's called "Retro". I wish them all the best of luck, but I think they're five years too late. Actually, in 1998 I made a post here saying that AmigaOS would be perfect for a Palm-like device. Shame.
I have to agree. Many people, in general, are quirky, weird, different. Not just developers.
The reasons for this might be different. I believe a lot of us, due to social exclusion early in life (i.e., early weirdness causing disenfranchisement?) discovered the computer.
I've also seen amazingly sane normal people in the field (and other fields).
It's just a silly topic.
No. Redesign Coffee Sales Policy.
Namely to pre-mix DRIVE THROUGH sales with milk and sugar as per customer requirements. Therefore lid doesn't have to come off the cup, and spillages won't happen.
And it isn't 24 million drive through coffee sales. The majority of coffee sales will be in-store. Extending that to drive through sales without a risk analysis of giving people in a car scalding hot drinks that require complex manipulation (lid off flexible cup held between legs in car seat to add milk and sugar) with risk of spillage was foolish - as I said, you don't need to be Einstein to work out what would eventually happen.
They had previously paid out $500,000 for those accidents, and they hadn't done a single thing to assess how to reduce them.
Stop sucking up to big corporations and excusing them for their mistakes and lack of foresight.
So they sold 24 million cups of coffee to people in cars via the drive-through counter, as with this case? The accident wouldn't have happened if the milk and sugar was added beforehand, and all those posts here talk about how the milk and sugar addition reduces the temperature for consumption. Yet to add the milk/sugar, she had to remove the lid on the coffee, which caused the accident. It was bound to happen sooner or later. The case seems perfectly reasonable, there was no aspect of "getting rich" about it, unless you think having your genitals scalded off is an acceptable price to get for a few hundred thousand dollars.
They sold scalding coffee to customers via the drive-through kiosk. The customers then added their own milk and sugar afterwards, which required pulling off the lid - you know, those awkward lids you get on styrofoam cups of coffee.
You don't need to be Einstein to work out what would eventually happen.
Go on, do it.
All over your groin so you need two years of surgery, skin grafts on your penis, probably no sex ever again in your life.
All for a measly few hundred thousand dollars.
All because McDonalds thought that serving scalding hot coffee to people in cars (it was a drive-through) where they had to add the milk and sugar themselves (thus taking the lid off, which causes spills if you've ever done that with a coffee cup lid in such a place, it's difficult even on a steady table) was an acceptable practice.
Stop being a mouthpiece for McDonalds and accept that they were in the wrong, they were punished for it, they adjusted their working practices, and things are better now.
It's scalding hot so that the process of serving it means it is the right temperature when it is drunk. This includes factors like a MUG that absorbs some of the heat to get the coffee down to drinking temperature.
When it is still scalding hot at drinking time due to using insulating polystyrene cups amongst other factors such as McDonalds keeping the coffee too hot after brewing it, there's a problem.
I take you want your genitals scalded off by a minor accident caused by an everyday action?
In addition in normal coffee outsets people take the coffee and sit at a table. In a McDonalds there is a reasonable expectation that the coffee will be taken out, as it was in this case:
"ordered a 49 cup of coffee from the drive-through window of a local McDonald's restaurant. Liebeck was in the passenger's seat of her Ford Probe, and her grandson Chris parked the car so that Liebeck could add cream and sugar to her coffee. She placed the coffee cup between her knees and pulled the far side of the lid toward her to remove it"
How are McDonalds not at fault here? They served scalding coffee through the DRIVE-THROUGH, expecting the customer to take the lid off to add the milk and sugar. This is going to be done in the car seat. The lid is on too tightly, increasing risk of spills. Clearly McDonalds should have served the coffee with requested milk and sugar so this couldn't happen.
Did all these marketing emails from the stalkery creeps in the marketing agency include an opt-out statement, and other identifying statements that indicated that it was not real and who the source of the emails was?
I would be willing to bet that they weren't present.
As you say, consent should be revokable at any point, but if there is no mechanism to revoke, nor any method to identify the source in order to revoke by other means,
Never mind that "informed consent" surely means giving consent when informed of how the marketing campaign would actually work, i.e., that there would be stalkerish creepy emails.,
Sorry, the court case, which heard all the details, found her 20% to blame. So your opinion is just irrelevant and invalid. You can't just say ""Shares the blame". No, she IS to blame." as if you're some higher force of knowledge and wisdom.
McDonalds sold a product for consumption within a car that was horrendously unsafe for said scenario by being too hot for that scenario. The situation could have also been changed by having a cap that reduces spillages (and contains aromas as a side-benefit), and a sturdier container that didn't deform under mild pressure. There is an argument that they couldn't have anticipated this situation, but they had 700 accidents recorded over ten years, so ...