But, as a long time but infrequent user, I really dislike the changes towards "non-destructive" UX that just seems to spawn endless layers and other forms of pixel buffer limbo that confuse me. Lately, it feels like I'm being slow walked by a passive-aggressive tool that wants to waste my time and mental energy.

I wish there was a "novice" or "casual" user setting option to go back to a much simpler UX, where I am operating immediately on the selected layer. Where a pasted object can be dragged but anchors as soon as I touch something else, etc. Where filters preview but then "apply" immediately. Where undo can revert some recent changes but otherwise the effects accumulate destructively into the current layer.

A naive user may never have to learn about layers, but they are still there when desired. I don't want a layer spawning on their own. I'll make the new layer before I start changing things, and I'll think deliberately how I want that layer filled. Then, I'll resume actions that immediately mutate it.

In the mid 90s, I got myself a DEC Multia (small Alpha-based workstation) to run Linux. It was fast at some things, but useless to browse the newly emerging web. Netscape Navigator wasn't available as an Alpha binary, and the emulated x86 was just as slow as an early Python based browser. Running Netscape on a 486DX3-100 was night and day like visiting the future. Some other native programs went the other way, with the Alpha beating the 486 dearly. But the web browser became more and more significant.

In college, I was also told I should covet Sun hardware. At my first job, I got issued a Sun Ultra workstation of some sort. I was appalled at how slow it was for my FOSS C programming workflows with autoconf/make/gcc etc. I started bringing in a Dell notebook with a Pentium-MMX running Linux, and it ran circles around the Ultra for actual day to day tasks. On the other hand, when I had to run certain commercial tools like Purify, the Sun was useful again.

I also had exposure to supercomputer centers at the time, doing portability work for our HPC codebase. It was often crazy how slow these platforms were for development work. There may have been a little bit of neglect by the vendors or IT groups in terms of what hardware they dedicated as front-end service nodes on these big machines. But, there were also dramatic differneces in the operating system behavior, tuned to get one user-level job running and get out of the way. They were terrible at multitasking, and this showed through in CLI/scripted interactivity too.

Sometimes, I wonder if some of those platforms could have survived if they jumped on the Linux bandwagon and kept developing their hardware. But maybe their fate was sealed because they depended on the bundling of their proprietary OS and hardware, neither of which was able to adapt to the new order...

For IAL2 identity proofing, Login.gov is only for US persons, i.e. validating US-issued credentials. Meanwhile. ID.me has support to validate foreign passports.

So, if TreasuryDirect supports foreign customers, it makes sense to offer ID.me, but it seems inappropriate not to offer Login.gov for customers who are US persons!

It's quite different than just reading a lot of text from other authors and passively absorbing diction and style. Instead, it means getting detailed reinforcement signals in the context of your own active writing effort.

This can start an ironic reinforcement learning pattern where the writer gets tuned to write in the LLM's "corrected" form. Imagine a traditional professional writer, in a long-term partnership with a particular copy editor who gates their output.

The problem with this kind of feature is that it falls apart if you're the type who leaves things unread or gets them all the time. Then, it is little more than a beacon to say "phone still exists"...

Many of the debates in the comments seem to come down to whether people believe prediction and extrapolation are synonymous.

These things can definitely erode the targets. Tomography experiments have to think carefully to optimize the set exposure angles used during a session, because the target degrades more with each shot.

Or maybe some kind of hybrid of x-ray microtomography and spectroscopic analysis all in one.

But, maybe the energies involved would be about the same destructive power as some microtome slicing technique...

A similar analogy is how 2-phase commit protocols enact (virtual) escrow.

The pigeon-hole principle isn't an instruction guide for birds, it just describes the reality of occupancy. An egg-tooth keeps pecking, escaping at most one egg. A dog may circle, but occupies at most one bed.

The real value of idempotence is being truly end-to-end. It is about the final effect being controlled, rather than about some message hop in the middle. In my opinion, the impulse to isolate it to a messaging layer is often misguided. It presupposes that the other layers don't also have similar failure modes.

It makes for a more robust system when you can elicit the desired idempotence from natural keys and occupancy rules. For example, the way REST can make creation idempotent when the name can be established ahead of the creation request, or deletion is idempotent when names are not reused.

There are families out there still with 18-20 year cycles and could pretty much tick off every generation.

And families like mine that more or less skip every other: Silent -> X -> Z -> ???.

Of course there are other permutations, since life is full of so many uncontrollable factors.

Imagine pusing for locked down paper so kids can't pass notes nor make spit-wads and airplanes. Or locked down pens to prevent tic-tac-toe, doodling, lewd drawings, or scrawling graffiti on those old desks.

Some kind of KYC rules so that the older kids at school cannot pass their broader understanding of the world and cussing vocabulary down to the impressionable younger kids. Age restrictions on the trail to the woods, where kids somehow always knew about that stash of dirty magazines...

The parallel trees could have different ownership and access privileges, so that the editable working copy does not require the same filesystem access rights as the metadata tree. The git CLI actions would be performed with the more privileged filesystem role, and it would also have to be audited to make sure it treats all the working copy content as untrusted payload.

Edit: Or, a fair closed-system comparison to a battery would need to include a liquid oxygen tank or similar so you have the two components stored but can control the delivery...

But that's because today's world is forcing us towards overwhelming risk management and compliance systems like NIST 800-53 and friends. If anything, these mechanisms are being drawn, quartered, and spread to the opposite corners of the Earth.

Control via configuration management systems with configuration drift detection etc. Outputs and diagnostics via monitoring, logging, audit, and accountability systems. Authorization systems with extreme least privilege, draconian rules for privileged role assumption. Interaction removed from the entire operations plane, so it only exists in some application domain concepts as a sort of ship in a bottle, which eventually perversely recurses into the same mindset for domains with interesting content and user roles.

Lots of access path restrictions intentionally limiting which usage scenario is available in which combination to which user type from which locale with which client device.

So the idea of flexible and convenient fusion of many different IO and control paths into a portable and remotely attachable terminal UX seems like the complete antithesis..?

I have a long term interest in full electrification, but find the process daunting due to the interlocking set upgrades. Between insulation envelope upgrades and electrical system upgrades, there is a lot of potentially disruptive work needed to even allow permits to be issued for heat-pump HVAC and water heater or fully electric kitchen.

If the internal wiring also needs much work, it threatens to be almost as invasive as a gut renovation. Then, I ponder what other work we'd want to piggyback on it. But then it all sounds too much for life and budgets, so we procrastinate...

The steering of the jet stream seems to have some qualitative changes in these conditions but also more chaos. It could steer storms anywhere along the coast, so different parts of CA, OR, and WA get different impact. Just in my lifetime in CA, I've witnessed some very wet El Niño winters but also some drier than average.

The biggest precipitation threat on the west coast seems to be a repeat of some of the biggest flooding events known historically or geologically. But, these are relatively infrequent and most of the record predates any understanding or tracking of the El Niño oscillation. So the correlation cannot be stated so clearly. These are atmospheric river events which seem to stall, producing heavy rains over the same area for a much longer period.

Just in the recent centuries of CA history, there have been massive floods in northern and southern regions in different month-long rain events. There have been improvements to flood control infrastructure since then. But, the only reason those events aren't known as the most costly is because there wasn't as much economic development here back when the floods happened.

Our usual storms sweep through an area the heaviest rains over just part of a day. Our varied terrain means that each individual storm also has very uneven rainfall amounts due to orographic intensification. Prominences with the right aspect towards the wind will get far more accumulation. Our watersheds can absorb quite a bit of this, but even those brief rains can cause localized flooding.

If the rain continues for many days in a row, we will see widespread mudslides and flooding of larger rivers, basins, etc. Some of the historically extreme events had rain persisting for over a month!

Edit: along with these "mega storm" scenarios, we also have evidence of "mega droughts". It's worrisome to imagine what challenges may come from a more energetic and chaotic climate.

I think its just as important to realize ideas themselves can be conflicted or contradictory, and that practical action requires compromise. Many seductive ideas may not be well-formed if you really dig deeply enough. It's not just economic or political pragmatism. Even the solo designer/thinker needs to compromise such untested ideas in search of a realizable system.