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.

We can go further, I think it's impossible to prevent memory leaks in a general purpose language

The Elm compiler

WTF I didn't understand, thanks for the explanation. The fact that it's used all around the world in big companies doesn't matter I guess.

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.

This: comparing something you buy once, with a license does not make a lot of sense. In SaaS, you get update, support, etc. For something critical, I'd rather get that than something that I buy once and may be buggued in the future.

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

What the actual fuck. It's a made up story I'm sure.

It's like someone has pooped on my screen.

My coworkers do document the code:

/// Returns a list of foos, given a bar. 
fn get_foos_from_bar(bar: Bar)