> How wide should the indentation be? 2 spaces? 4? 8? Something else?
> By making the indent be a tab, you get to decide the answer to that question and everyone will see code indented as wide (or not) as they prefer.
> In short, this is what the tab character is for.
0: https://groups.google.com/g/golang-nuts/c/iHGLTFalb54/m/zqMo...
All in all, it's several things that need to be reinforced. The distribution network needs to be smarter. The energy generation facilities need to be tested through their entire voltage range, so they can be counted upon. And there has to be more voltage inertia available in the network.
The proof is that multiple competitor products have been launched since, and all of them have had sync issues at some point, with different degrees of severity ranging from sync delays, through data conflicts, up to loss of data in all synced devices. To this day, I still trust Dropbox more than its competition. This includes custom rsync scripts.
It looked like SteamOS was going to be a contender, but apparently not.
Back on Linuxland, the userbase realized this about two decades ago, when Ubuntu launched. Having a nice default experience was considered better than having easy tweakability, because Ubuntu could also be configured to the fullest extent in the classic Linux way of reaching into the guts of the system and rearranging things to taste. Not that I would ever recommend tweaking Ubuntu too much, but it can be done.
What about the other end? Most people who like fiddling with Linux by reaching into its internals have settled on distributions such as Arch, where this way of managing the system is expected and thus the distribution works to ensure this experience is as easy and predictable as it can be, by providing a good happy path experience for common scenarios, and providing top-notch documentation for common and uncommon customization options, or minority hardware platforms and devices.
Strictly speaking they only lose all results, FOR SURE, if they have to reboot ALL the servers at the same time. If they implemented a system where the cached results are shared and replicated among all their servers, it can in theory be kept cached indefinitely.
> Each time the Leta application is restarted (due to an upgrade, or new version) server side, a new secret hash is generated, meaning that all previous search queries are no longer visible to Leta.
If I read this correctly, the cached data is per-instance, there would be no way to share cached data among instances if each one has its own secret hash and they are cycled on each start.
Have a look at the linked https://m3.material.io/blog/building-with-m3-expressive to get a better impression of what this is about. From the guidelines given there, many parts of the design make sense and will help designs work better - grouping objects properly, be aware of contrast to highlight important elements, more options for good typography (instead of basically none, Android/Material offered nothing by default), helpers for highlighting buttons etc. It's also still simply a good idea to focus on good animations that actually work for the UI, instead of being superfluous baggage, and then to make them feel nice. I'm not saying it's groundbreaking, but it's helpful to have something like this as an official guideline, and be it to reign in rogue designers.
But it's still a flat design, and thus does not properly transport clickability. And their weird approach for the color schemes still leads to an ugly mess, pastel with weird contrasts and color combinations that just are ugly. I haven't seen a proper analysis what's going on there, but it sucks. Also, this whole design system is very far from leading to a consistent system, but that seems to be a non-goal, just some standard component building blocks are there to foster familiarity.
Better than nothing and probably a step up, but M3E doesn't convince me totally so far.
It's an actual objective fact of life.
You don't get a larger 15"/16"/17" inch screen. You get a screen that size minus the notch because of a psychotic obsession with thinness. And then they struggle to compensate for that with barely working workarounds in software that don't cover even half of cases.
If you want to avoid the extra space, it's as easy as using a 16:10 resolution size. The menubar will drop down to the 16:10 space.