• 1 Post
  • 105 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle

  • cbarrick@lemmy.worldtoLinux@lemmy.mlLinus Torvalds and Richard Stallman
    link
    fedilink
    English
    arrow-up
    76
    arrow-down
    1
    ·
    4 days ago

    However, Linus’s kernel was more elaborate than GNU Hurd, so it was incorporated.

    Quite the opposite.

    GNU Hurd was a microkernel, using lots of cutting edge research, and necessitating a lot of additional complexity in userspace. This complexity also made it very difficult to get good performance.

    Linux, on the other hand, was just a bog standard Unix monolithic kernel. Once they got a libc working on it, most existing Unix userspace, including the GNU userspace, was easy to port.

    Linux won because it was simple, not elaborate.





  • \1. Many retro games were made for CRT TVs at 480p. Updating the graphics stack modern TVs is valuable, even if nothing else is changed.

    \2. All of my old consoles only have analog A/V outputs. And my TV only has one analog A/V input. The mess of adapter cables and swapping is annoying. I want the convenience of playing on a system that I already have plugged in.

    \3. I don’t even still have some of the consoles that play my favorite classic games, and getting retro hardware is sometimes difficult. Especially things like N64 controllers with good joysticks.

    Studios don’t need to do a full blown remake to solve these problems. But I’m also not going to say the Crash and Spyro remakes weren’t welcome. Nintendo’s Virtual Console emulators toe this line pretty well.

    But studios should still put in effort to make these classic games more accessible to modern audiences, and if that means a remake, that’s fine with me.

    (I’m mostly thinking about the GameCube/PS2 generation and earlier. I don’t see much value in remakes of the Wii/PS3 generation yet.)








  • cbarrick@lemmy.worldtoPython@programming.devNumPy 2.0.0 released
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    13 days ago

    Huh. This got me curious.

    Yes, I did just type a bare URL. Every mature markdown parser I’ve used turns this into a link, and appropriately handles trailing punctuation.

    So I went to the spec, and it’s explicitly called out that this is not an autolink. Autolinks must be explicitly surrounded with angle brackets <>.

    So yeah \shrug.

    https://spec.commonmark.org/0.31.2/#autolinks

    Edit to be clear: This means that both of our markdown parsers are wrong relative to the commonmark spec. But I’ll argue that if a parser is going to attempt to autolink this, then handling trailing punctuation is better than not.







  • I assume so.

    If you’ve got a phone or laptop charger, then input voltage doesn’t often matter. They’ll work with either 120v or 230v.

    And in general, you likely won’t be bringing non-charger electrical stuff with you when travelling.

    So if you’re installing this in the US, it makes sense to just wire this with 120v. Peoples’ phone chargers will continue to work just fine.


  • Mostly I use custom launchers because I don’t like the Google News feed

    What’s wild to me is that back in the Google Now era, I was so excited to root so that I could install the extension for Nova to add Google Now.

    But these days, the Google “Discovery” feed is trash compared to what Google Now once was.