I assume this is about the Android gallery app? You may want to try an alternative, like Fossify Gallery. I switched for the exact reasons you say and the paid/locked filters that I don't use anyway.
That's not it. The core issue is AAA sites vs apps. Let me explain.
Public sites need to load quickly and use progressive enhancement, work without JavaScript even. Next.js is driving this with server side rendering and hybrid approaches. They've done a great job so far.
Then there are applications that have a browser UI. These typically use a JSON-based API (REST, RPC, or GraphQL doesn't matter). These apps don't require server side rendering and their API backend can be anything.
In the latter model, you just host a bunch of static assets and point them to your API. No need for compute, everything is done client side (except API operations of course).
In the first model, you need to pay for rendering and it guides you into doing the API the same way. Closer to older PHP/ASP sites but on steroids.
This move caters to Next.js. IMO, as a lot of recent developments do.
I use Arch almost exclusively on the desktop but I gave up on running it on servers that I don't want to actively maintain (think of small, non-critical web servers). Ubuntu works fine there.
I found this a few days ago when I was researching SVG in Flutter. After the initial "why not SVG?" reaction, this is not that bad! As the README says, It is a format for efficient presentation, not an authoring format. You're supposed to author in SVG etc and then export to IVG.
However, SVG Native [1] seems to be very similar, and it's also a subset of SVG, and non-binary.
I noticed a light blue or sky blue color used as the accent color (on Windows at the moment). Screenshot: https://imgur.com/a/yZUXhxf
It's even used as outline on this textbox I'm typing in. I would expect it to use the system accent color, but it does not! Any ideas if I can customize just this color, without installing a different theme?
While interesting, this sounds like giving the keys to "the internet" to a handful of key manufacturers. There's also the cost of the devices, which is significant, making this useful for only a tiny percentage of the world. I'm also skeptical about the privacy guarantees; how large would the manufacturer batches have to be to be accepted? and how many people within my geo-ip range have a device from that batch?
It does have another big architectural weakness: no detachable windows (see issue #10121). Not impossible to fix but quite hard.
And while the embedded dev tools is very cool, especially for the headless browser, it only brings in even more windows in the main VS Code window. Notice how dev tools typically take the largest part of the screen. In many workflows it is beneficial to have the dev tools on a second or third monitor so it doesn't obscure the code.
Agreed but you got very large monitors. If you have regular sized monitors (~23-24") then you can arrange them in more creative ways than horizontally.
I'm using 3 monitors - the two main are right in front of me, the one on top of the other, and the 3rd is on the side, rotated vertically. I tried several arrangements and I found this one working great for me.