• 0 Posts
  • 185 Comments
Joined 1 year ago
cake
Cake day: July 29th, 2023

help-circle
  • They’re clearing out the scene before the switch 2 releases because they perceive the current emulators as a major threat somehow.

    Which I assume means that the new switch is similar enough in architecture that it would be relatively trivial to ship a fully functional emulator on hardware release.

    Pretty insane because at least in the USA, emulation is protected by law, except if someone can successfully argue that you are bypassing DRM which is illegal.

    In a working system, this wouldn’t be an issue but I imagine neither Yuzu nor Ryjunix would want to deal with Nintendo’s insane law team that could wreck them financially in a matter of days before even entering a court room.

    I hope someone either makes an anonymous dev team for a future project, or gets assistance from a consumer justice firm/group to properly argue in court to shut Nintendo down. They really should not be able to do this because it was already a thing 24 years ago:

    Sony Computer Entertainment v. Connectix Corporation, 203 F.3d 596 (2000), commonly referred to as simply Sony v. Connectix, is a decision by the Ninth Circuit Court of Appeals which ruled that the copying of a copyrighted BIOS software during the development of an emulator software does not constitute copyright infringement, but is covered by fair use. The court also ruled that Sony’s PlayStation trademark had not been tarnished by Connectix Corp.'s sale of its emulator software, the Virtual Game Station.


  • mlg@lemmy.worldtolinuxmemes@lemmy.worldNewbies never listen...
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    12 hours ago

    Our crappy vendor software will only function if IPv6 is disabled network wide. Even if one machine has it enabled, the whole thing breaks

    Lol our former crappy vendor solution required to be run directly from AD Administrator. Pure luck the entire business didn’t collapse before we replaced it.

    A thread I read a long time ago on r/sysadmin



  • After 15 years of wayland development hell, I’m honestly open to anything. Problem is I can definitely see an experimental branch being just as scrutinized. One of the core issues highlighted was that features and requests were rejected because of hypotheticals and the maintainers trying to avoid fragmentation like early Xorg.

    Basic features from X11 are still missing. Everyone ended up somewhat fragmenting anyway via compositors because weston wasn’t really useful for developers beyond a demo. Wayfire started out as a Compiz redux and now its being considered by several DEs like XFCE to be the default compositor which they should standardize around.

    Regardless, I really hope they nail it down in the next year because the halfway migration to wayland is seriously harming Linux desktop, especially when lots of frontend UI has been done perfectly decades ago on X11, and wayland still not properly supporting new features like HDR.



  • I’d support anything to see NIntendo get kicked in the nuts for shutting down yuzu, which could have easily continued legally by removing like 2 paragraphs and probably a few lines of code.

    Also Citra which was 100% legal.

    EDIT:

    I also wanna mention that current Pokemon gameplay sucks, and would also kill to see GameFreak’s billion dollar franchising burn. Maybe 15 20 years ago when hardware was “limited”, a low asset turn based RPG focused around pocket monsters was a fun game. Ain’t no way a PS1 graphics looking game with practically zero changes to the formula can be considered AAA title in 2024. And even then they’ve somehow made it into an A button press simulator by nuking the difficulty.

    Being completely honest, the DS hardware was not that limited (had 2 generations on it with significant upgrades despite being the same console). BW2 was probably the golden era with very well done animated sprites, overworld, features, etc. The moment it hit the 3DS, it started showing its cracks with GF continuing to develop the game without expanding the team to meet development demand.

    Palworld isn’t even the first challenger. TemTem gained some popularity purely for showing how much of an upgrade it was from Pokemon only a few years ago.


  • I’d say about 99% is the same.

    Two notable things that were different were:

    • Podman config file is different which I needed to edit where containers are stored since I have a dedicated location I want to use
    • The preferred method for running Nvidia GPUs in containers is CDI, which imo is much more concise than Docker’s Nvidia GPU device setup.

    The second one is also documented on the CUDA Container Toolkit site, and very easy to edit a compose file to use CDI instead.

    There’s also some small differences here and there like podman asking for a preferred remote source instead of defaulting to dockerhub.




  • Yeah I should have mentioned the context is FBLA, and Google partially fixed the prompt.

    Original from a few weeks ago:

    BPA is another student org called Business Professionals of America

    The AI ignores the subject context and just compares whatever is the most common acronym.

    They lazy patched it by making the model do a subject check on the result, but not on the prompt so it still comes back with the chemical lol.





  • In a different article, he said he had issues with the ext4 maintainer who was acting high and mighty about C despite being responsible for a number of huge CVEs from code that he wrote.

    That being said, I don’t really see the benefit of rewriting modules in Rust.

    Technically, it’s still not a 1:1 replacement because Rust will many times not generate the exact same machine code as C, which does result in a small loss of speed (and in some small cases, vice versa).

    It’s acceptable for anything new, but unless there’s a notoriously painful part of the kernel, there’s no pont in redoing existing parts and even core userspace binaries.

    C quite literally makes you manipulate memory like a caveman holding a machine gun, but that’s important because it’s exactly what the machine is doing, which is required when you need to maximize efficiency. In Rust, you’d have to abstract some of that to the compiler to handle your logic which doesn’t match what a machine is doing. There is no such thing as “borrowing” and “ownership” in machine code.


  • It’s not 90s tech though, especially for China.

    Their latest x86 CPU is comparable to Kaby Lake in cycle speed which is only 8 years old, except it comes with more cores and supports DDR5 so it might as well be a first gen ryzen 7.

    They still haven’t revealed how they fabricated it or what process they used, probably because they want to keep the production chain and size a secret.

    Enriching uranium and making nukes, in comparison, is banging rocks together.

    No it isn’t, especially for weapons grade Uranium. Look at Iran, they’ve been perpetually “10% away from a bomb” for more than 20 years and still haven’t succeeded.

    The ridiculously high precision required to make the centrifuges, and then the scale required to make hundreds of thousands of them per plant just to reach 20% enrichment is insane.

    Reaching 90% is like taking all that and ramping it up several hundred times.

    The only reason Pakistan succeeded was because they got (stole) the critical design parameters needed for the centrifuges to work, and a rather brilliant metallurgist who took several years to figure out how to manufacture the centrifuges consistently at scale. Plus an entire set of physicists just to figure out the centrifuge physics in a way that would allow them to maximize refinement with dozens of design variables. It still took them a decade, but they eventually got it.

    It’s a pretty good comparison to lithography machines which requires similar dead precision with each decreasing size of transistor requiring an order of magnitude more precision in quality engineering.

    Also I don’t think the US is involved in this, at least not directly:

    I doubt it because they’ve been making it a pretty big deal for the past 4 years. Tons of Chinese tech OEMs are blacklisted, and the trade war keeps escalating with new bans/tariffs/exclusions every year. Plus they dumped billions of dollars into intel and TSMC in a desperate attempt to make a fab on the home front.

    It doesn’t matter that it’s DUV, they just want to ensure they make it harder for China to catch up, so even last gen tech is on the line because they believe it can be studied and reverse engineered.

    imo it’s a stupid shortsighted policy, but it’s nothing new for the US pulling these types of moves. I just wish for once they’d see that it’ll only delay the inevitable, and maybe they should put that effort into actually making quality products at home instead of throwing money at chip OEMs and expecting them to move out of Taiwan overnight.


  • People here (including the US govt apparently) acting like it’s actually going to take China a decade to figure out how to run a wafer machine bruh.

    Not only do they probably already have the procedures written down and kept safe, they’ve been already been experimenting with having to run the entire supply chain on their own for years now. Hell they’re even the ones basically carrying RISC-V development right now because they barely have OEM access to x86.

    And that’s all without the assumption that China hasn’t stolen some key trade secrets that would give them a head start. I highly doubt this equipment will actually go offline besides some practice runs and research application which they have likely already done without telling anyone.

    Pakistan’s entire nuclear arsenal only exists because one talented due working at URENCO (also coincidentally Dutch like ASML) took a few hundred documents and his years of work experience back to his home country. If broke ass Pakistan could figure out how to make fissile material and nukes in their backyard, China sure as hell gonna figure out how to fabricate chips without any external suppliers or contractors.