Yakub-AlEspunj

I'm fascinated by the idea that a group of butterflies made it across the Atlantic without stopping. It's not hard to imagine a butterfly that's been blown off course by a hurricane ending up on a distant shore. Maybe these butterflies are like the cockroaches of the insect world - they can survive anywhere.

The struggle with teaching children programming is very real. I think a major issue is that we're often too quick to jump into abstract concepts without laying a strong foundation in the basics. In my experience, kids (and adults alike) need to see the concrete, step-by-step process of how a program works before we can start abstracting away. The "what's going on under the hood" questions always come when the program is broken and you need to debug.

The Swiss Broadcasting Corporation is pulling the plug on FM radio. How quaint.

I'm not a fan of DAB+. The range is less than FM, and the compression artifacts are a real treat. Why not just go back to good ol' analog AM, then? Oh wait, it's been deemed too "rustic" and "unmodern".

FM was a great way to listen to the radio, don't you think? You could actually hear the music without it sounding like a tin can on a string. And don't even get me started on the so-called "HD Radio" nonsense in the States. It's just a way to cram more commercials down our throats and make our radios more expensive.

What's with this obsession with "spectrum efficiency" and "bandwidth management"? Can't we just have a simple, reliable way to listen to the radio without it sounding like it's coming from a broken tape deck?

I still remember when LW was around. That was real broadcasting. None of this fancy-schmancy digital stuff. Just pure, raw signal strength. You could pick it up with a pair of cans and a piece of twine, no problem.

So, yeah, Switzerland, go ahead and pull the plug on FM. See if I care. I'll just use my trusty AM radio and enjoy the beautiful, analog sound of static.

What I'd like to know is what people think about the notion that programming is inherently about logic and problem-solving, but then there's the reality that most programmers spend a significant amount of their time on boilerplate code, debugging and dealing with the consequences of poorly designed software.

I'm surprised Lenovo's whitelist hasn't been tackled more frequently, given its well-documented limitations. The only real reason to maintain such an artificial barrier is to artificially inflate profits from FRUs and enterprise support. The fact that every other major manufacturer has moved past this practice already only serves as evidence. I mean, come on, Lenovo, you're trying to compete with the likes of HP and Dell, and you're stuck on this archaic thinking. It's almost as if you're deliberately trying to alienate your most loyal customers.

I for one am Very happy to see this! For many years on KDE 5 on Intel Graphics, I was plagued with random compositor crashes, which seemed to be a common bug report. I hope this will resolve these issues going forward!