My bad, i am not a native English speaker... I did my best to try and brush it up. Terribly sorry if it did not match your flow.

▲

jchw 3 hours ago | parent | next [-]

LLMs are pretty good at translation, they're just pretty awful at generating natural-sounding English prose from scratch. In my opinion, probably the best solution is to simply write the README in your native tongue and use an LLM to translate it.

	▲	junon 6 minutes ago \| parent [-]
		This! Claude word salad is worse than maybe subpar translations, with which I'm sure PRs can help.

▲

mcmatterson 4 hours ago | parent | prev [-]

All good friend! I'm as guilty as anyone. It's a super cool project though.

Now that I have you on the hook, is there any benefit to this over virtio for a single KVM passthrough situation? I previously ran a proxmox based gaming PC setup (docs here: https://github.com/mtrudel/rabble/tree/4d9329f3dd0fb09123a8f...), and was lucky enough that the GPU passthrough part of that build 'just worked'. I'd started down a path of trying to share the GPU between VMs based on a naive 'one VM owns it at a time' setup, but never really got it off the ground.

	▲	WanjohiRyan 4 hours ago \| parent [-]
		The benefit is that you do not have a limit to how many VMs you can run at the same time. However, virtio-nvgpu has no Windows support as of yet, please check back in a while :) You should check out Nestri [1], another project we are working on, that helps you do exactly that. It helps run multiple gaming sessions for you and your friends on the same GPU, without anyone meddling in the other person's session. Everyone gets to stream their game to whatever desktop or device they want. It is still a work-in-progress though. [1] https://github.com/nestrilabs/nestri