• 6 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: July 25th, 2023

help-circle
  • Analogue likely doesn’t emulate the hardware at the transistor level, as it’s far more difficult than doing what most software emulators do.

    From an interesting (altough non-conclusive) HN-thread [1].

    Without seeing the code, it’s impossible to know where Analog’s implementation falls on the spectrum of software emulation vs hardware simulation. There is nothing magical about FPGAs that automatically makes anything developed with them a 1:1 representation of real hardware. In fact, there are plenty of instances where the FPGA version of a particular console is literally just a representation of a popular emulator only in verilog/vhdl. In many instances, even the best FPGA implementations of some systems are still only simulating system level behavior. Off the top of my head, one famously difficult case is audio, where many chips have analog circuitry that cannot be fully simulated.

    [1] https://news.ycombinator.com/item?id=37901381




  • Nintendo didn’t put legal pressure on emulator devs for decades at this point, which made devs less cautious about preserving their pseudonymity.

    Now it’s too late and they can’t stop Nintendo from finding out who they are and which mistakes they did at some point over the years.

    Maybe a new generation of emulator developers will be more protective of their identity, by using hosting providers like Njalla or privacy networks like i2p. The latter would limit access (as it requires i2p), which isn’t desirable for most users.






  • I disagree with the notion that it’s better for the cheaters to have an easier time (and less chance of being detected), but you’re right, BattleEye doesn’t solve the cheating problem for GTA.

    Rockstar should fix their netcode and run game server on dedicated server, instead of their customers PC’s. I’d think decting aimbot isn’t the biggest issue, while cheaters are able to break entire lobbies…

    IMO no game should require client side anti cheat except for shooters, where looking through walls and aimbot is actually difficult to detect server side. At least for those is it possible to find valid arguments (except for being lazy).


  • tl;dr
    Read the first sentence after each citation ;D


    So Wayland, a protocol, is needing the addition of other protocols?

    Yes. What we know as Wayland is the Wayland core protocol and a few other protocols that are absolutely necessary for desktop use (stable).

    Then there is staging, which is not necessarily implemented by all compositors, e.g. fractional scaling.

    Unstable also exists, which is even easier to get a protocol into (idk the exact requirements, likely the amount of support and explicit dislike by contributors).
    These are often only used by a subset of compositors with e.g. XDG decoration allowing compositors to announce to clients (windows) that they support server side decorations (top bar with close/minimize/maximize buttons). This isn’t implemented by Gnome, but most other desktops support it.

    Different desktops also have their own protocols, which are published so that apps targeting those desktops can implement them. Some are also supported by other desktops, if they think they are suitable for them.
    E.g. wlr layer shell makes status bars possible, which are used by basic compositors like Sway or Wayfire. KDE also supports it, even though it was originally created by wlroots.

    Does this make it a Wayland Distro?

    In a way you could say that a compositor is a Wayland distro, as it implements a subset of Wayland protocols.

    In the end this is good, because it allows for rapid development and discontinuation of protocols. E.g. if a better protocol comes around, both protocols can be supported at the discretion of every compositor.

    The goal was to solve the problem of X11, where Xorg still has to support drawing UI by itself, even though no program or toolkit uses it anymore (the 80s were very different). The Wayland core is so minimal there shouldn’t be any issue with using it for a very long time.

    Also, Wayland was developed by people with the goal to use it in automotive and other industry applications, where basic desktop functionalities, like multiple windows or session lock, aren’t useful.








  • I believe the advantage is that old drivers still work as they are all in the kernel. With them sharing much code it’s not even that big of a disk space issue. Edit: A more dynamic approach would be great though, especially with this size issue popping up.

    In a way it’s great that I’m able to replace any part of my system and it just works without me having to make sure the old GPU driver doesn’t leave some traces behind–altough while writing this the latter part shouldn’t be an issue with Windows auto download and installation of drivers.




  • After using Fedora Atomic for around a year, I’ve switched my mom over from Linux Mint. Since then a few years’ve gone by and there’s been no issues with automatic updates failing or not applying. That’s awesome compared to regular issues with dpkg errors because of shutdown/power loss while updating.

    Obviously release upgrades still require manual intervention, but that’s an hour once a year for updating and testing if everything works as it should.

    Personally I’ve switched to NixOS, because even with ublue image-based OS aren’t great for configuring window managers. In general, image-based OS are especially awesome for long-running, low maintenance systems. I wouldn’t want to use an OS which doesn’t provide some kind of rollbacks anymore (btrfs snapshots is the minimum).

    Edit:

    Do you feel it’s worth it to learn the nuances of their use?

    Fedora Atomic is almost identical to regular Fedora, the difference is mostly how the root filesystem is managed:

    The former are files from rpms get copied to an ostree image, which then gets mounted as the root file system.

    For the latter dnf copies files from rpms to the root file system.

    […] did you manage to properly run AppImages […]

    They always worked flawlessly on everything except NixOS (because of no FHS-layout). Through distrobox they should work on any distro.

    […] trying to install Outline VPN […]).

    These kinds of not properly packaged apps are a big issue with ostree based systems. VPN provider apps need to be natively installed and usually aren’t available in repos.




  • This proves that AC Oddysey runs faster on Linux than on Windows with your specific hardware. What this doesn’t mean is that “Linux gaming is faster and smoother than Windows gaming”.

    Counter examples are Overwatch, CS:2, GTA V and many more.

    Nobody reasonable doubts that Linux can perform as good or better than Windows, but claiming that this is true for all games is simply misinformation.

    Wrong general claims like these lead to posts asking why their specific games run worse on Linux since they switched because they want more fps.

    Don’t get me started on older GPU’s like 1000 series Nvidia that have problems with any vkd3d games so the performance is abysmal.

    Why is it not enough that almost all games work on Linux with ±15% performance difference?