[–] 5 points 2 weeks ago* (last edited 2 weeks ago) (3 children)

It's still unclear where the "Raven’s guest components or libraries" come from.. which I think it's the question that was being asked (given that wine is a reimplementation of the Windows components).

EDIT: apparently they are using ReactOS implementation of the Windows kernel & system libraries to translate the system calls, and beyond that they use the official Microsoft libraries that need to be installed inside the Raven runtime, like you would install in ReactOS.

EDIT2: Also apparently there's some controversy going on because ReactOS is GPL but Raven is getting distributed as MIT, so there's a bit of a mix of licenses which opened a bit of a debate.

  • source
  • parent
  • context
  • [–] 9 points 2 weeks ago (4 children)

    From the site:

    How does it work?

    A virtual machine boots a guest operating system. Compatibility runtimes such as Wine instead implement the Windows interfaces an application needs.

    Raven runs the .exe directly on the CPU in a supervised guest process. Some Windows functions execute inside that process, in Raven's guest components or libraries. Requests for supervisor-managed services cross into the runtime outside it, which manages processes, handles, files and registry state and mediates access to the Linux host.

    Raven implements Windows Installer custom actions, side-by-side assemblies through WinSxS and a service manager. These are among the interfaces real installers depend on; application compatibility still needs testing.

    The official redistributables can be installed with their classic installers, like you would on Windows (Visual C++ 2005 to 2022, DirectX, .NET Framework 3.5 and 4.8, XNA and OpenAL). Raven protects its own system libraries during installation. Snapshot creation can fail, so check that a checkpoint exists before relying on rollback. Tested applications can use the vendor's installer; other applications may still fail to install or start.

    Graphics go straight to Wayland and Vulkan, with DXVK and vkd3d-proton for Direct3D.

  • source
  • parent
  • context
  • [–] -5 points 2 weeks ago (6 children)

    Ive never opened a thread on lemmy and seen anyone not hate whatever the thread is about. Everyone here just seemingly hates everything and its always everyone elses fault about why people dont leave reddit for here…

  • source
  • [–] 27 points 2 weeks ago* (last edited 2 weeks ago) (6 children)

    How is this different than what wine does though? Looks like it implements the windows apis, just like wine. It was originally implemented in go, with a C++ rewrite started July 31st the original go implementation was removed three days ago .

    By all means, wine is a huge project, probably with a lot of baggage. I'm not pro AI, but I guess translating between apis could be something language models could be good at. Looks pretty sloppy though.

    Edit: based on some twitter posts by the author, looks like the conceptual approach is an NT kernel shim running in user space rather than translating api calls directly. gVisor was mentioned as doing something similar

  • source
  • [–] 2 points 2 weeks ago (5 children)

    Is this similar to Bottles in being a front-end for WINE, a fork of WINE itself, or independent program similar to WINE? No matter which, I will have to keep it in mind for future random needs for Windows programs.

  • source
  • [–] 4 points 2 weeks ago

    Sounds like sort of a hybrid between a VM and WINE where programs get access to a real Windows kernel. Sounds promising and it’ll be interesting to see how this turns out.

  • source
  • [–] 6 points 2 weeks ago

    Yeah this tracks for the Danish government. So I found the original press release from back in 2025 and I've sent them an email asking wtf is going on. They had 38 press releases for all of 2025, and for 2026 there's been just 4 total, and the year is almost over.
    Not sure what is going on, except that we (Denmark) had a election year and it took 69 (nice) days to form a government, and that might've influenced how things are run there. It is funny though because our new government is slightly more left-leaning this time around, at least on paper, so one would think they'd be more interested in moving away from Microsoft.

  • source
  • [–] 3 points 2 weeks ago

    I have it on all my home networking equipment, my router and my APs, and a wifi bridge for my SBCs. My experience has been that it is just as simple as the proprietary firmware, and more robust. The catch is that I chose each piece of equipment knowing that I would flash custom firmware onto it, so they were ones the OWRT wiki showed as being simple to flash.

    Which model TP-Link are you going with? The page for whichever model on the OpenWRT wiki should tell you whether it's easy or difficult to flash and revert

  • source
  • view more: ‹ prev next ›