bbbhltz

*or distribution

Having been a (GNU-)Linux user since 2006 (desktop only), I have done what many Linux users have also done: hop around from one thing to another.

That all stopped a few years ago when I decided that I would just stick with Debian. I was happy and comfortable. It worked. I used Stable, Testing, Unstable... no issues.

That is until about 4 months ago I was cleaning and found an older laptop and decided to try something different on it: Alpine Linux.

I even wrote about it on my blog. It was such a nice installation and process that I decided to put it on my main personal laptop.

Since April I have been using Alpine and I must say I am pleased. Differences from one Linux to the next aren't much to write about. With Alpine however, I finally experienced another part of Linux that I hadn't had the opportunity to enjoy: the community.

Package requesting? Easy. Asking for help? No shame. Patience and help provided? Excellent.

None of those comments are to disparage other OS communities. It is simply that I had only ever used popular distros (Debian- and Arch-based) so I never needed to ask for help. Either way, I am still using Alpine.

So, just to repeat the titular question: what have you tried out this year? What are your impressions?

Despite the fact that 90% of what I ate was home cooked, mostly from scratch, meals, I managed to miss out on some basics like courgette (zucchini) and aubergine (eggplant) and BUTTER if you can believe it.

My mother was big on margarine. So when I moved out I continued the tradition until one day I made a fateful mistake. It was like in Ratatouille. I was sat in my studio just eating buttered bread having an out of body experience.

Came across this video earlier today. While it mat be long, I found it interesting from the perspective as a millennial to see how serious a younger cohort takes these issues.

Archive link

Not a big fan of the title (asking question in the title isn't a great idea) but the conclusions give a good summary:

The Cyber Resilience Act (CRA) represents a significant step in Europe’s efforts to enhance cybersecurity. However, its potential implications for the open source software community have raised serious concerns. Critics argue that the legislation, in its current form, could impose undue burdens on open source contributors and inadvertently increase the risk of software vulnerabilities being exploited.

New insights from GitHub’s blog post highlight additional concerns. The CRA could potentially introduce a burdensome compliance regime and penalties for open source projects that accept donations, thereby undermining the sustainability of these projects. It could also regulate open source projects unless they have “a fully decentralised development model,” potentially discouraging companies from allowing their employees to contribute to open source projects. Furthermore, the CRA could disrupt coordinated vulnerability disclosure by requiring any software developer to report to ENISA all actively exploited vulnerabilities within a timeline measured in hours after discovering them.

ARCHIVE

Reposting because rules