Well, given that parking in a bike lane carries a hefty fine, and that the cops don't seem to care, it's unlikely that they'd be around to notice or choose to do anything about scratched paint or a broken headlight.

I have enough anger for both.

I just went through F-Droid and counted out all the projects I have on my phone. At £5 each I'm looking at an annual bill of about £70/year... Bargain.

Thanks for the idea!

While it's understandable that you might think so, that's not where this is coming from.

The white poppy comes from the UK originally where they treat Remembrance Day rather differently from the way we do. While in Canada, it's a moment to remember the horrors of war and the millions lost when we embrace industrial scale international violence, the UK really doubles down on the whole "To Our Glorious Dead" thing. They take the day to recognise the sacrifices "for freedom" and other deeply propagandistic ideas.

So in rejection of this, the white poppy came about as a rejection of this messaging. In a way, it's an effort to make Remembrance Day more how Canadians tend to recognise it.

If the white poppy is now appearing in Canada, it might be in answer to how the day is changing culturally.

Source: I was born and raised in Canada. My grandfather fought in our armed forces to liberate the Netherlands and we attended Remembrance Day ceremonies regularly as far back as I can remember. I emigrated to the UK when I was in my 30s, and I will not wear a poppy here. It means something very different.

Oh boy are you going to love-to-hate this then. It's best viewed on a proper computer, but you'll get the gist on mobile too.

This too is an excellent take. "Artificial pain points" for capitalism, or "learn some shit" for Linux. Love it.

In my experience, the larger the company, the more likely they are to force you to use Windows. The smaller companies will be more relaxed about the whole thing.

The largest company I've worked for that allows Linux had a staff count of hundreds of engineers and hundreds more non-nerds. In their case though, the laptops were crippled with Crowdstrike and Kollide and while the tech team was working hard to support us, we were always aware that we made up around 1% of the machines they manage and represented a big chunk of their headaches.

The response to this you usually hear (from me even) is that "I don't need support, I know what I'm doing". Which is probably true, but the vast majority of problems is in dealing with access to proprietary systems, failures from Crowdstrike or complaints about kernel versions etc.

TL;DR: work at a small company (<100 staff) and they'll probably leave you alone. Go bigger and you'll be stuck fighting IT in one way or another.

That you cannot understand technology without understanding the people. And you cannot understand people without understanding politics. Every choice you made has an impact on the world.

As it happens, I had this very conversation with a high school kid yesterday who was in my office on work experience. She said something to the effect of "I'm not political" to which I looked her dead in the eye and said: "You should be. Everything is political".

Thanks for sharing. It's always good to see people advocating for Free licensing for the right reasons.

A lot of places don't have buses and the roads aren't safe for kids to cycle anymore. The assumption is that if you're a parent, you just have to "make time" some-crazy-how.

Honestly, this is so much better than those cases when the codebase is an absolute fucking nightmare are the senior dev doesn't see it. Instead they gaslight you into thinking that this is actually best practice.

yt-dlp is pretty much the authoritative solution for this these days.

When I stepped away from my own (mildly successful) Free software project, I had the same concerns: it's about the reputation.

The project had earned a decent amount of trust when I was running it, and presumably people were installing new updates without going over the changes. If I handed off the project to someone new, I wasn't just handing over the work, but that trust as well.

So rather than handing over the project to someone new, I archived it and someone else (thankfully someone not-evil) forked it. Anyone installing the fork immediately understood that the relationship was new. They'd have to decide whether to trust this new maintainer or not.

For my money, this is the way. If you're burning out, remember that your reputation is tied to your project name, and that it has considerable value. If you don't want to continue, the disruption of a fork is better/safer than the smooth-but-risky hand-off.