Documentation should be generated from code imo

I agree, this is an anti-pattern for me.

Having explicit throw keywords is much more readable compared to hiding flow-control into helper functions.

Positive and negative what?

Yeah, idk, ive never actually used win 11 and have barely used win 10. It just a meme.

That’s right. Let’s return to basics, to the first programming language we learn as developers: Pascal. Well at least I have, I assume everyone does too.

/s

That’s a valid argument, but a very weak one. If we are not completely sure something is an improvement in all aspects are we just to dismiss it altogether?

Maybe search for this on kaggle? Or scrape Wikipedia?

This is the major reason for me. I really liked yaml, because it is way more readable to me than JSON. But then I kept finding new and more confusing yaml features and have realized how over-engineered it is.

Yaml would be great language if it had its features prunned heavy.

They’ve lost potential revenue, but that is not the same as if amazon would come to their house and had stolen their only rucksack prototype.

Potential revenue is not your property.

It still sucks though.

It works great for a closed group of people, all on one instance. Another data point that federation is hard.

Oh, i have to try these out to see if it effects my development cycle. I do notice that cargo check is super fast, but cargo build takes a long time. So codegen and linker could be the source of slowness.

For a clean build: number of cores (because cargo builds each crate dependency in a separate process), for a build of your crate only: single core perf.

Can you expand on this wild claim? The whole point of containers is isolation so what you are saying is that containers fail at that all the time?

Why would you not be upgrading due to a new feature of python? You don’t like new features or was that a badly wordered sentence?

I use rathole for this purpose. Works great, minimal, great performance.

Please explain more! What happened?

Did you destroy a database? Expose credentials? Nuke the company intentionally?

Today, to configure fail2ban. Before that, yesterday to select which tests to run.

Well, lemmy is a place for much more cultured audience. We can appreciate a good shitpost (that does also hold some water).

This is an overstatement, definitely. C is one of the few (mainstream) languages where memory safety vulnerabilities are even possible. So if you batch C and C++ together, they probably cover more than 90% of all the memory unsafe cove written in last 50 years, which is a strong implication that they will contribute to 90% of memory vulnerabilities.

All that said, memory vulnerabilities are about 65% of all high implact vulnerabilities on Chromium project^[1] and about 70% of vulnerabilities at Microsoft ^[2].

You are not alone. This is the work git was built for.

There is a bit of benefit if you have code reviewed so separate commits are easier to review instaed of one -900 +1278 commit.