mcronce

It depends exactly how simple that CRUD API is. If there's any business logic, I'd rather get all the cheap correctness guarantees that Rust provides. I don't find myself making many truly dumb CRUD APIs.

Time to iterate is also only much faster in certain situations, e.g. local development; if you have to e.g. build a container image, push to a registry, and redeploy to a k8s cluster somewhere, those savings become somewhere between less significant and nonexistent.

Conduit as well, although AFAIK it's not an "official" homeserver, while Dendrite is

This sounds... Legitimately like a perfect match for a use case I have. Thanks for the write up.

I was on the Northeast Regional last September and can confirm, halfway decent beer selection. They had wine as well, not sure what the selection was like, and not sure about spirits.

It does contain many, many memes, which - along with emojis - are the hieroglyphs of our time. There are certainly worse legacies I could leave.

See also: Insurance, healthcare, and car dealerships, all "free market" institutions that people consistently have great experiences with

/s, in case it's non-obvious

You mean in 500 years, nobody's going to dig up the server rack in my house and figure out how to rig the Ceph cluster back up?

This doesn't answer your question, but I really wish someone would offer off-the-shelf panels with tubing on the back to hook up water lines. It would be dope to cool my panels and preheat my hot water at the same time.

Yes and no - deploying a Node project, I need to install all its dependencies. Deploying a Rust project, I still typically only need to pull down the binary. The general attitude is still to pull in dependencies to do a job instead of inventing your own solution, which I consider a good thing, but not everybody agrees.

To get from minutes of time to minutes of human time, you have to multiply the 5 minutes by the number of passengers on the flight

I don't have an opinion one way or the other on the "optimization", just pointing out the missing step in the math

> You can always mutate things in a local context (i.e. objects that are either owned or uniquely borrowed)

You do have to explicitly declare them mutable, though, and will warn you if you have a mutable variable that you never mutate. This is helpful for avoiding surprises.

You can if you want, but it sounds a lot more like FUD than anything else.

It's not a promise, it's an observation

I agree with this. I may not be able to have a non-working prototype that crashes on its first input as quickly with Rust as with Python, but I can create a working prototype more quickly, and that prototype will transform into production code far more quickly.

Scale up a bit, and you end up with far fewer (often zero) subtle bugs when other people change other parts of the codebase, or when you do a significant refactor - some of these being the kinds of bugs that are difficult to test for.

I would call that "more productive", personally.

Definitely not trivial, but staged builds are my go-to solution. Depending on the specifics of the tech you're including it can be a lot easier than figuring out how to clean up every little build artifact within a layer - just add a second FROM line and copy precisely the pieces you need in the final image, and nothing else.

I also think it makes the build stage a lot easier to follow for people who aren't as familiar with Dockerfiles and all the quirks that come with optimizing a final image.

This ban doesn't punish the machine; it doesn't care whether or not it's banned from Twitch. It does two things:

* Makes sure the people controlling the machine are incentivized to correct it (not that I think they needed it, but what I think is irrelevant)

* Ensures that content that Twitch management doesn't want on their platform, and which is in violation of their TOS, is removed immediately, regardless of the thoughts/actions of the people controlling the machine.

It's also super easy to enforce at the crate level with #![forbid(unsafe_code)] if you feel so inclined - no manual checks necessary

The circle of life

Tokio has a single-threaded executor as well

> the reality is that the the whole process is just as deterministic and conscious-free as water flowing downhill

This isn't just an analogy, either...if the material happens to be water, it's _literally_ flowing downhill if it's falling into a black hole.

I think that's why the "bare minimum" language was used: It's a lot better than the status quo, but doesn't go far enough.

Yes, it does. Just because one of them matches your personal anecdote doesn't waive the requirement for actual evidence.

I'm glad to hear you had a good school life. Most people aren't that lucky.

Exactly the same amount of backing up as "school != stress for most" does.

The real lifeprotip is always in the comments

Yup. Two kids fit in the back seat of a sedan perfectly fine.

96 cores and 6TB per socket with Genoa!

A good start, at least with Google, might be for them to give anything resembling a fuck about their non-advertising customers.

My experience is that they seem to have this mindset that if you aren't paying them for advertising specifically, you're not a customer, you're a user - the product - which is true if you aren't paying them at all, but isn't even remotely the case when you're giving them money in exchange for a product. Absolutely horrendous customer service every time I've needed to contact them.

They also like to yell and scream about how "science can't make up its mind"

Yes, because that's how science works. When new information is acquired, new hypotheses are created and tested.

30% isn't a majority.