the comparison does not make sense, steam is doing much more than launching games, including handling a whole windows compatibility layer through proton/wine.
I think I and lot of others lack a clear instruction how to use it and what are the limitations. With docker/containers we are sold the promise of sandbox (not true, but regardless), and with existing systemd user level separation is really hard to grasp.
We started turso way before vibe coding became a thing, king.
And these days we use AI, like most people, but still review all the code ourselves before it goes in.
Very disingenuous to call turso a vibe coded project.
1. I've looked at how Turso verifies the correctness of their db and I'm satisfied with it.
2. Turso supports features I want that don't exist and will not exist in sqlite.
I mean this is pretty obvious, I'm not using sqlite because it doesn't do what I want it to do. I also don't understand the repeated "sqlite is the best tested software" sentiment. I don't care if it's the best tested if it doesn't do what I want it to do.
this whole thing is a misunderstanding from legacy docker semantics. you can easily use namespaces in systemd as user in lighter ways, for example, keeping the rootfs but protecting home and binding a private tmpfs, or to bind a completely different rootfs, providing a vm-like experience. Please read the documentation before vibe coding; the name wsl for Linux just shows how lost you are.
> I see you are using Cadence IP in your project, unfortunately this is not allowed per the terms and conditions and you will be reported to the authorities
Also : create proprietary locked down eda->no data to train models->models suck at it->reach out to ai lab to rl on it -> expect users to pay for eda and the model.
... > I see you are using Cadence IP in your project, unfortunately this is not allowed per the terms and conditions and you will be reported to the authorities
EXACTLY, prepare to self deport immediately, push to execute
Also the other way around (Cadence shipping Synopsys IP). Big chips wind up with IP blocks from many sources and (at least usually) the right people get paid. And EDA engineers bounce around between Cadence, Synopsys, and Mentor (now Siemens EDA).