From what I am seeing around me though, reading for pleasure or even to gain knowledge has decreased a lot. I noticed it in adults first and this is being reflected in their children.

You'll lose the ability to easily and quickly look at the photos, as in a single click and you're in, but the process would achieve what you want. To view the photos, you can mount a decrypted version whenever you actually want to look at them and can automate some of this process if it is time consuming or you do it frequently. This is all much easier to do on a computer rather than a mobile a device.

On Linux, there's ecryptfs. There were a few other similar tools in various states of maturity and maintenance when I checked. Perhaps look into something similar for your platform.

In my experience, this is what ended up happening.

And what's a proper cooldown? 1 day? 3 days? 1 week? 1 month? If you have a vulnerability, now you're exposed during that cooldown period. There's no straight forward or easy answer here.

I am speaking from my own experience here with having to sit in during these discussions where security "advice" is provided to the development team without understanding what it entails or any tradeoffs. I found that keeping things relatively secure is hard work and needs to be a part of culture.

On the other hand, I notice the AI-fundamentalists(I am not sure how to refer to people within that group) just say that you won't be doing any hand coding anymore and you'd "just" ask something like claude to maintain it or re-write.

I believe the point being discussed is the scale of "badness" that vibe-coding introduces.

Having a command runner within your project will mask a lot of the issues the author mentioned. And although, in my experience, having a command runner for mid-sized projects and up is useful for many things, masking the UX issues means there's a problem.

I got on the uv bandwagon relatively recently as most of my work is maintaining older python projects so I've been using it for new builds. Although the speed part is welcome, I couldn't see what the big deal is and mostly keep on using it because it is a popular tool(there are benefits to that in my line of work) and not necessarily because it can do something that couldn't be done before though with a couple of other tools. Whether it is beneficial or detrimental to having all of that functionality within one tool, to me, is a matter of opinion.

The problem to me is that I've seen this cycle many times before. New tool shows up claiming it is far superior to everything else with speed being a major factor and everyone else is doing it wrong. Even though the new tool does a fraction of what the old "bad" tool is doing. With adoption comes increased functionality and demands and the new tool starts morphing into the old tool with the same claimed downsides. The UX issues to me are a symptom of that process.

I still think uv is a fine tool. I've used poetry before and sometimes plain old pip. They're all fine with each tool catering to different use cases, in my opinion. Sometimes you have to add pyenv, sometimes you don't. Sometimes you add direnv, sometimes you don't and so on. And I've cursed at everyone of them at times. However, the fanboyism is very strong with uv which makes me wonder why.

It's going to be interesting to watch this unfold. Google's automation vs LLM agents, no humans from either side.

Anyone feels like all this money spent on weapons and war would better benefit humanity if invested in other industries? These days it is either wasted on AI, technology marketed at making people obsolete, or weapons, technology to kill people. Sad.

The build quality has improved over the past 5 generations or so. It was getting too plastic-y and felt brittle. Nothing like the original thinkpads though, those were built like bricks.

Something bad did end up happening due to that lax security and there were oh so many meetings about it.