• 0 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle

  • Rosetta and proton are two completely different layers.

    Game porting toolkit is indeed also based on wine, but that’s only the conversion of directX to ogpl or vulkan (using metalVK in Apple’s case)

    Rosetta is a completely separate harware accelerated (as in, the chips have dedicated hardware for this) translation layer for x86 to ARM

    Given the lengths they had to go through to get even this custom APU, I can only imaging the difficulty in procuring a first-gen ARM offering from AMD.

    I swear, this is just the “VR is really here, and it’ll replace conventional gaming!” Debate all over again. I’d be surprised if it happens in the next two years. After that? Maybe, if x86 doesn’t catch up more than it already has (which I fully expect it to do).



  • Apple’s M-chips have dedicated hardware to accelerate rosetta 2 (support for x86 memory ordering), please stop using rosetta2 as a show of what x86 on ARM can do, as it is a vertically integrated piece of software that is not indicative of the current market for anyone outside of apple.

    Just take a look at windows on those new qualcomn chips - when they do the translation, the performance is underwhelming to say the least.

    Yes, it will improve, but it currently does not exist outside of Apple.



  • I looked into distros using plasma 6 for a bit, but decided it wasn’t worth the hassle. It’s also a not trivial boot setup (dual boot with w11 and bitlocker + LUKS + secureboot) and the (k)ubuntu installer just handled it flawlessly (meaning not having to enter my bitlocker key on every boot)

    Works fine for me (except some weird locale issue, but I knew that in advance)





  • Wireguard (which is what tailscale is built on) doesn’t even require you to open ports on both sides.

    Set up wireguard on a vps first, where it is accessible, then set it up from within your network. It’ll traverse NAT and everything, and you don’t have to open a port on your network.

    Tailscale is the exact same thing, just easier because it does everything for you (key generation, routing, …). Their service replaces your vps, up to you if you think that’s acceptable or not. IMHO, wireguard is worth learning at least. I eventually (partially) switched to tailscale because I’m lazy, and all services I host have authentication anyway, with vpn just being a second layer.


  • How? The sublinks devs started the project just because they didn’t want to work on Lemmy for whatever reason. If they did, they would have worked on Lemmy. It’s either Lemmy AND Sublinks, or Just Lemmy with the same developers.

    Having multiple implementations is a good thing, regardless of what language they use. They all implement the same protocol, should be (mostly) compatible, and can learn from (and compete with) each other.

    Look at other OSS. There’s so many Linux distributions, Why doesn’t everyone just work on a single one?

    Because everyone has a slightly different view on things. This makes the OSS community stronger.


  • I have seen people wanting to do Java, and while I personally prefer rust, I do see why.

    Outside of the entire Sublinks discussion, it’s important to note that Java is not just Java anymore either. Kotlin offers many of the same advantages syntax-wise that Rust does (including the lack of null), and has access to Java’s excellent ecosystem.

    Ultimately, it is up to people to decide what they want to use. Regarding of your opinions on Java or Rust, it is a valid choice either way for this type of software. It’s a personal choice.







  • I don’t think programming language is a good metric for security. I assume everything I host has issues, and then try to mitigate from there.

    IMHO, a better approach is to vet the project beforehand, looking at whether it is still actively maintained. I usually use things like commits, issues, etc to try and gauge whether a piece of software is actively maintained so that when an issue arises, it can be fixed.

    You can mitigate much of the risk by using some basic best practices, like isolating all apps from each other (using docker, for example), using a reverse proxy, tools like fail2ban or a web application firewall, using proper database permissions for each app, etc

    What I also do is add another layer by making certain applications accessible only over vpn. That won’t work for some tools, obviously, but also reduces the risk for tools you are only using yourself.