I think you already used a pretty nice way, which is using shadowing. If one variable is only used for the creation of another, simply shadowing it keeps your namespace clean.

Sometimes it doesn’t make sense to give the shadowed variable the same name, because that name doesn’t describe its content very well. But in this case it seems like that is not a concern.

https://github.com/NixOS/nixpkgs

You could also improve the current NixOS setup, that would make creating a new instance a lot easier!

In Java you get a bunch of unexpected NullPointerExceptions instead…

They certainly do like to use the word “in” a lot.

What kovarex controversy? Link? Context?

!nottheonion@lemmy.ml

Does GDPR apply to stackoverflow? Since my data there probably does not identify me as a person?

Trump is too unironically placed next to two important persons from US history here. Ethically questionable.

Linux kernel guilty as well. It reports memory in “kb”, but digging through documentation, you will at some point see that they actually mean KiB. The “kb” would be 1000 bits.

Oh nice! Does this exist for EU as well?

It is enough if his name appears just once. Modern language models take more than just the last few characters as context.

mysql_real_escape_string

Copilot is just an LLM trained on all GitHub code. Hence it gives you random stuff from some open source code bases.

It’s the independent 🤷‍♂️

Interesting. But the article headline is misleading. The article states that the biggest difference was between volatile anonymity where people could make arbitrarily many accounts, and stable pseudonyms, where a ban cannot easily be evaded. Stable pseudonyms are a lot better as the article states.

Between stable pseudonyms and real names, the difference is smaller, as stated in the article. Real names make it only slightly worse.

This is often done by people while the project is unstable. No need to write documentation that gets outdated every few weeks, when you can help people live in discord.

Hyperloop tubes are now used as spaghetti storages?

(I didn’t watch the video, just looked at the thumbnail)

Nice to see that they have trust in Rust!

I would really wish that the async ecosystem would not be based around runtimes, but would separate runtimes from async libraries. Like let me do file IO async without having to choose between async-std, Tokio, or whatnot for that.