lad

Did it help, have you managed to get rid of the sounds?

I went from Debian to Mint

It’s kinda comical to imagine them caring to keep that source code a secret decades after its deprecation.

I feel like this is very common and it makes it much less comical. There are cases where sources were leaked, but still not legally available, afaik

I don’t quite get what sense does ‘the flinch’ in the title have beyond being a reference to The Hitchhiker’s Guide to the Galaxy. It reads as if it was something bad, but the post is just a list of thanks

No True Scotsman, ey?

I’m not entirely sold on the idea, because the article shows no example of defining and using special error codes. It leaves an impression that if anything you want to recover from is IO and HTTP (no HTTP/2, too) then it’s all good.

Still it looks interesting and I will take a deeper look into it later

Wait, can’t this presumed weapon of mass rustification coreutils clone be also re-published under GPL?

Well, one time it did help me when I knew the password but it didn’t work

If it got wings and human body, it angel

You were right, it’s an entertaining if a bit unsettling comment section

Depends on your soup alignment

The author claims to be an expert in Rust, so at least they don’t come from a standpoint of ‘I hate Rust and everyone who recommends it’ which seems to be somewhat popular

I almost agree, but I think that supporting old hardware practically forever would be a nice thing to have.

Luckily, it doesn’t evolve anymore and given time Rust will likely have that support if it would be necessary for its role in the kernel.

Yeah, I can totally see pet projects done with this, it would be relatively simple to understand by others, and you can get to know your project through and through.

have no package manager and encourage less code reuse as a shared value

Also, its main goal is understandability, but some stdlib is written in assembly. I mean, this looks like a nice but very niche language, for some small endeavours maybe?

it’s clear at this point already that Zig is a weakly-typed language

Uhm… pretty sure it isn’t.

They seem to think any type inference makes for a weak typing, judging by their previous rant about auto in C++

So, yeah, author’s views are a bit special, not sure this article will help me be better :(

This quote from Linus is what I find inspiring hope of a future wider adoption or Rust:

Thanks. I decided to try to do the merge on my own, but failed. I came close, but it was good to have your example merge to see what I got wrong.

The pin_init becoming a crate of its own, but ‘pin::Pin’ being in the core crate ended up messing with my “monkey see, monkey do” approach to Rust merges.

I’ll learn eventually, in the meantime please do continue to give me example merges and I’ll use them as training wheels.

Not everything that’s poorly written is ai, you should give humans more credit

We have an engineering manager that’s about the same, the only issue is that they let PR through because features are wanted and there’s no time to get things right.

I think, I may be pleased to have to redo everything several times to make it better and simpler, but what we get is that everything is bad but we’ll still merge 😞

I now feel at several times I fucked up quite a lot by making something that works but not something simpler.

My girlfriend is gonna be mighty upset is she thinks I’m into that kinda thing. […] please change the image to something Gnome-related and/or trustworthy.

That’s an interesting takeaway from a DDoS issue