And here you're only talking about a subset of memory leaks, by inaccessible memory. You can also leak memory by pushing new elements in a channel while never reading them for example.

Lmao, what the heck. I've heard about that, but I still cannot believe it's true.

Yeah, I changed my career direction (industry, tech stack…) but before that, my CV only was enough for me to get hired. They would just verify the information, and sometimes, there weren't even a single tech interview.

I was so lucky in the interview for my current job: I'm working on a product with a big networking component, and I was asked to write an echo server with low level components. That was maybe the second time I had a test related to the job.

Why the fuck would they prevent private browsing? I use that a lot to be sure the session is closed correctly.

I really like this instance, so of course I'm 100% for the move

The first article is funny, because I moved from my native country to the one right next to it, and everybody is confused by my name. They have one given name and 2 family names, while I have 4 first names, and a compound last name.

No need to travel to the other side of the planet to meet a different culture of naming.

While you're at it, with sum types, you can replace this stupid nil with an optional type. Also, you can replace the stupid error handling with an either/result type. Then you can add a keyword to return early if it's left/err. Then you have Swift or Rust.

I think they just don't like cringe

As said my sibling comment, I use KDE connect with GNOME shell

And a light theme. I'm tired of websites having dark theme only.

Uh, they're different, though. There is no C++ tool (AFAIK) providing an exhaustive check of ALL the data lifetimes. I even think it's impossible, because their semantics are really different. Rust is move by default, C++ copy by default; Rust has no inheritance with its constructors, etc.