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.
If you want to write new code and have a lot of influence over the overall implementation instead of fixing bugs on a years old steaming pile of tech debt.
Not all places with large existing codebases are that bad, but if you are experienced, it can be very personally satisfying doing something well before it has degraded over time.
I have worked in quite a few. One is a household name down here in Australia. I was the first engineer with the two founders. I worked 2 years 24/7 for half the salary I got when I left. I'll never get my money back but that's ok as I loved the time there.
I just have some IR LEDs on an esp8266 in the same room as my Daikin and run tasmota. It works perfectly. I have temp control and fully remote automation.
This is what I did to control an DeLonghi electric oil radiator in my home office. And since it takes a couple hours to warm up, I have it connected to Home Assistant to turn on a couple hours before my workday starts - and also sync'd to my work calendar so it doesn't do it on days I'm not working. And then turn off again at the end of the day.
Ended up setting it up as a virtual thermostat along with a Zigbee temperature sensor and letting HA manage the the whole thing. After a few months of hacking and tweaking, it works pretty well!
But, there were a few problems with this approach:
* The IR code to turn on and turn off were the same code (which makes sense if you look at the unit, there's just an on-off toggle button)
* No temperature control. On the heater itself, you can adjust the temperature as well as a high/medium/low setting. The remote didn't have these settings, so I couldn't capture them using an IR receiver sensor. Thankfully, these settings persist when the unit is off so I just set them once and called it good enough. And I eventually got around the need for this by setting up the virtual thermostat with a Zigbee temperature sensor in the room.
But the biggest problem is that I had no way to know if the unit was actually ON.
The codes sometimes wouldn't work unless the IR blaster was pointed directly at the unit, and even then they will sometimes randomly fail. I ended up plugging it into a Zigbee plug with power monitoring, so I could tell from the power draw if it was on, and try to re-send the commands a few times if it failed to turn on.
Overall, it was kind of a fun way to make a dumb device smart, but what OOP is doing is way cooler.
Home Assistant supports a variety of plug-in watt meters. I have some smart plugs that have a current meter built in, you wouldn't need to use the On/Off of the plug, just have Home Assistant read the current power consumption value and branch your logic from there.
I have one of those little Xiaomi LCD temperature meters in the room as well.
I actually have more than one LED on my device. It's in the opposite corner and points to the air-conditioning unit that is fixed. In this scenario I can't ever recall it not working 100%.
My automation is in nodered and I heat or cool the bedroom to 18C and turn the the unit off.
I tried that but the IR LEDs were too directional. In the end I got a little $7 device off Ali that connects to the Tuya API. The API works passably well (I'd rather connect directly, but eh), but the hardware is great, it works from any position in the room, even without line of sight.
I've done the same for an AC that wasn't supported by IRDB at the time. Just went through recording every possible combination, was a boring 30 minutes but it's worked perfectly ever since.
Just adding, this is completely the opposite to what the original blogspam article says. I think the references to the "Poisoned Chalice", should be updated to replace Macbeth with KX. The promise, (and delivery) of a hyper efficient way to analyse data that kdb/q gives you will always lead to final regret.
reply