ecnahc515

Reading the comment reminds me of how I feel about the AWS APIs.

Correct, but for AWS, you can use SSO and delegate the MFA to your SSO provider.

> At FAANG scale, "one in a million" happens a lot more often than you'd think.

And it happens less than you think too, sometimes, which I think is closer to the original point.

Classic computers weren’t so different 30-40 years ago.

So disable it when you turn off the device?

Windows + WSL2 is starting to catching up with Chrome OS + crostini. How exciting.

On point 1), sometimes an approach to this is helping others. That might mean answering stackoverflow questions, or helping someone on IRC or Slack.

Mentoring/helping others helps solidify your own understanding.

I hadn’t considered how this being in the upstream kernel would make it possible to run my WSL2 on NTFS natively. That’s pretty cool. I’m sure there’s still some stuff to figure out, but still pretty awesome.

podman has a `machine` subcommand for setting up a VM for running podman. It configures the podman server and your podman client connects to the server, very much like docker.

https://docs.podman.io/en/latest/markdown/podman-machine.1.h...

For what it’s worth, podman has a `podman generate systemd` command for generating systemd units for running containers using podman.

Not everyone at Apple is a high compensated IC. A lot of them are retail workers.

Not anymore. Twitter is rolling out changes that require an account to view tweets.

For rustc with llvm maybe, but there's projects to build a GCC backend for rustc, as well as projects to build a Rust frontend for GCC, both of which could solve this.

Diversity and inclusion. So probably something about % of under-represented groups vs the majority (usually white males in the US tech sector).

It's possible to ship a product that doesn't break though.

You can add new APIs, etc, instead of breaking existing ones. Anytime you do a major rev because your changing an API or removing one, you could also ship new APIs instead and keep the major version the same.

This sounds a lot like how Prometheus works.

I want them to add touchID to the magic trackpad. I use the magic trackpad with my mechanical keyboard and it's great, except for the point you made.

Uh, plenty of people accept this argument, it’s part of the idea of the movement behind legalizing all/most drugs.

Look at marijuana, the drug dealer is now a business, and very few people are mad at dispensaries for selling pot.

In the end, if it wasn’t them, it would be someone else. If governments weren’t buying spyware from NSO, they would be making it themselves or finding another group who builds exploits.

Compiled executables are pretty simple to deploy without containers. The benefit of containers is that it can help standardize that type of benefit to other runtimes like Python/Ruby where it's much more challenging to just ship an artifact.

In addition to that, with cgroups and namespaces you get a lot of other benefits, which can be used with eg: systemd/etc but it's nice when one tool handles all of it.

The risk here is a lot lower, it’s not really gambling. In this situation, you’re in the same position as everyone else in the country. It’s that fact that means you can more easily slip by without being caught. Not only that but it’s arguable that even people still working were financially impacted by the pandemic, and they could reduce or stop paying rent. A lot of people had pay cuts, or lived with roommates, it’s not hard to justify it. You might not think your stretching the truth or you may think if your the only roommate paying rent that it doesn’t matter at that point.

Back to your example of shoplifting: If it’s a riot and looting is happening, then even people who normally wouldn’t steal or commit often join in. It’s mob mentality. “If everyone is doing it, why can’t I?”

There are plenty of people who probably made enough to continue paying rent, but chose not to because of the eviction moratorium.

A tech worker could basically stop paying rent, stating they've been effected by COVID, even if they weren't, or if it was short-term, and then basically collect their tech salary check's while not paying rent.

They _could_ pay, chose not to, and reaped the benefits.

They still can, this is only about individual stocks. Under this, members of Congress could still hold index funds, just not individual stocks.

A lot of this is just spending more money and resources to make it possible to optimize for speed.

With sufficient caching with and a lot of parallelism makes this possible. That costs money though. Caching means storing data twice. Parallelism means more servers (since you'll probably be aiming to saturate the network bandwidth for each host).

Pre-aggregating data is another part of the strategy, as that avoids using CPU cycles in the fast-path, but it means storing even more copies of the data!

My personal anecdotal experience with this is with SQL on object storage. Query engines that use object storage can still perform well with the above techniques, even though querying large amounts of data from object is slow. You can bypass the slowness of object storage if you pre-cache the data somewhere else that's closer/faster for recent data. You can have materialized views/tables for rollups of data over longer periods of time, which reduces the data needed to be fetched and cached. It also requires less CPU due to working with a smaller amount of pre-calculated data.

Apply this to every layer, every system, etc, and you can get good performance even with tons of data. It's why doing machine-learning in real- is way harder than pre-computing models. Streaming platforms make this all much easier as you can constantly be pre-computing as much as you can, and pre-filling caches, etc.

Of course, having engineers work on 1% performance improvements in the OS kernel, or memory allocators, etc will add up and help a lot too.

> You won't know which tokens should be considered expired in-advance, you still have to call the DB for every request to check

You can verify the signature before calling the DB.

You don't need to rewrite history unless you weren't using LFS or accidently committed large files to the repository. Nothing about LFS "requires" rewriting history.

Not to mention, many users are paying for a service that provides LFS, and hosting an LFS service isn't crazy hard. It's a file server with a custom API, it's mostly doable using S3 as a backend. It's not like this is crazy complicated stuff.

JWTs expire, so you only need to maintain a list of invalidated JWTs that haven't expired yet. You get two short cuts, one that you only check for revoked tokens which aren't expired and have valid signatures. This can save a lot of DB queries given you usually have to check auth validity per request.

The repository states in it's readme:

> This project will compile verilog (a hardware description language) into factorio blueprints.

This exists, specifically for the industry (food service) OP is talking about: https://www.pared.com/.

Ah dang I knew I should have looked up your role!

This reminds me of a blog post by Steve Klabnik (on the community team of Rust currently) about how he went through the Ruby on Rails backlog once similarly. It's a good read: https://steveklabnik.com/writing/how-to-be-an-open-source-ga...