hairyballs @ hairyballs @programming.dev

Posts

0

Comments

43

Joined

3 yr. ago

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.

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.

• I put the types first in the file, sorted by importance
• then the public free functions
• then the impl blocks, sorted by importance, also. Usually, display impls and similar end up being at the end
• then the private free functions (helpers)

The idea is that I can see all the types in one glance, then I look at the rest.

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

It's a toy example. In that case, the solution is to assign the expression to a variable to compute its result upfront.

There are still obvious things the BC cannot get. For example:

    
struct Foo;

impl Foo {
    fn num(&mut self) -> usize { 0 }
    fn index(&mut self, _i: usize) { }
}

let foo = Foo;
foo.index(foo.num()); //error

  

It's like someone has pooped on my screen.

Genuine question: what's wrong with templating engines?

My coworkers do document the code:

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

  

Htmx is a godsend for that. You actually write HTML while having AJAX easily.

The desktop website is so bad... I ask for a light theme in my settings, they don't care (it's white on black) because it's HARD to add a few CSS rules. Then there is a flash of light which could give a seizure to someone with a condition. It's shitty design at its peak. That doesn't really inspire confidence...

Firefox is really badly integrated in MacOS. The fn + arrow shortcut doesn't work, for example, it's not integrated in the menu system (the menu shortcuts don't work) etc. But there is Sideberry, so...

Nope, my webpages are not just nested divs. I use nav, main, form, select, etc to name a few. I actually use very few JS. It's mainly for communication with the server when I need AJAX to retrieve data.

It's much easier to work with streams of untyped data in a weakly typed language.