I mean that's still basically what they tried to do at the time. They were trying to get them through web standards committees and everything.
IIRC a big reason it didn't end up working was because NaCl was such a "big" technology and asm.js such a "small" one that asm.js was able to reach production-ready first despite starting work several years later.
The cute thing about asm.js is that it was fully backwards compatible with the web: it was just a lot slower without dedicated support. So Epic or whomever could put out a demo that would run just fine in Chrome, but the performance was a lot worse than Firefox which had a dedicated compilation pipeline, so it made Chrome look bad.
The way I remember it, NaCl and PNaCl ended up nowhere not because big, but because Mozilla, then with big influence on standards, declared them not web enough for the crime of not being JavaScript and pushed against any addition of it into Gecko in any form and promoted "JavaScript is all you need" including an early demo of decoding video in JS - which I recall disgusted me because I somehow knew it would take away various technical issues preventing proprietary encoding from closing down web videos.
Funnily enough, NaCl had its origins in Mozilla extension, with old versions IIRC mentioning lineage starting in Google Gears extension for Firefox
Bullshit work has hit escape velocity, won’t be long now before we have huge warehouses filled with people doing sudoku for their daily food allowance, and that’s just how our entire economy functions.
How are we sliding face first into “snowpiercer but dumber”?
don't worry they're not building many of them anyways, they're just accumulating debt and padding the pockets of all the construction companies that are sitting around idle
The difference is that early-bird pricing is transparent and predictable. There is a written, known policy of $X discount during specific hours. You can plan for it. It's never a surprise.
Dynamic pricing means sometimes you go there, and Wendy's decides on the fly whether you get a lower price and how much. It gives Wendy's the option to pinch pennies how they see fit for their own benefit, rather than offering a deal which you can choose to accept.
I can't tell if you're implying that Wendy's was going to offer different prices to different customers "on the fly", but that wasn't the case.
It was store-wide with updated prices shown clearly. Yes it could change on a daily basis, but you would also expect it to be roughly predictable because the whole point is to get more people to come in when it's cheaper.
Saying that Wendy's is "pinching pennies" doesn't make any sense.
So... you just apparate at Wendy's instantly without cost when you decide to go? Most of us aren't so lucky. We need to travel there, which takes time and resources. Sometimes we decide to go through the drive-through and there are 5 cars in front of us and soon 3 more behind us blocking us in. When prices are 20% higher than you expected when you finally get to order, do you leave and waste all that time? Do you pay 20% extra, giving them money for nothing? Economically, both of those options are losses.
(Yes, I understand that Wendy's claimed it was only ever going to be used for discounts. But frankly, I don't believe them. The temptation to increase prices is just too powerful to ignore for a profit-maximizing MBA.)
I mean, I go to a place like McDonald's probably once a week when I'm starving and it's convenient. Their prices change all the time. The item that had a big promotion last week no longer has one this week. On the other hand, there is a new item on the menu that has a big promotion this week. And because I went to a different McDonald's today than I did last week, the prices are all different anyways, often by as much as two dollars.
You seem to be assuming that fast food prices are already known and predictable when they're not. What you usually do is decide you're in the mood for Wendy's, go there, look at the different prices and different promotions and decide what will most satisfy you while being the cheapest. Maybe you were in the mood for a bacon cheeseburger but they have a promotion where double cheeseburgers are 40% off so you get that instead.
Why you are bringing in travel time doesn't really make a lot of sense to me. And the whole point of dynamic pricing is that they want it to be somewhat predictable, so you know that if you show up at 3:30 p.m. you're going to save a couple of bucks compared to if you show up at 12:15 p.m. Like, it's not rocket science to figure out at what times a restaurant is going to be less busy.
You've never had to budget tightly, then? When I was in college, I knew what my typical order at every restaurant near campus would cost me, to the cent. It was a big deal in how I planned my days. Something costing $1 more could blow my budget for the month - and did, a few times. I can't imagine how miserable it would have been trying to balance all the various factors if prices were basically randomized.
I know a fair number of people who still have to plan to that degree. It's not a foreign idea for them. It's their daily life.
I have some background in data privacy compliance.
It sounds like they are claiming to be a Service Provider under CCPA, which is similar to a Processor under GDPR. Long story short, a Controller is the one legally responsible for ensuring the rights of the data subject, and a service provider/processor is a "dumb pipe" for a Controller that does what they're told. So IF they are actually a Service Provider, they're correct that the legal responsibility for CCPA belongs to their customers and not them.
That's a big IF, though.
Being a Processor/Service Providor means trade-offs. The data you collect isn't yours, you're not allowed to benefit from it. If Flock aggregates data from one customer and sells that aggregate to a different customer, they're no longer just a service provider. They're using data for their own purposes, and cannot claim to be "just" a service provider.
ALL existing product simply let you set up alerting system, and that alerting system is manually done by you. still un-expected issue can arise. LogClaw is not altering system. you just send all your logs, its capable of injecting terabytes of logs per day, and it automatically ignores all the successful logs, and it works on the uncaught exceptions, errors from all services, infrastructure itself.
That type of experimental set-up is forbidden due to ethical concerns. It goes against medical ethics to give patients treatment that you think might be worse.
The Gaussian integers usually aren't considered interesting enough to have disagreements about. They're in a weird spot because the integer restriction is almost contradictory with considering complex numbers: complex numbers are usually considered as how to express solutions to more types of polynomials, which is the opposite direction of excluding fractions from consideration. They're things that can solve (a restricted subset of) square-roots but not division.
This is really a disagreement about how to construct the complex numbers from more-fundamental objects. And the question is whether those constructions are equivalent. The author argues that two of those constructions are equivalent to each other, but others are not. A big crux of the issue, which is approachable to non-mathematicians, is whether it i and -i are fundamentally different, because arithmetically you can swap i with -i in all your equations and get the same result.
I don't think anyone thinks is "i and -i are fundamentally different". What they care more about is whether the 5 5th roots of 2 have an natural ordering or not.
They weren't "just" raw dumps of internal C structures. It takes careful design work to dump raw memory in a usable fashion. Consider: You can't just write a pointer to disk and then read it back next week.
Binary MS Office format is a phenomenal piece of engineering to achieve a goal that's no longer relevant: fast save/load on late-80's hard drives. Other programs took minutes to save a spreadsheet, Excel took seconds. It did this by making sure it's in-memory data structures for a document could be dumped straight to disk without transformation.
But yes, this approach carries a shitton of baggage. And that achievement is no longer relevant in a world where consumer hardware can parse XML documents on the fly.
I have heard it argued, though, that the "baggage" isn't the file format. It's actually the full historical featureset of Excel. Being backwards-compatible means being able to faithfully represent the features of old Excel, and the essential complexity of that far outweighs the incidental complexity of how those features were encoded.
HIPAA is not a privacy law, nor even a healthcare law. It's an insurance law. It does not cover medical records generally. It deals strictly with how doctors bill insurance companies, and mandates security for health information being billed about.
For the same reason, health & wellness apps are not generally covered by HIPAA, and in fact quite a few of those exist solely for the purpose of selling medical data to data brokers. Especially ones related to women's health.
IIRC a big reason it didn't end up working was because NaCl was such a "big" technology and asm.js such a "small" one that asm.js was able to reach production-ready first despite starting work several years later.