uponcoffee

I think the GP means that as far as incidents occurring, so far as care is (or was) taken to prevent them and learn from them, then that's all one can really reasonably ask for. The first incident falls under that heading and 'is fine' in a 'life happens' sense.

The following incident comes across as reckless and avoidable as there should have been procedures to safely test the rollback (and perhaps there were, but a perfect storm allowed it fail in prod). Lacking details about how the second incident came to be or how they will be prevented going forward places the second incident as 'not fine'.

This information is what the GP comment is asking for.

Compare this PM with Cloudflare's PM, where they detail how they tested rules, what safeguards were in place, how the incident came to be, and how they intend to prevent similar incidents; the impression given here is that they will put up more fire alarms and fire extinguishers but do little fire prevention.

From a similar high elevation perch: https://softwareengineering.stackexchange.com/questions/2746...

Tl;dr AoT can be more resource intensive as a one time cost while JIT uses and limits runtime resources

Google, w3c, mdn... to name a few

https://developer.mozilla.org/en-US/docs/Web/CSS/@keyframes

Lua. I never really got behind importing a package for everything, so the lack luster package management/community doesn't bother me. The syntax is fairly clean (its a nice break from braces and semi colons everywhere), it's easy to extend, and it's perf under LuaJIT is hard to argue with.

I use pihole + dnscrypt-proxy 2.*

A fair number of resolvers support DoH and dnscrypt-proxy also supports DoT. It's fairly feature rich, you can configure a hosts file and then some.

[0] https://github.com/jedisct1/dnscrypt-proxy

Can you detail how the views presented provided are 'slanted' and 'don't matter'?

Fair, ESNI will eventually fix that but it's still a ways off from a finalized standard, and further still from being adopted en masse.

Then there's the option to reverse lookup the dns record associated with a given ip.

So ad blocking/censorship will still be viable for a while yet.

The solution is to do as most goverments do [0]: sniff the SNI header during TLS handshakes and drop the connection if the domain matches your blocklist(s)//regex filters.

[0] https://signal.org/blog/looking-back-on-the-front/

Amazon should be held responsible, and they can recover damages by suing the third party. This protects the buyer in the case that the seller disappears or cannot afford the settlement.

IMO, amazon would be better off moderating their platform.

I'm in the same boat. On has many meanings, as written 'on Github' could mean:

- Github is the platform/medium/support facilitating work - Github is the target/aim/focus of the work

E.g. 'Working on a table' means I could be making a table or I am using a table to work on something.

From my understanding, this isn't saying there are 25k employees working directly for/on github. This is saying they have a lot of distinctly separate open source projects (e.g. VSCode) that teams work on that are hosted on Github.

A quick google suggests there's some odd ~900 employees of Github, which is the same order of magnitude as Gitlab.

Not that I necessarily disagree, but I think there's a bit of leap between ghack's footnote and assumptions about Google's behavior.

One could leap to the assumption that ghack's target demographic are more likely to embrace ad-blockers, which is why they're being hit hard.

I think log scale or some different minimum/increment (start from the min instead of zero) would make the chart more informative.

'England's got a new Queen' really skews the precieved scale as most everything else is sub 500k, with it pulling ~1500k

There's probably bit of hardware lot it with Intel chips. Since they control the hardware, Apple probably has invested quite a bit into hardware specific optimizations that won't readily port to AMD chipsets.

Also, AMD is only recently been a performance front runner - they might not hold on to that for long. In the short term it doesn't make sense to jump ship.

For for general computation/ecosystems or for generation/device specific ventures (e.g. Consoles) it makes sense to turn with the tides.

> At what point with the wish to deliver ads outweigh the want to measure user engagement?

It could be argued that self selection from advertisements makes ad campaigns more cost effect per impression/click. If a person wants to block ads they might be less influenced/willing to purposefully click on adverts.

The other end of the stick is that website owners cant be trusted to self report metrics which influence payout.

I think the <insert minority/foreign country here> will steal our jobs narrative doesn't really work here.

This will cut jobs, yes, but as a latency/redundancy sensitive application jobs servicing this will be geolocked to 'hubs' of some form. Like air traffic control, but for trucks.

I think the parent comment is asking if the patches have been applied to both chips in the benchmark. Yes, AMD perf will be largely the same but comparison between patched and unpatched will be different.

It's hard to talk about things without names. You could use the CVE but it's hard to remember one from the other and is about the same as using no names.

How does one plagiarize and attempt to profit off somebody else's work without knowing it?

It's ingenious to say you've apologized while at the same time saying you didn't knowingly do anything.

It'll like be pursued by other companies if it's beneficial, but currently this is theoretical, doesn't scale, and while they speak to power consumption there's no mention to computation speed (FLOPS).

Exciting yes, but like battery tech, there's a lot to address in that last mile to market.

This boils down to voting with your dollars, the root comment didn't like B&N's business practice and gave their business to someone else.

I don't see how that would work. If my site gets zero traffic, would I still get paid a flat rate to 'serve' ads? Pay per impression/click works to pay proportionally to individual site traffic and the extent of a campaign.

The current solution is effectively a flat rate as far as an ad campaign is concerned: impressions/$

I get what you're saying, and agree to a degree.

On the other hand this is like not backing up your hard drive. Having a single point of failure and expecting anything less is...

Like you said, he's big enough to shout into the abyss and get a response, while others have to accept that a single point of failure is exactly that.

If we changed the headline to hacker deletes '5 years worth of work', the response would be different; two-factor should have been enabled, should have used a strong password, one password per account, yubi-key, etc. The onus would have been on the developer.

There are plenty of free hosting services for repos, so there's no reason IMO to not maintain a mirror.

How would devices use the obscure DoH IPs, there would have to be a method to update/lookup said IPs. That same method could be used to keep an up to date block list.

Alternatively, the traffic could be subject to heuristics to identify DoH connections.

With the prevelence of ad blocking tech, the question becomes why haven't they already?

The answer being that content providers can't be trusted to self report metrics that determine how much advertises pay. At least not for pay per view/client/etc models.

The people that self select themselves from viewing advertisements might be doing advertisers a favor. They're perhaps less likely to make purchases based on impressions//click ads on purpose; per dollar, ad campaigns might be more effective without said people.

Assuming ample money, resources, and support, height isn't a big deal (for solid state rockets).

From my experience as a part of a collegiate (liquid) rocket club, just getting to manufacturing is a major hurdle.

There's legal red tape, university specific red tape, insurance/liability, material sourcing, funding, manufacturing, testing etc.

Note that some of these steps may require specialized facilities/equipment, transport, etc. Outsourcing (e.g. manufacturing) trades off for added red tape. ITAR is fun.

This makes working towards great heights a slow process, and if something goes wrong during testing/launch it's a major set back.

>3 bytes for prices up to 167772.16. If you frequently buy things more expensive than that, just have one of your servants transcribe the recipe to your favorite format.

>1 byte for the number of items. If you buy more than 255 of one thing, we'll just add another line to the recipe.

You could split prices greater than 167772.16 into chunks, delimited by using zero for the number of items in the subseqent line items.

Have you tried using pengwin[[1]](https://github.com/WhitewaterFoundry/Pengwin)? I got the docker client working for windows in just a few keystrokes last night.

[1] [https://github.com/WhitewaterFoundry/Pengwinhttps://](github...

Why would giving up Adobe programs/games be a reason to switch before?

I don't think the reasons have changed much at all, just the execution. The above is an example of why one might dual boot, or run one OS in a VM, it's also a reason for chrome books/windows to ship a Linux kernel.

Fair point, that was a poor example/counter example on my part.

What I had in mind was more a long the lines that windows/Mac OS isn't transparent and the consumer has limited control over what it's doing and how to implement things. Furthermore their official app stores are a walled garden of sorts.

Consumers/developers have a good deal of freedom on these platforms and with that comes breakage in various forms. Malware, instability, etc. And to deal with that you have repair shops/programs. System resets, fresh installs etc. Maintenance becomes a responsiblity of the consumer.

Like I said, the lines can move based on context. Moving the needle further towards freedom for developers/consumers gets you *nix systems - which is harder for your average consumer to maintain/use. Moving away gets you iphones/consoles, etc which "just work" and flaws in software/hardware handled by the manufacturer.