The only reason these people have jobs is because it's just barely cheaper to hire humans than to replace them with robots. Crank up minimum wage to $15 and they won't have a job at all.
The main difference is that the warranty is usually offered by the manufacturer, whereas the Sale of Goods Act governs interaction between people who buy and sell things.
I understand legally what the difference is, I don't understand how it's different for the consumer.
Seagate used to sell the best spinning disk hard drives until their quality took a nose dive, then it was Western Digital. Samsung was OK, hardly the best.
The Sale of Goods Act in the UK (and equivalents in most EU countries) allow you to return the goods for a full refund if they do not meet the promises made at time of sale.
So what's the difference between a 1 year replacement warranty and a promise that a product will last for a year under a Sale of Goods Act?
Sure, I've had the odd lemon WD drive, but every Seagate drive I've owned failed before or not log after it's warranty was up.
I confirmed this with an acquaintance who runs an enormous disk array for a university. They switched exclusively to WD Reds after atrocious failure rates with Seagate drives, and a pilot where they tested Samsung drives.
I interpret their relative slowness to market as doing proper testing before releasing product.
I had an array of 4 western digital 4TB drives. Added 2 Seagate 6TB drives, as they were the only company that produced them at the time. One failed after six months - replaced that one, the second died after another 4 or 5 months. I quickly bought two 6TB WD drives and mirrored the data before both Seagate drives failed again. The old 4TB WD drives are still running fine, as are the new 6TB drives, two years later.
It's extremely predictive. Given a limited set of variables, basic economic theory works pretty well - hedge funds bartering for futures or Maori tribes bartering for food.
There are, of course, a lot of exceptions. Those exceptions are the study of economics.
and pre-load the database (most common way of getting data into the database initially) then hit it with an OLTP workload, ZFS will perform *terribly* - because it got large streaming writes up front, allocated huge stripe sizes, which makes rewrite performance go to hell in a handbasket,
L2ARC is supposed to fix this. I've heard good things about it.
Commits that break builds. Commits that don't work. Commits that are buggy. Commits that are poorly formatted. Commits that aren't logically structured. Commits that don't follow project conventions.
My favorite nutjobs are those that are scared of HFCS. It's glucose bound to fructose. Your body processes it into... glucose and fructose.
You get into trouble when you take in too much of it, in the *exact* same way you'd get into trouble if you sat there and ate handfuls of cane sugar every day.
Just eat less of the stuff. A coke every now and then won't kill you.
To be fair, windows seems to have pretty good penetration into the embedded market already. Heck, I see random boxes with screens frozen on the windows desktop all the time.
My favorite experience is waiting at airport security a couple of years ago - there were screens denoting which lanes were open and which were closed. Apparently each screen was an individual windows box, and every single one would randomly crash and reboot every minute or two. Made for a nice light show while waiting mindlessly in line.
And you think it's hard to do better than the real guys, but they screw it up too, and they don't try particularly hard.
Remember, companies were throwing together working ECMs back in the eighties out of discrete components and one dinky microcontroller. Hitachi used a 3 MHz 6800-series chip in the computers that ran the Impreza, 240SX and some of its other contemporaries.
They do screw up sometimes, that's why there are years of testing done.
It's not the parts, or even necessarily the code. It's the process and experience. You need something that works reliably with precision AND accuracy for the life of the engine (ideally more than ten years) under every possible condition.
For several years the anti-fructose movement has been making noise and has been showing increasing insight is the underlying mechanisms. Famous example spokesperson of this movement is Dr Lustig, and googling his name alone gives a boatload of references.
An MD claiming a single chemical is mostly responsible for obesity? BS detector starts ticking up...
The only reason these people have jobs is because it's just barely cheaper to hire humans than to replace them with robots. Crank up minimum wage to $15 and they won't have a job at all.
To get any reforms through you'll need approval of the unions. The unions will say no. You aren't anti-union, are you?
Cripes, OpenBSD is a HUGE fork of nearly everything from FreeBSD. Runs pretty damn well.
The main difference is that the warranty is usually offered by the manufacturer, whereas the Sale of Goods Act governs interaction between people who buy and sell things.
I understand legally what the difference is, I don't understand how it's different for the consumer.
Seagate used to sell the best spinning disk hard drives until their quality took a nose dive, then it was Western Digital. Samsung was OK, hardly the best.
The Sale of Goods Act in the UK (and equivalents in most EU countries) allow you to return the goods for a full refund if they do not meet the promises made at time of sale.
So what's the difference between a 1 year replacement warranty and a promise that a product will last for a year under a Sale of Goods Act?
Sure, I've had the odd lemon WD drive, but every Seagate drive I've owned failed before or not log after it's warranty was up.
I confirmed this with an acquaintance who runs an enormous disk array for a university. They switched exclusively to WD Reds after atrocious failure rates with Seagate drives, and a pilot where they tested Samsung drives.
Then again, a high enough failure rate will eradicate the profit margin on your product, especially on low-margin commodity items.
I interpret their relative slowness to market as doing proper testing before releasing product.
I had an array of 4 western digital 4TB drives. Added 2 Seagate 6TB drives, as they were the only company that produced them at the time. One failed after six months - replaced that one, the second died after another 4 or 5 months. I quickly bought two 6TB WD drives and mirrored the data before both Seagate drives failed again. The old 4TB WD drives are still running fine, as are the new 6TB drives, two years later.
It got 80's nostalgia correct, if not the weird themed diner.
How am I going to play at NetBabyWorld without shockwave?
Looks bad, but why would anyone have their web-admin interface opened up to the internet?
It's extremely predictive. Given a limited set of variables, basic economic theory works pretty well - hedge funds bartering for futures or Maori tribes bartering for food.
There are, of course, a lot of exceptions. Those exceptions are the study of economics.
and pre-load the database (most common way of getting data into the database initially) then hit it with an OLTP workload, ZFS will perform *terribly* - because it got large streaming writes up front, allocated huge stripe sizes, which makes rewrite performance go to hell in a handbasket,
L2ARC is supposed to fix this. I've heard good things about it.
Commits that break builds.
Commits that don't work.
Commits that are buggy.
Commits that are poorly formatted.
Commits that aren't logically structured.
Commits that don't follow project conventions.
My favorite nutjobs are those that are scared of HFCS. It's glucose bound to fructose. Your body processes it into... glucose and fructose.
You get into trouble when you take in too much of it, in the *exact* same way you'd get into trouble if you sat there and ate handfuls of cane sugar every day.
Just eat less of the stuff. A coke every now and then won't kill you.
The NSA and the rest of the police agencies are there to protect US CORPORATISM.
There, fixed that for you. Having government "protect" capitalism is kind of a contradiction in terms.
To be fair, windows seems to have pretty good penetration into the embedded market already. Heck, I see random boxes with screens frozen on the windows desktop all the time.
My favorite experience is waiting at airport security a couple of years ago - there were screens denoting which lanes were open and which were closed. Apparently each screen was an individual windows box, and every single one would randomly crash and reboot every minute or two. Made for a nice light show while waiting mindlessly in line.
And you think it's hard to do better than the real guys, but they screw it up too, and they don't try particularly hard.
Remember, companies were throwing together working ECMs back in the eighties out of discrete components and one dinky microcontroller. Hitachi used a 3 MHz 6800-series chip in the computers that ran the Impreza, 240SX and some of its other contemporaries.
They do screw up sometimes, that's why there are years of testing done.
It's not the parts, or even necessarily the code. It's the process and experience. You need something that works reliably with precision AND accuracy for the life of the engine (ideally more than ten years) under every possible condition.
It takes multiple years to type-approve an ECM for a single application. That's on top of the years-to-decades of development on the engine itself.
But if you think you can hack together one with a consumer grade ARM, go right ahead.
You aren't a programmer and you don't know what you're talking about.
No,
wrong way around.
His idea:
Fructose is causing metabolic syndrome and partly responsible for weight gain by sabotaging leptin response.
Right - that's his idea. Hasn't been proven by any studies, though.
There was one study that showed some correlation but, IIRC, it was poorly done and not replicable.
For several years the anti-fructose movement has been making noise and has been showing increasing insight is the underlying mechanisms. Famous example spokesperson of this movement is Dr Lustig, and googling his name alone gives a boatload of references.
An MD claiming a single chemical is mostly responsible for obesity? BS detector starts ticking up...
https://www.sciencebasedmedici...
http://blogs.scientificamerica...
BS readings confirmed.
Oldest trick in the book.
1. Cut library funding out of the general budget
2. Close the libraries saying that they are out of money
3. Run a special millage for the libraries
So your 'library millage' is actually a general fund millage that's been shifted around.
It works for a while - it's been done so many times in the city I live in now that the libraries are completely funded by millage.
Even if he simply transplanted a clock into a pencil case, he shows more knowledge of electronics than the vast majority of adults.
Geek cred: I was reading Getting Started in Electronics by Forrest Mimms in 5th grade, and wiring stuff to the user port of my C64 in middle school.