Hey Home-labbers/ self hosters.

This weekend my 10 year old processing machine finally bit the dust (RIP 🗿 💀 ; old system76 laptop, won’t even post, not the topic of this thread but if you’ve got ideas, I’m all ears), and as part of figuring out what happened and coming to the realization its time for a new machine. And as part of getting/ pricing a new machine (not looking forward to the consequences of the RAM-pocalypse), I’ve been reviewing/ thinking about the “structure” of what we as a household currently use our self-hosted/ home-labbed system for.

Myself and my partner are researchers, and as such, we regularly collaborate/ work together on manuscripts, and the reality is, we rely on windows because we’re also collaborating with other authors who also rely on MS word to write in. Now I’m a 100% FOSS advocate, but this is a sticking point my partner has had, and I agree with them, at least in practice that realistically, we need a windows machine laying around specifically for this one, particular use case.

Now my thinking here is to use proxmox to spin up a windows machine as a VM, something we can remote into. Is there any best practice for something like this? How would this work with licensing? I personally haven’t installed windows on something since like windows 7, and I know they’ve enshittified beyond recognition.

I personally don’t want windows on my machines. But realistically, I recognize its necessity for this one particular use case. Thoughts?

  • Decronym@lemmy.decronym.xyzB
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    22 minutes ago

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

    Fewer Letters More Letters
    Git Popular version control system, primarily for code
    NAS Network-Attached Storage
    VPN Virtual Private Network

    [Thread #56 for this comm, first seen 2nd Feb 2026, 21:20] [FAQ] [Full list] [Contact] [Source code]