Some HTTP certificates do exactly that, and web browsers used to show the company/identity the certificate was issued to in the URL bar. Now you have to go to the certificates detail, very clear on Firefox, behind a few clicks on Chrome. Here's an example from a bank in Spain: https://www.bbva.es
The current version is 0.0.13 (on the homepage), it's normal that the author is focusing on their platform at the moment. It probably was too son to post it on here.
Not the OP but I use all the programs full screen / maximized. I change windows with alt+tab or maybe I reach down to the dock to select the app icon quicker. I only see my wallpaper when changing workspaces, because the animation shows it a split second. I do use the command line but it's not the only way to not show the wallpaper. This is true whether I'm on Linux or macOS.
Also me but on Windows 10. I only see the wall paper just after I've booted the machine and within a few seconds at least one window is maximised (typically a tabbed browser), started from the task bar. alt+tab after that
It's also a sneaky strategy to deal with features you've decided to remove, because users are that fucking stupid.
1. Instead of just removing the feature, hide the feature and call it unsupported so the users who remember the feature can't complain yet.
2. Then finally remove the feature in the next update, with justification that it was an unsupported option and used by few people, so users can't complain.
Frog boiled. With each update the company seems to be acting rationally on "metrics" and principles, but the decision was set internally before that.
Of course, people who modify their settings in the first place are more likely to disable telemetry, particularly if they're choosing a non-default, low market-share application that specifically bills itself as privacy friendly.
If I recall correctly, that was their justification for no longer supporting it: too few people used it. Except it was tucked away in a small dropdown at the bottom of the customize toolbar screen, which requires right-clicking the toolbar to get to. If it was in the actual settings somewhere or, better yet, given as an option during the first launch flow, I imagine more people would've used it.
I didn't even know about it until after it became unsupported.
Usually when people call a feature bloat it’s because its presence, resource consumption, etc is too great relative to its value and utility to users or it’s not particularly relevant.
I’d hesitate to call something like optional compact UI metrics “bloat”. To me the term is better applied to e.g. features associated with only tangentially related services or something running in the background sucking up CPU cycles for little user benefit… basically the modern Microsoft playbook.
Code bloat is not that obscure of a thing. I think a decent portion of people realize that a program with features upon features is stretched too thin to meet users' needs in high quality, or in a timely fashion, especially if they paid $0 for it.
Don't get me wrong. When Firefox removes a feature, often it's not out the concern of bloat to be able to serve existing users better, but to shift resources for the next revamp that will make the browser ever more "modern", to claw for a new userbase.
All features require maintenance as code around them and through them changes with time. Feature bloat is very often code bloat and maintaining code costs money, especially 20 million lines of it. When a module owner sees an opportunity to improve their module by removing low-use features that are built on code that's a challenge to maintain, that's a good thing for the long term health of the code base and the features it provides and the app they make up.
It's possible. I remember one app that opened a webview to their terms of use page, which somewhere had a link to a Google page, which I could use to go to Google search. So, no direct URL input, but you could go to any website indexed.
IIRC webview, by default, requires a dev to whitelist domains. Maybe that has changed, IDK.
But finding an example where you can navigate elsewhere is not proof that all webviews are broken; maybe they have this "security issue" by default and allow a dev to tighten it (bad sec. practice IMO), and maybe android versions or SDK-versions differ in how they adhere, IDK. But the times that I encountered this and fiddled with it, it was a PIAS to even allow loading a page from another domain.
Another pro in my book: it "compiles" to a single binary. I was writing a small side project and when it was time to deploy, it was as easy as to push the binary to my server via `scp`. That single binary also includes a copy of `sqlite` since it is a WASM dependency. Also, cross compilation. I can compile it from my m1 mac for an x86 linux server.
How's the performance vs ffi version? I'm about to use deno with sqlite and have to decide which one to use. The lack of WAL in WASM version gives me a pause though.
