• 0 Posts
  • 15 Comments
Joined 14 days ago
cake
Cake day: August 17th, 2025

help-circle

  • I’ve worked in the video game industry for a couple years and have been credited in several games. This number may actually be higher.

    It may sound crazy, but there’s a lot of people working on AAA games, usually most of them completely unrelated to game dev. Marketing, public relations, translators, 3D graphics artists, sound designers, orchestra performers, motion capture stuntmen, voice actors. Probably a few dozen managers, who have never even seen the game. Hell, some companies even credit IT staff in the game’s credits.

    That’s already a whole bunch of teams. It’s also important to mention that many third-party contractors will often be skipped from the credits. QA is very commonly outsourced (to poorer countries like Romania or Serbia) and rarely gets into the credits. You may only see 5-10 names, while in reality it was at least 100. This is true for several other fields, though mostly non-game-related, e.g., localization, promotial material, merchandise.

    I won’t disclose in what capacity, but in the past I have worked on several of Blizzard’s titles for a few months and I’m not credited anywhere. Just like at least a couple hundred other people. Not necessarily saying I should be - it was never mentioned or promised. Just highlighting that the real number of staff that worked on the game (or adjacent to the game) may be above 10k.


  • Some things are - on purpose - made easy to misuse and - by design - accessible to people, who are likely to misuse them. All this money, this supposedly cutting edge technology, and reporting to the police, but they aren’t able to tell when a child is at risk and report it as well?

    Smells like bullshit to me. More like they don’t care. I’m not so sure children should even be allowed to use chatbots in the first place. Or only allowed to use versions specifically trained for interactions with children. But of course - banning children from accessing youtube and wikipedia is a much more pressing concern.


  • Hey everyone! As many have noticed, the PinePhone Pro is currently out ot stock on the Pine Store. Unfortunately we have to deliver you the following news: the PinePhone Pro is officially discontinued. We were told it didn’t sell well enough to keep production going. But the good news for current owners are that spare parts will still be made for up to two years, depending on demand. Meanwhile, the trusty PinePhone (A64) is still alive and kicking, and Pine Store plans to keep it rolling for about two more years.

    Well, that sucks. So I guess the better move here would be to wait for something new? I don’t think the regular PinePhone is at all viable as a daily driver.




  • I’m a huge fan of Pine64, but I wouldn’t expect the PinePhone to be a great replacement for an Android smartphone. Personally I have quite extensive experience with PineBook Pro, PineTime and PineBuds Pro. I haven’t had the chance to try the PinePhone, but I’d definitely go for the Pro.

    Even then, prepare for a junky experience and forget about lixuries such as good camera, nice screen, smooth UI/UX. Their devices are great, and the ideas behind them more so. But unfortunately they rarely work well, perhaps with the exception of PineBuds Pro.


  • As of right now, it’s looking like GrapheneOS will be unaffected, and Google has yet to lock down the bootloader. So this should remain a valid option for at least 2 years.

    Other than that:

    • Any smartphones with an unlocked bootloader + any ROMs without gapps
    • Chinese smartphones with non-Google Android builds
    • Linux smartphones
    • Bonus: Huawei is about to release their own non-Android OS, but I wouldn’t expect it to be privacy-friendly

    Honestly there probably isn’t any good, long-term solution. Personally I’m somewhat shocked we’ve gone this many years with reasonably open smartphones. Next step is probably closing bootloaders in new laptops, as part of the switch to ARM (which is already undergoing).



  • Two things especially worth noting from the article.

    If you have a non-Google build of Android on your phone, none of this applies.

    This means that at least GrapheneOS will be unaffected for now. Other ROMs without gapps will be unaffected only as long as you don’t install gapps. Since Graphene has a sandbox for them, I’m assuming it’ll be fine. That is, unless Google decides to lock the bootloader entirely.

    In September 2026, Google plans to launch this feature in Brazil, Indonesia, Singapore, and Thailand. The next step is still hazy, but Google is targeting 2027 to expand the verification requirements globally.

    So most users worldwide still have at least 1.5 years until it’s implemented. Plenty of time to get a Pixel and install Graphene on it. Or to figure out some other plan.

    Don’t get me wrong - this is insane, unreasonable and horrible news for everyone. We should push back as hard as physically possible against it. However, at the very least we still have some time to figure things out before the policy rolls out.


  • You’re also massively wrong about DirectX on Linux, DXVK and VKD3D both work to run various versions of it on Linux.

    I very clearly wrote that Linux does not support DirectX. Which is 100% true, no matter how you look at it. Just because there are translation layers, it doesn’t mean Linux ‘supports DirectX’, because it doesn’t. It supports Vulkan, which DXVK and VKD3D translate DirectX API calls to.

    Let’s say you can’t read Spanish, but you hire a translator to translate a text for you. Now you can read it. Does that mean you can suddenly read Spanish?


  • They created the Game Porting Toolkit a while ago

    Hmm… Must have missed that. I’ll need to take a look. Might be the exact same thing I mentioned and I just had no idea it was already released.

    The RaspberryPi has existed for ~15 years at this point, the platform is far more mature than Windows on ARM and rivals macOS for support.

    I wrote “From my experience” and “Might depend on the device though.” Also, RaspberryPi is not a daily use device. At least not for the vast majority of people.

    If Linux works on ARM for other people - great. I’m hoping to be able to switch to it sometime in the near future. However, the last time I tried it was horrendous. A lot of programs I use were completely unavailable, with no compatibility layer that I know of. That was about 2 years ago.

    That said, I also tried Windows 11 on ARM around the same time and it was great. Practically everything worked out of the box and worked flawlessly. It was basically the same experience as on amd64.


  • After introducing Metal (their own proprietary graphics api), Apple killed OpenGL support and never implemented Vulkan support. Almost every single video game nowadays uses either DirectX (Microsoft’s proprietary API) or Vulkan for 3D graphics. 2D games use OpenGL and Vulkan. OpenGL and Vulkan are both open source and cross platform.

    Windows supports everything, Linux everything except DirectX, and MacOS (for Apple Silicon devices) only supports Metal. You can still play OpenGL games on Intel-based Macs. Steam tells you which games won’t work on recent Mac systems.

    In order for a game to run on ARM Macs, it has to either be ported to Metal, or there needs to be a compatibility layer like Wine and Proton. However, neither of these two work, since Apple no longer supports OpenGL or Vulkan. Theoretically, it is possible for people to write a new compatibility layer, specifically for Metal. The problem is, nobody wants to, because it’s a lot of work (as usual with development for Apple devices), and you never know when Apple may decide to drop support for some other libraries/APIs/drivers.

    Additionally, Apple seems to be working on their own Metal translation layer. Leaks show impressive performance in Cyberpunk 2077. However, nobody knows what the availability will be like or when it releases.