So you could be diligent and curl into a text file, see nothing is wrong, but then when you curl into bash, it runs something different.

Normally not a fan of appimages, but this group focuses on making higher quality versions that make very few assumptions about the host system and work almost anywhere. While also prioritizing speed, small sizes, and up-to-date dependencies.

If their firewalls can detect it not being typical http/s traffic, they can block it.

I also hate configuring Konsole, most KDE apps for that matter. Being able to have a plaintext configuration file I can keep in my dotfiles is way simpler.

I don't think that's the case. The great thing about TPMs is that they measure what's on your system. As long as you modify things properly, your changes get measured and stored in the TPM.

Secure Boot is the more closed-sourced way. By default it relies on Microsoft keys unless you enroll your own and sign your stuff.

But in the same fix, they also removed the reasoning-sample, which kinda sucked.

I'll trust the words of groups like curl (https://daniel.haxx.se/blog/2026/06/10/a-human-in-control/), Linux, and even the infamously anti-AI Gnome (https://blogs.gnome.org/mcatanzaro/2026/10/02/the-era-of-sof...) that AI is finding real vulnerabilities and you're your project a disservice by ignoring them.

Edit: Though Greg did recently have a talk (that I skimmed) where he was a little reserved on LLMs: https://www.youtube.com/watch?v=NnV_cWeoo5Q

They aren't saying that AI produces bad code or is terrible for the world in some way.

It's mainly just resulting in a lot of PRs that they don't have enough time to review or features they don't plan to add.

When I was picking out that Lenovo laptop, there were dozens of different laptops just from Lenovo alone with lots of hardware variety. Then consider all the different manufacturers I could have also chosen from.

With that much hardware, it's hard to find comprehensive reviews matching the exact laptop I was looking at. And from the few reviews I did find, none of them mentioned that issue.

A model of non-Apple laptop could have serious issues, but since it's not Apple, it wouldn't have anywhere near the same media presence an Apple laptop would. With their few SKUs and popularity, the issues are visible. I did not need to follow Macs closely to know about the butterfly keyboard issues, overheating issues, etc. I wouldn't have purchased a Mac back then given those issues.

But Apple got their stuff together and fixed that. And when I was considering the M3, there were no hints of any hardware issues from the reviews I saw and discourse I read online. And thankfully that matches my experience, it's the most robust and "it just works" laptop I've used.

Made the laptop miserable to use, so I went for a MacBook instead which wouldn't have such an obvious issue be unfixed because Apple has so few SKUs to support.

Also went for it in part because I do not like Windows and macOS typically would save me when Linux support was lacking. Just had to hope for a quick port of Asahi Linux to become (unfortunately didn't happen for my M3, but thankfully it's been progressing recently).

That's strange since as Plus, you still get access to latest Pro (albeit 3.1) but not the latest Flash.

I would understand if I Plus subscribers still got access to 3.7/3.8 Flash, but it just burned through the usage limits faster.

That's not to say it's perfect. There was a pretty bad bug maybe around 2 years ago where upgrades just stopped working and without any warnings. You had a notice the issue and run a special command to fix the issue. I've also had quite a few AMD/kernel regressions recently that resulted in artifacts in the desktop and AV1 video decode.

I wish there was like a Debian but atomic that has broad support like Fedora does. Though I did see that openSUSE leap 16.1 introduced an immutable option.

So it would really be beneficial for the LLMs to be able to have their own environments to write and run code, but also to store those programs for later use automatically.

Wasn't it also the case that that the number of installs remained flat? So despite more apps being made, there didn't seem to be a demand for them.