__float

This should be such an infrequent occurrence that the cost should be negligible. Surely their $10/month plan has enough margin that this can be covered?

Is it not...a bit of both? There's some dollar amount where "what you can do with it" wouldn't make up for the price, no?

Not everything needs 10k RPS, and in some sense there are benefits to a new process – how many security incidents have been caused by accidental cross-request state sharing?

And in a similar vein, Postgres (which is generally well liked!) uses a new backend process per connection. (Of course this has limitations, and sometimes necessitates pgbouncer, but not always.)

It sounds like this may have been one of the pieces of software the author intentionally chose not to use:

> There are some clunky old Windows programs, niche scientific tools, and image analysis software that assumes you’re trying to count cells under a microscope...

Those downsides don't seem that bad to me. If something needed repair, they can bring a contractor on site, and certainly the Fed has cameras and police to monitor.

(In line with some other commenters, I'm more inclined to believe it's bills they've taken out of circulation than "almost finished" ones -- security features are built in throughout the process, not just an extra step at the end.)

It's a tech/quant role.

I like the exit code feature a lot; Starship does that with my config in a subtle color change.

My shell customization is largely throwing Starship in (so it looks the same on all the machines I use -- Ubuntu servers at work, macOS at home, nixOS/Fedora/etc. servers for personal use.) and a starship.toml I wrote once and now leave alone.

What in microtype makes "a big difference"? I don't recall using it (my LaTeX years are long behind me), but all of the examples on https://www.khirevich.com/latex/microtype/ seem incredibly minor. I don't think I'd notice any of them as the reader.

With all of the basic mistakes in the content of this report, how is removal of the word "big" worthy of description as a fuckup?

Do many people use macFUSE? I thought ever since the license change it's really dropped off.

I think they're probably more concerned about fake accounts and people finding ways to get free stuff.

> Hopefully Matz sticks to his guns and never allows type annotations at the language and VM level.

Why? Just because they _exist_ doesn't mean you'd need to use them.

Checklists work well in high stress situations where you cannot forget a step (medicine, aviation).

A checklist in a security incident? Probably helpful.

A security checklist to satisfy auditors and ancient regulations? This is an entirely different kind.

It may violate the SQL Server license? Microsoft have not apparently paid for a Jepsen analysis (or perhaps don't want it public :))

Neat idea, but uh, you're giving users a text box straight to a costly API.

Why is that unexpected?

That isn't the point. In practice, if you provide randomness, it will be depended upon.

The live demos were neat! I was playing around with "The Pete System Prompt", and one of the times, it signed the email literally "Thanks, [Your Name]" (even though Pete was still right there in the prompt).

Just a reminder that these things still need significant oversight or very targeted applications, I suppose.

YRIS: you'll read it someday

My experience has not been so smooth. Migrations are reasonable, but they're not free and "always keeps backups" sounds like you'd tolerate downtime more than I would.

Even in the best case (e.g. basic column addition), the migration itself can be "noisy neighbors" for other queries. It can cause pressure on downstream systems consuming CDC (and maybe some of those run queries too, and now your load is even higher).

Performance is not necessarily worth maxing at all costs.

Is that project even maintained still? GitHub looks...quiet.

While none of that is false, I think there's a big difference from shipping your data to an external LLM API and using AWS.

Using AWS is basically a "physical server they have control of".

He has surely dedicated a significant portion of his life to his own pet theories on obesity, but to consider him a well-regarded expert is very misleading.

He has quite a few claims that are just...ridiculous, and his pop science books have some serious flaws (as reported by actual experts).

What's wrong with Markmonitor? They don't have nearly the customer base of Zoom (where I can relate to any complaints, I'm sure)

No, it's objectively more difficult to type [on a qwerty keyboard].

cmd-s is a single keypress and can be done with a single hand.

shift-; w cr is two more and involves a back and forth over the entire keyboard.

Modern GUI apps tend not to design for the keyboard-wielding power user.

TUIs can have just as many quirks and bugs, but on the whole they tend to be a little simpler, and the author usually is an end-user :-)

This might be true for the most part as an end user, but from a licensing perspective regarding the original binaries, this is irrelevant.

You must be able to modify and change the code, not merely append to the PATH:

> Tivoization: Some companies have created various different kinds of devices that run GPLed software, and then rigged the hardware so that they can change the software that's running, but you cannot.

from https://www.gnu.org/licenses/quick-guide-gplv3.en.html

While the GUI is somewhat helpful, at the end of the day it's not the key piece, and it could easily be rebuilt.

This was discussed somewhat recently in https://news.ycombinator.com/item?id=42855258

The lifetime warranty clearly was valuable to many people here.

The problem though, is the _misleading_ marketing around "better sound" and similar that is false and does not justify charging more to basic home consumers who don't know any better.

I can't really fault them too much for hopping on the latest bandwagon, if their software is general enough at running workflows for it to fit.

They do seem to have a nice "quickstart for CI" they haven't abandoned, yet: https://docs.dagger.io/ci/quickstart

(As much as I personally like working with CI and build systems, it's true there's not a ton of money in it!)