If you want to do the same thing, build a cluster of complete machines, in a ligh-weight manner, just for the learning experience, you can use incus to create containers in the same manner.
As they are all complete machines and you bridge them, you get DHCP allocation identical to running a little PC on the local LAN. If you have ssh set up in the image, as described, you can run the identical scripts.
As a plus, if you run them on ZFS with de-dup, even the disk cost for new machines is miniscule.
.. and in 1mS it travels 300km. Maybe they just want to sound technical, somewhat to match the rest of the article. They certainly didn't use chat gpt, so maybe that's a good thing.
If you want vi history editing like you are used to in bash for the last 20 years it's subtly different in a manner that makes it insanity inducing. If you use the traditional emacs like editing it's much the same.
I never had ansible scale through more than 100 servers. Its design assumes things will mostly work. Above a few hundred servers, things will fail all day every day.
Whereas I have seen salt easily manage 6000+ servers.
I sure hope this is better than pathetically useless. I assume it is to replace the extremely frustrating Gemini for Android. If I have a bluetooth headset and I try "play music on Spotify" it fails about half the time. Even with youtube music. I could not believe it was so bad so I just sat at my desk with the helmet on and tried it over and over. It seems to recognise the speech but simply fails to do anything. Brand new Pixel 10. The old speech recognition system was way dumber but it actually worked.
I was riding my motorcycle the other day, and asked my helmet to "call <friend>." Gemini infuriatingly replied "I cannot directly make calls for you. Is there something else I can help you with?" This absolutely used to work.
Reminds me of an anecdote where Amazon invested howevermany personlives in building AI for Alexa, only to discover that alarms, music, and weather make up the large majority of things people actually use smart speakers for. They're making these things worse at their main jobs so they can sell the sizzle of AI to investors.
Yes, I am also talking about a Cardo. If it didn't used to work near 100% of the time this time last year it might not be so incredibly annoying, but to go from working to complete crap with no choice to be able to go back to the working system is bad.
It's like google staff are saying "If it means promotion, we don't give a shit about users".
I remember trying "call <my wife's name as in my contacts>" a few years ago and Google Assistant cheerfully responding with "calling <first Google search hit with the same name>, doctor". I couldn't believe it, but back then, instead of searching my contact list, it searched the web and called the first phone number it found. A few years later (but still pre-Gemini), I tried again and it worked as expected. Now, some time ago, post-Gemini, it refused to make a call. This is basically the first most obvious kind of voice command that comes to mind when wondering what you can do with the assistant on your phone and it's still (again?) not working after years of voice assistant development. Astonishing.
A probability distribution describes how likely different outcomes are.
It requires multiple observations or an assumed model that can represent variability.
This another reason why COM and CORBA failed. A whole lot of people telling everyone else the way they are doing it is all wrong and their 'proper' way is the only way. Maybe proto became popular because google didn't actually care that much. I remember the ACE/Tao people who did a lot of work around CORBA. They did good stuff but such painful religious fervor vibed everyone out.
Honestly I've been loving systemd-nspawn using mkosi to build containers, distroless ones too at that where sensible. Works a treat for building vms too.
Scales wonderfully, fine grained permissions and configuration are exactly how you'd hope coming from systemd services. I appreciate it leverages various linux-isms like btrfs snapshots for faster read only or ephemeral containers.
People still by large have this weird assumption that you can only do OS containers with nspawn, never too sure where that idea came from.
As a motorcyclist myself, I always felt drivers should be forced to do a certain number of hours on a motorcycle to make them more aware. But, those atrocious drivers would probably get injured so quickly that the idea would never fly. Now they are just driving.
As a plus, if you run them on ZFS with de-dup, even the disk cost for new machines is miniscule.
reply