If you join multiple/many tables, you could end up with a large volume of data. And yes, this is bit-for-bit duplication—on the network. The query result is (typically) a single table. This table will get serialized as-is, with all duplicate data.
I actually think the search feature rocks, because you have high fidelity OSM maps to query. Can't search for drinkable wells in Google Maps!
But then, it of course isn't Google Maps. It is likely to be more out of date and will not understand "natural" search queries as Google does. I believe it just takes some getting used to. There is overlap between the two, each service has its strengths and weaknesses, but also unique features.
Why not? On my home server, k3s (single-node master), sitting idle (no workload, no changes), has amassed as much CPU time as a full virtual machine running Home Assistant: 17.75 hours in 106 hours of uptime.
All those abstractions and cluster features do not come for free.
To each their own, of course, but: If you're within a 1-hour walking or cycling radius (and you have access to showers at your destination), this is no problem at all. Plus, the mental and physical health benefits are simply incredible.
Man if only there was a solution to this. It's almost as if we could design our environment to minimize this (bike- and pedestrian-friendly routes) and then deal with the aftermath if it happens anyway (showers).
I do not consider employers that do not offer showers.
It's great. It's complicated. I have a MacBook Pro Late 2013 – very old. NixOS runs totally great! Even the proprietary hardware just works, with the nixos-hardware channel. Battery life is awesome, 4 hours of office work.
There is a snag however: Drivers for the built-in Broadcom Wi-Fi card are unmaintained and bug-ridden. Replacements do not exist either. The driver doesn't work most of the time nowadays and I have to rely on a USB Wi-Fi adapter that is sooo slow.
Maybe more recent Wi-Fi chipsets in Intel Macs are better off. Or maybe you don't need Wi-Fi!
Arguably, this situation is already broken right now. If an organization can't be bothered to use their tools (Sharepoint and the wider O365 ecosystem) correctly, it's entirely on them.
That's what I feel. Whenever I see someone writing something to the effect of “LLMs will replace X” (where X could be literally anything including software developers) I get an intense urge to write something against it. Not something nice, mind you.
I also find takes from the anti-LLM to be exceedingly dumb at times. Oh this text has this and that, it must have been written by LLM and thus is not worth even considering.
Extremely unlikely. Automating Office (the desktop application suite) simply does not scale. It's not needed, either. Libraries exist that can extract information from Office documents (both legacy and OOXML) much faster. Many(!) orders of magnitude faster, in fact.
AI is entirely unrelated. This is simply yet another push to get more SaaS subscribers.
Yes, it can be sniffed. It will at least use transport encryption, like TLS. For everything, yes. So you'll only get encrypted data you cannot read. You could attempt a Man-in-the-middle attack on this connection. Unless the app is badly made, this will not succeed.
And then, even if you could look inside, there's another type of asymmetric cryptography going on: the remote attestation itself. Again, if properly designed and possibly backed by a hardware security chip, it cannot be spoofed. This isn't something trivial like a shared secret in an HTTP header.