Nor have they been keen on letting users OR devs customize the ui.

> users customize the UI

The home and widgets screen can be customized to the point you don't recognize it as iOS

> devs customize the UI

Have you used Spotify? It completely ignores Apple UI and does its own thing cross platform. If you mean let devs customize the OS' UI, why would they? UI consistency is one of Apple's core strengths (or so it was before the 26 releases).

The unused variable error drives me insane

If they wanted the release build to be an error I wouldn't care. Having the current solution be "have the editor automatically change code to include or remove the underscore" is so wrong to me. Just invented a problem that needs tooling to modify source code to fix.

Maybe they already did and the answer was in some way lacking so they asked a peer.

Being mentored is infinitely better than a text box spitting out subtly wrong answers.

I'm confused what else you think they are?

Its fundamentally how LLMs work.

"Magic"

> If I ever start using any query strings, I’ll allow only known parameters.

They aren't saying the concept of query strings are bad, They're saying unsolicited query strings during referal are the issue.

Doesn't look like that has been or will ever be (generally) learned.

And how much do they exhale over 8h of AI use?

I've found widewine a blessing because news sites that autoplay trash seem to be the only group that uses it (other than paid media platforms like Netflix and Spotify).

The blessing is I can just reject it and it blocks all their videos from playing/downloading.

Its hyperbolic but hits the point.

I've helped multiple coworkers (in a non-computer related field) sideload F-Droid for a few spyware/ad free apps they liked the look of.

Id sideload my own phone using adb but I'd tell them theyre out of luck.

I'm in a similar boat, but I've found where I once habitually put things in the same workspace every time and was able to trivially recall them, I now end up all over the place.

Also I've been missing scratch deeply.

I'm sure it's solvable with some diligence and config changes, but I haven't invested the time yet.

I'd agree with sph about having one workspace per activity. I've never had a rigid workflow with lots of permanent named workspaces, but I have a workspace-naming script that lets me label my numbered workspaces after they've been set up.

Other things that help include a fuzzel-based open window searcher and, to be honest, restrained use of Niri's flagship scrolling feature. Most of my workspaces most of the time are the same size as my screen, with the scroll used very sparingly for usually temporary overflow.

I guess it also helps that I never used the i3 scratchpad so I don't miss it.

I mentioned elsewhere that scrolling WMs shine when you use a workspace per activity. You should never "have stuff all over the place", you should be working on a single one until you context switch.

This is sway on scrolling steroids:

https://github.com/dawsers/scroll