Skip Navigation

Posts
2
Comments
1177
Joined
3 yr. ago

  • In a decade or two, they will be electric and there won't be a carburetor. It will all be more like that parking system. The moment software comes in, much easier to lock people in. That needs to not be the case. It's always made out that somehow working on software of these things is dangerous, but somehow working on a mechanical machine of controlled explosions of flammable liquid is not. Most people are just going to flash on firmware someone else did.

  • Surely repairable doesn't mean no tech, just open tech. I'm sure there is tech features that are worth having. It's the vendor lockin and enshitification that isn't.

  • The return of the fat client in the age of AI mainframes? Nvidia is selling shovels in the AI gold rush, so they don't care either way.

  • I don't think you can be pro copyleft and pro-today's-LLMs, which are used to wash away copyleft. Copyleft and LLM poison the code and downstream developers have to play nice.

  • Guessing you don't like GPL either. Restricting those developers down stream of you.

  • Exactly. Right now it is the mainframe era and the billionaire monopolies want it that way. However that is a future not one but them wants. Little tech rebel alliance is the way to go. I'm not interested in big tech's imperial AI.

  • If they are commiting code they don't understand, this is but one of the issues they are going to get hit by. They can't blame the AI, the buck stops with them.

  • It won't go away, but LLM won't always mean automated-cargo-cult-programming, digital serfdom, climate apocalypse and a financial speculation bubble. At some point, their cost will have to be their actual cost. Bigtech hope is many will be so hopelessly dependent at that point, that they will pay that cost. Also that there is little competition because few can run at those losses.

    But I think at that point, efficient small language models you can own/host, train and use at will, will be a thing. No one wants to be (American) bigtech serfs.

  • I've done a thing with Kamailio and Baresip and MQTT and Linphone on my phone so when someone presses the door bell button, I get a video SIP call from "doorbell". But other I think are doing things with HomeAssistant, go2rtc and Frigate. I just didn't like it so went my own way. Would love to have done my own Signal client that wrapped RTSP, but it wouldn't be allowed on the Signal network, but Linphone is ok. Video SIP is standard at least.

  • Humans are going to be the weak point of any system.

    I was thinking this about getting off America servers and services. More a question of digital sovereignty security. But it is all do with hacking via humans by pretending to be support staff.

  • Is this to help them burn cash on AI a bit longer? That's how I'm taking it.

  • Containers are often used as a way to not have to keep things up to date, or install properly. Don't have to be, but often are. Also, not have a separate kernel means you aren't protected from things like the recent exploits when you allow things uploaded to run. Maintaining Debian Stable is easy really. Love me some Debian. 😀

  • I don't like GC languages. Things written in them often seam to be written like they are the only thing that matter on a system. Thus don't play well with each other in regards to memory consumption. Memory is not an all you can eat and clean up later. Yes there are environment variables you can use to enforce better behaviour, but that's a fail. Rewrites into Rust seam to solve this, but I know reason is really that Rust is the new cool thing and programmers like rewrite things, but I'll take the win.

    Also, I don't like static linking. It doesn't scale. When a library has a vulnerability, it means everything needs rebuilding. It also means you have lots of duplicates of those libs at different versions. It's a mess I hoped had died of decades ago.

    Also, I don't like languages each having their own half maintained package manager that is their language only. Just put in the work and get into root distros like Debian, Fedora, etc. Maintain a stable version you back port security fixes to. Only trustworthy packages get in. All languages under one roof.

    Also, I don't like languages that orbit an American tech monopoly.

    Also, I think Go is failure and in legacy mode and largely replaced by Rust.

    Basically, Go often makes me grumpy. ForgeJo is an exception. I also like a lot of what Codeberg say and do.

    It triggers me with things I also didn't like in other things of the past.

  • It's so easy, why bother? But I have each service in a separate small Debian VM to avoid conflicts. This avoids conflicts, enforces limits, and gives kernel separation. The real kernel isn't running anything public.

  • ForgeJo is pretty nice.

    I mean it's Go and not package managed properly in distros, but as a services to run it's nice.

  • Exactly, consumer choice only works as a force in a functional market. Phone OSs are very much not a functional market. This requires regulators to wake up.

  • Humans and still humans, but red vs blue is the worse setup. All debates just become which team you are for.

  • No, the US needs to move past Red vs Blue "democracy" to something multi party and with constant coalitions and compromises. Then hopefully grown ups will run the US. Two parties is a democratic failure.

  • Selfhosted @lemmy.world

  • Privacy @lemmy.ml

    Boxing Android