• Skull giverA
    link
    211 days ago

    Messing with 18650s is rather risky, I’m not sure if exposing them as individual cells is a good idea. I hope the company is smart enough to put a “if you burn your house down replacing the batteries, we’re only liable if we sent you the replacement” clause in their sales contract or they’ll be sued into the ground if this thing ever takes off.

    As for ARM+games: with tools like Box64 you can get some impressive performance out of 3D games assuming your GPU is supported. The native code of the game will be running translated, but the expensive calls to 3D engines and such will all be caught and replaced by native ARM libraries. I doubt you’ll be running Cyberpunk on this thing, but don’t count it out just because of the translation step.

    • @tal@lemmy.today
      link
      fedilink
      English
      3
      edit-2
      11 days ago

      Messing with 18650s is rather risky, I’m not sure if exposing them as individual cells is a good idea.

      I mean, there are plenty of devices with them out there. !flashlight@lemmy.world seems to only really be interested in lithium-battery-driven flashlights. I don’t think that an 18650 is intrinsically unsafe.

      My understanding is that you can get (slightly cheaper) unregulated cells, but that normally, for end users, one uses regulated cells. The electronics on each cell aren’t smart enough to do things like measure and report charged capacity, but they should be adequate to avoid fires if the battery is shorted.

      And there’s no standard for a “smarter” battery pack that would do things like report more information.

      The native code of the game will be running translated, but the expensive calls to 3D engines and such will all be caught and replaced by native ARM libraries.

      Yeah, that’s true – some games are going to be GPU-constrained, and the instruction set isn’t gonna be a factor there.

      A significant chunk of what I’m getting at, though, is battery life. Like, my understanding is that Apple’s got somewhat-better compute-per-watt-hour ratings on their ARM laptops than x86 laptops do. But having that is contingent on one running native ARM software, not running emulated x86 software. Apple can say “we’re just gonna break compatibility”, and put down enormous pressure on app vendors to do so because they own the whole ecosystem. They have done multiple instruction set switches across architectures (680x0 to PowerPC to x86 to ARM) and that ability to force switches is something that they clearly feel is important to leverage.

      For people who are only gonna run open-source Linux software – and this thing is shipping with Debian, which has a native ARM distribution – then it is possible that you can do this, because for open-source software, you can recompile against a new target architecture.

      But Windows can’t do this, because there’s a huge amount of binary software that will never be retargeted for ARM. You’re going to be burning up your battery life in translation overhead. And you can’t do it with Linux if you want to run binary-only software – often Windows software – which is what Steam distributes. That library of software is just never gonna be translated; some of it probably doesn’t even have the source around anywhere. I don’t even know if Steam in 2024 has a native way to distribute ARM binaries (though I assume that one could have the game handle the target and running appropriate code).

      • Skull giverA
        link
        English
        310 days ago

        I don’t think regulated 18650 cells is a problem, but most users don’t know the difference. With every other laptop, you can pop out a battery and replace it with a model with the same part number, but with 18650 cells that’s a lot harder to accomplish. I’d rather see them “package” a bunch of 18650 cells together with its own part number and lets the people who know how batteries work figure out how to add their own cells (anyone with background knowledge will recognise the pack configuration the moment they take out the screws!)

        I don’t know about M4, but with the M3 Apple’s compute-per-watt was already behind some AMD and Intel chips (if you buy hardware from the same business segment, no budget i3 is beating a Macbook any time soon). The problem with AMD and Intel is that they deliver better performance, at the cost of a higher minimum power draw. Apple’s chips can go down to something ridiculous like 1W power consumption, while the competition is at a multiple of that unless you put the chips to sleep. When it comes to amd64 software, their chips are fast enough for most use cases, but they’re nowhere close to native.

        A lot of Windows programs run on .NET, which is architecture independent, especially if they target UWP (which is more common than you might realise). The remaining applications will need porting to get decent performance, but the most important applications (browsers and Office) already work.

        Re: Windows: Windows on ARM already has a binary translator, developed in part by Qualcom, that comes pretty close to Apple’s Rosetta2 for many types of software. It’s not as complete as qemu-static is, though it is faster for the software it does support. The worst part of the translation layer is that the ARM chips made by Apple’s competitors just aren’t very fast in comparison.

        I believe Steam can distribute different binaries (there were games with x86 and amd64 binaries for a while!), but until ARM laptops with decent GPUs start coming along, I don’t expect any game devs to use features like that. Still, apparently current ARM devices can hit 50-60fps with current gen devices already, and the upcoming Snapdragon chips are supposed to compete with Apple’s CPU, so who knows!

        Microsoft already tried (and failed) to make Windows on ARM a thing before with the Surface RT. I hope they don’t go all Windows 8 over their current attempt…

        • @tal@lemmy.today
          link
          fedilink
          English
          110 days ago

          I don’t know about M4, but with the M3 Apple’s compute-per-watt was already behind some AMD and Intel chips (if you buy hardware from the same business segment, no budget i3 is beating a Macbook any time soon). The problem with AMD and Intel is that they deliver better performance, at the cost of a higher minimum power draw. Apple’s chips can go down to something ridiculous like 1W power consumption, while the competition is at a multiple of that unless you put the chips to sleep. When it comes to amd64 software, their chips are fast enough for most use cases, but they’re nowhere close to native.

          Oh, that’s interesting, thanks. I may be a year or two out-of-date. I believe I was looking at M2 hardware.