Off-and-on trying out an account over at @tal@oleo.cafe due to scraping bots bogging down lemmy.today to the point of near-unusability.

  • 38 Posts
  • 1.72K Comments
Joined 3 years ago
cake
Cake day: October 4th, 2023

help-circle

  • In the indirect sense that an engine might impact a game’s visual appearance, hardware compatibility, or performance, sure. But I don’t care about the engine specifically as an engine. That’s just an implementation detail. It’s just “does the game look appealing” or “does the game run well on my hardware”?

    There are some cases where I can look at an engine and know that it’s very likely that some feature that I want is or isn’t there. For example, the (open-source) Twine engine supports interactive fiction multiple-choice Web-based games, usually written in a language called Sugarcube.

    There’s a similar proprietary engine and language, Choicescript, which runs in a proprietary viewer. This is used by Choice of Games LLC, which has published a large number of commercial text-based games.

    The developers of the Choicescript engine decided that an “undo/go back/save” feature would be undesirable, probably because it reduced the gravity of a player making choices; they basically require a player to play the game in “ironman mode”, where if anything happens that the player doesn’t like, the player has to go back and play a new game from scratch to avoid it. The Twine developers decided that “undo/go back/save” was a good idea and enabled it by default (and even if a game disables it, there are typically ways to modify a Twine game to re-enable this feature). I very strongly disagree with “undo” being disabled; I feel that it’s not respectful of my time, so when I purchase a Choicescript game, I know that I’m probably going to have to live with this particular decision that I do not like.








  • Every time I get an Android update, my first reaction is “what workflows that had been working am I going to need to relearn?”

    I’ve had some similar comments about Windows in the past. Like, a lot of the lock-in value that Microsoft enjoys isn’t anything special that they’ve done — it’s because people are expert in using their platform. If you make them change their workflow, you throw that out. And people profoundly dislike changing their workflow, once they’ve put the effort in to become accustomed to one.




  • Shortage Likely

    https://en.wikipedia.org/wiki/OpenWrt

    OpenWrt (from open wireless router) is an open-source project for embedded operating systems based on Linux, primarily used on embedded devices to route network traffic.

    OpenWrt can run on various types of devices, including CPE routers, residential gateways, smartphones, pocket computers (e.g., Ben NanoNote). It is also possible to run OpenWrt on personal computers and laptops.

    OpenWrt also recommends choosing a device with a minimum of 16 MB of flash and 128 MB of RAM, preferably higher amounts.[77]

    If you can install OpenWrt, you can probably get ahold of hardware that can run OpenWrt.

    OpenWrt provides regular bug fixes and security updates even for devices that are no longer supported by their manufacturers.

    You’ll probably also have a longer device lifetime.







  • I use “mono-9” in all my terminals, including for emacs. On my Debian trixie system, that maps to DejaVu Sans Mono in the fonts-dejavu-mono package.

    $ cat ~/.config/foot/foot.ini
    [main]
    font=mono-9
    $ fc-match mono-9
    DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"
    $ fc-list|grep DejaVuSansMono.ttf
    /usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf: DejaVu Sans Mono:style=Book
    $ dpkg -S /usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf
    fonts-dejavu-mono: /usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf
    $
    

    https://en.wikipedia.org/wiki/DejaVu_fonts

    The DejaVu fonts are a superfamily of fonts designed for broad coverage of the Unicode Universal Character Set. The fonts are derived from Bitstream Vera (sans-serif) and Bitstream Charter (serif), two fonts released by Bitstream under a free license that allowed derivative works based upon them; the Vera and Charter families were limited mainly to the characters in the Basic Latin and Latin-1 Supplement portions of Unicode, roughly equivalent to ISO/IEC 8859-15, and Bitstream’s licensing terms allowed the fonts to be expanded upon without explicit authorization.

    The full project incorporates the Bitstream Vera license, an extended MIT License, which restricts naming of modified distributions and prohibits individual sale of the typefaces, although they may be embedded within a larger commercial software package (terms also found in the later Open Font License); to the extent that the DejaVu fonts’ changes can be separated from the original Bitstream Vera and Charter fonts, these changes have been deeded to the public domain.[1]


  • There are some memory latency benefits to putting memory on a single chip, but to date, that’s largely been handled by adding cache memory to the CPU, and later adding multiple tiers of it, rather than eliminating discrete memory.

    The first personal computer I used had 4kB of main memory.

    My current desktop has a CPU with 1MB of L1 cache, 16MB of L2 cache, 128MB of L3 cache, and then the system as a whole has 128GB of discrete main memory.

    Most of the time, the cache just does the right thing, and for software that is highly performance-sensitive, one might go use something like Valgrind’s cachegrind or something like that to profile and optimize the critical bits of software to minimize cache misses.

    I could believe that maybe, say, one could provide on-core memory that the OS could be more-aware of, say, let it have more control over the tiered storage. Maybe restructure the present system. But I’m more dubious that we’ll say “there’s no reason to have a tier of expandable, volatile storage off-CPU at all on desktops”.

    EDIT: That argument is mostly a technical one, but another, this one from a business standpoint. I expect PC builders have a pretty substantial business reason to not want to move to SoCs. Right now, PC builders can, to some degree, use price discrimination to convert consumer surplus to producer surplus. A consumer will typically pay disproportionately more for a computer with more memory, for example, when they purchase from a given vendor. If the system is instead sized at the CPU vendor, then the CPU vendor is going to do the same thing, probably more effectively, as there’s less competition in the CPU market, and it’ll be the PC builder seeing money head over to the CPU vendor — they’ll pay a premium for high-end SoCs.

    In Apple’s case, that’s not a factor, because Apple has vertically-integrated production. They make their own CPUs. Apple’s PC builder guys aren’t concerned about Apple’s CPU guys extracting money from them. But Dell or HP or suchlike don’t manufacture their own CPUs, and thus have a business incentive to maintain a modular system. Unless one thinks that the PC market as a whole is going to transition to a small number of vertically-integrated businesses that look like Apple, I guess, where you have one or two giant PC makers who basically own their supply chain, but I haven’t heard about anything like that happening.