I would have used Arch as a teenager, at that time I reinstalled DOS/Windows every other month anyways and learned a lot.

Eventually I got fed up with all that and switched to Mint.

And we can expect the same playbook

1. It’s antifa
2. It was 8 magats
3. Dirt is found on the ones filing the case.
4. A video with the 8 magats and some high level right wing personality surface
5. Crickets

Gift idea for your daughter

I would see that as a badge of honour.

D is more than 20 years old (from 2001), so it’s due for a renaissance, Python was also in its 20s before it became fashionable.

It worked on my lawn, I sprayed some weed and then there ended up being a circular hole in the grass that took a year to close. And that was the last time I did that.

Any news on how they did it?

My first thought was maybe a roundup or acid soaked towel? That could explain the pixelated look.

I wrote “RP !ud” in DuckDuckGo, and felt like a wizzard.

Fine, but do you use Arch?

Reminds me of this one

Many were increasingly of the opinion that they’d all made a big mistake in coming down from the trees in the first place. And some said that even the trees had been a bad move, and that no one should ever have left the oceans.

It depends on which floppy disk is on top of the stack.

Forget virtual desktops, when you got real desktops.

My ebook reader from 2008 still works, even if I may have to replace the battery.

The pilot should check if that yellow striped cable is a lanyard for a USB.

I remember when sourceforge was a good place to get windows software, as I recall it took over from Tucows.

I remember buying a VCD of some movie around 2000 and then 20 minutes in, I see the outline of someone getting up and walking out of the cinema the cam release was recorded in! I quit watching and from there on I only go for quality rips.

What about Slackware, LFS or BSD?

I like to treat warnings as errors and refuse releases with errors.

Occasionally I disable single warning in a specific file because it does not make sense.

Using TODO also makes sense, I’m mostly used to seeing them years after when debugging.

In your case it sounds like you may end up ignoring all the TODO’s as too many of them become noise. I would instead disable the specific warnings in the compilers options, instead of in the code, and then deal with the remaining.

Later you can disable one warning at a time and fix it.

Jnome