Preferences

Firehawke
Joined 477 karma

  1. That's been my experience. The Pi 3 was notorious for killing SD cards, for instance. I know one guy who eventually just moved all Pi 3 installations he made over to USB sticks because every Pi 3 he used would just kill SD cards at random but far faster than they should have. Not many write cycles at all, just surged the cards or something.
  2. We already know prices will go up considerably-- they always do after a merger, and you'll lose the option of subbing for one or the other only when they have something you want to watch. Most people are not keeping two subs going constantly and are just alternating when there's something worthwhile.
  3. Or, for that matter, using GitHub Actions to do the final Hugo build and remote deployment when you do a git push.
  4. No, they absolutely know. They've been very very slowly migrating stuff over to the new Settings panel bit by bit. If you look at what's in Control Panel now, it's maybe half as much as what used to be in there ten years ago.

    That said, it's insanely ridiculous that it's taken 10 years to get it even halfway done.

  5. CRT simulation didn't run well on Intel iGPUs for a very long time. While they could run the effects, they couldn't run them fast enough. There was longstanding advice in the emulation scene to not bother using shaders unless you had a dGPU; that only changed around Sandy Bridge, where the performance became sufficient.
  6. Considering that MAME's shaders run fine on a 2011-era laptop with the positively primitive Intel iGPU of the Sandy Bridge era, I can only assume they're intending to run this on something extremely ancient that would end up being less power efficient for the task.

    Even a Raspberry Pi can handle this stuff at low power consumption today.

  7. GoG is packaging a large chunk of their library in an emulator already. DOSBox is what got them started, in fact.
  8. A lot of the time, they lock the slot to only their officially supported modules. Dell is rather notorious for doing that.
  9. Something like what's done with https://www.hardfought.org/nethack/ maybe?
  10. This just wrecked my trust in KeePassXC. Time to go see if anyone's going to continue this from a fork where they aren't setting themselves up for a massive security failure of some variety.
  11. That seems very likely. One of the first things I'd noticed back in the early 90s when I got my shell account and used Pico for the first time was that the UI was similar (not exact copy, mind you) of how Wordstar was, with some basic guidance at the bottom to get you started.

    Also kind of reminds me of the old Telix terminal software for MS-DOS, with the bottom status bar. Not exactly the same, but again quite similar in the approach to have you just quick glance at the bottom of your screen for a HUD.

  12. Same. My first internet access was a BSD shell account back in 1993; I had Pine and Pico on there. Coming from a world of MS-DOS BBSes (I ran one myself!) it wasn't that hard to take QEdit skills and move that over to using Pine and Pico-- it was quite comfortable.

    I still tend to muscle memory my way through using Nano when I need to do quick file edits on Linux.

  13. Something like that happened to me in first grade. I was trying to go down a slide and a friend decided to climb the slide itself. He ended up launching me off the side of the slide. It was maybe a five or six foot slide, and I remember going over the side in slow motion, grabbing for the rim of the slide but being at least 6" away from reaching it, and then suddenly.. sharp pain and pitch black as I landed on my back.

    I was conscious again about 10-15 seconds later. It's the kind of thing that sticks with you your whole life. It probably wasn't close to life threatening, but the combination of adrenaline, sharp pain, and brief unconsciousness definitely leaves an imprint in your memory.

  14. It's also how easy the userland can break things. Windows backwards compatibility tends (even if it's not 100% successful on this) to stay relatively stable. It's kind of funny that the most compatible way to distribute Linux binaries for games is to target Proton/Wine.
  15. This is exactly the same for me. I definitely like being able to switch between a tablet/e-reader for regular reading and using my phone when I'm stuck waiting in line or transport.

    I don't specifically need the physical book; space-wise it'd be difficult to keep all of the books I'd like to own. Just not enough space. That means that DRM becomes a major concern; I have absolutely no issue with stripping DRM for my own use whether it's a game, movie, music, or book.

  16. I never said cognitive, just dissonance.

    A tension or clash resulting from the combination of two disharmonious or unsuitable elements.

  17. Yeah, that's a pretty big case of dissonance there. While I agree with large parts of the article in general, the bit about getting yourself fired is just completely out of touch with reality in a job market trying to replace engineers with shitty AI.
  18. Not much in the way of WYSIWYG, unfortunately. There've been some VSCode extensions in the past to simplify editing but that's about as good as it gets.
  19. MAME's documentation was moved to Sphinx (and thus RST) a number of years ago. I headed up that project, in fact.

    There was a significant learning curve getting good output when converting some of the old ASCII charts out of .txt files, but once settled it makes for a much better user experience and it auto-compiles to HTML, PDF, and even EPUB with zero additional effort.

    I would definitely not want to go to Markdown from RST for technical documentation that's more complex than a Github readme.

  20. DJGPP was the primary development platform for MAME when it was limited to MS-DOS. It certainly got the job done.

This user hasn’t submitted anything.