tucosan

Sure there is. Containers and VMs. That's how you properly isolate ai workloads.

This thread was highly entertaining. Thank you two for arguing the topic and special thanks goes out to pandanman for his patience and composure. I guess I just found my next rabbit hole to investigate.

I'm sorry, but that's utter bullshit. The EU project was and is a significant growth motor for the member states. That's why even Canada is contemplating to become part of the union. But yes, bureaucracy and bad implementation of useful regulation a real issue.

That's the very reason I vibed my own daemon. I don't want the Logitech binary blob on my system. It needs too many permissions, it's huge, hogs memory and telemetry built in.

My vibe coded daemon is just a few hundred LOC of go code I can inspect, modify and trust.

Lol. I did exactly the same thing. Small go app. .02 CPU utilization.

I just built my own version to scratch my own itch.

Completely vibe coded. It solves my problem. I didn't even consider that someone else might have already built it. It's fast, simple, needs barely any resources. It has a daemon, it can detect new mice. It even has a vibe coded logo. Oh, did I already mention that the whole thing is completely vibe coded?

Flipped the repo to public in case someone else might find it useful.

But I won't go so far and advertise it.

I love it. I loved my pebbles. The only thing that always annoyed me was the design.

My dream is that pebble eventually becomes a beautiful time piece. Maybe teenage engineering could be convinced to give the pebble a design refresh.

Cool. In the meantime Google Assistant still fails to reliably call my contacts via voice command. And trying to use Google's AI offering as a paying customer of Google apps for work is a giant shitshow. So much so that I'm finally contemplating of dropping the Google ecosystem all together.

How do they know the study participants consumed honey and not corn syrup?

The developer time required to learn and properly use nix makes it unattractive to most teams. The benefits don't outweigh the costs of adoption.

Instead of debugging code, the team would have to spend significant time maintaining the build system for the build systems sake. Don't get me wrong, I want something nix-like in my toolbox. I want to love nix. But I wouldn't dare to argue my team to commit to the world of pain that comes with it.

There's a good reason that nix didn't see wide adoption in the industry.

Why are you happier exactly?

If you don't need the pinouts, it's likely cheaper to get a used thin client or a N100 based machine. You'd get similar power draw, plus a case and a PSU.

How does it mitigate the issues outlined in the article?

Banks in Germany offer access to consumers via the HBCI standard. Not sure about the rest of the EU.