You save the server bandwidth bills and have all the people currently downloading help you get it instead of competing with you. Also, most torrent clients are way more competent and featurefull for handling downloads than most browsers.

Usually, it doesn’t make a lot of difference.

Temperature, speed, flow rate, cooling.

In other words, close to anything. Follow a calibration guide. Also keep in mind that some filaments just don’t make good overhangs.

It’s supposed to be stocks trading, not an AWS bill.

Oh, heavyweight Wasm is one of those things better written in Rust.

Intrinsically, one would expect there to be better options. But Wasm is difficult enough that people have been unable to port most tools. That will probably change at some point, but I would not stop anything to wait for that.

All the other options are worse.

But, hummm… Some people do use Rust for software where other languages are a better fit. But usually not in public. You see a lot of libraries helping people to use Rust in GUIs or web applications, but all the Rust rewrites people talk about are for stuff better done in Rust.

Think of it like Haskell’s cast from the Typeable class.

Yes, if somebody sends random stuff, you’ll have to handle a failure, or do the equivalent of returning undefined, what is way easier than properly handling it in TS. What you do from there is up to you.

Not really. The things where C++ used to shine are usually best done in higher level languages.

Rust is a great C replacement.

Well, the author is to blame for the choice of language.

That is, unless somebody forced their hand. What happens a lot in professional settings. Then it’s that other person to blame.

There are only 10 types of people:

the ones that expected a binary joke, and

the ones that expected a ternary joke, and

the ones that expected a quartenary joke, and

…

Nor care to have those reasons in the first place.

And if you press them, you get complete bullshit reasons. But SO will also ban you, while ChatGPT only cares about you paying.

Glass is guaranteed to be flat. The thicker the flatter, and mirrors tend to be thin.

It’s kind of normal. Printing on a glass is normal, some people pick a mirror because it conducts heat slightly better.

have to check and destructure the result of every function call

Learn how to use enum error types, how error bubbling works, and how to convert between Options and Results.

It’s Rust you are talking about, not Go.

Following the modern C conventions, the text following the series of (gnu) doesn’t matter and you can write anything you want there.

Microservices:

Several instances of the top panel each doing one of the steps on the bottom panel.

Oh, man, the people that design most REST APIs got loose!

Hum… The US is imploding in general, but there’s nothing on the horizon that could collapse the IT job market.

Yeah, doesn’t look like APL to me, but I don’t know it well enough to tell for certain.

Either way, that much code in a language that is at least as concise as APL… what is this? a full office suite?

• You should really not need to do a PR across multiple repos. If you need, you are breaking your code wrong. Some functionality may require multiple PRs, but you should always be able to do those at different moments and test them separately.

• The monorepo tools are exactly software that emulate the features of a multi-repo so that you can have thousands of people on the same repository. We also have multi-repo tools that emulate the features of a monorepo, but people don’t hype those online because they are simple and free.

Yeah, let’s pretend the vibe-coder creates praiseworthy code when everything is working…