heinrich5991

There's also `progress` which works for tools mainly operating on a single file, but unlike `pv`, you don't have to start the tool differently. It'd e.g. work nicely for the `gzip` example. Just call `progress` on a different terminal while `gzip` is running.

What are "ThomPike* macros"?

> If you use i32, it looks like you care.

In Rust, that's not really the case. `i32` is the go-to integer type.

`isize` on the other hand would look really weird in code — it's an almost unused integer type. I also prefer having integers that don't depend on the machine I'm running them on.

Actually, if you don't care about the size of your small number, use `i32`. If it's a big number, use `i64`.

`isize`/`usize` should only be used for memory-related quantities — that's why they renamed from `int`/`uint`.

Permalink (press 'y' anywhere on GitHub): https://github.com/torvalds/linux/blob/4d939780b70592e0f4bc6....

Almost. You need a workaround for chatting with new numbers and can't add anyone to groups.

Even worse:

    /issues/
    /issues/:id
    /pulls/
    /pulls/:author
    /pull/:id

> Also the above will not compile.

It compiled for me (after changing NULL to nullptr).

> Because compilers can actually detect if you set a pointer to nullptr and then use it.

Apparently it didn't.

> Here, you didn't use it so maybe the compiler won't complain. But in the general case yes it will complain.

That's incorrect, there's a use of the nullptr.

> You call some unsafe code that directly interacts with memory.

I don't see something explicitly declared as unsafe from the source code alone. It looks like a normal pointer dereference to me.

It's used in Firefox. See e.g. the infobox of https://en.wikipedia.org/w/index.php?title=Firefox&oldid=123....

18 including the leading 3.

AFAIK most of modern web browser vulnerabilities come from JavaScript engines.

This diagram should be zero-aligned at the very least.

It actually seems to be only .desi. Or does it? For .wed, I see a document titled "Final Determination by ICANN to Not Transition Operation of the gTLD (19 May 2021)", but it says that "ICANN org will proceed to make arrangements towards a transition of the .wed TLD to a successor Registry Operator following the Registry Transition Process with a Request for Proposals."

Permalink (press 'y' anywhere on github): https://github.com/nate-parrott/ball/blob/609f3bdba21b6a6a59...

Why is the Bluetooth LE Audio protocol problematic?

I guess BI stands for https://en.wikipedia.org/wiki/Business_intelligence?

They helpfully send the whole article before asking you to enable tracking cookies. You can e.g. use reader mode to read the article. This mostly seems like an oversight on their part though.

Archive link: https://archive.is/kGByU.

Orginal article, submission link is machine-translated by the publisher: https://www.heise.de/news/ARM-will-Verkauf-aller-neuen-PCs-m....

You can use vaultwarden for self-hosting: https://github.com/dani-garcia/vaultwarden/. It's easier than the official server.

Bitwarden

+ cross-platform

+ free as in beer

+ free and open-source software

Can't really comment on convenience, I moved from LastPass, but it has worked well for me.

C++, Nim, Rust, Zig would probably work as well.

No need to go to the kernel API to create filenames that are invalid UTF-16. The Win32 API will happily let you do it.

The grandparent does not present a dichotomy, let alone a false one. It says that when you are not using email patches, the network effect of the platform (like Gitea which you present as if it was explicitly excluded by the grandparent) is important.

A checksum is usually intended not to match if the checksum itself is corrupted.

Concurrency with rayon in Rust isn't pain, I'd say. It's basically hidden away from the user.

sin(x) is platform-dependent.

Working link: https://github.com/layerdiffusion/sd-forge-layerdiffusion/as....