• 1 Post
  • 60 Comments
Joined 3 years ago
cake
Cake day: June 18th, 2023

help-circle





  • To add to this excelent answer, one thing that made me really understand and realize quite a lot about how do CPUs actually work, and why is most of the stuff the way it is, was playing through the amazing “Turing Complete” puzzle game.

    The premise is simple - you start with basic AND/OR/NOT gates, and slowly build up stuff. You make a NAND, and then can use your design. Then you make a counter, and can use that. The one bit memory. An adder. A multiplexer. All using the component designs you have already done before.

    Eventually, you build up to ALU and RAM, until you end up with a working CPU. Later levels even add creating your instruction sets and assembly language, but I never really got far into that part.

    It’s a great combination of being a puzzle game - you have clear goals, and everything is pretty approachable and very well paced. I had no idea how is memory done on the circuit level, but the game made me figure it out, or had hints when I got stuck.

    And seeing a working CPU that you’ve designed from scratch is pretty cool, but most importantly - even though I’ve had courses on hardware, CPU architecture and the like on college, there’s a lot of stuff I kind of understood, but it never really clicked. This game has helped tremendously in that regard, and it was full of “aha moments” finally connecting a lot of what I know about low-level computing.

    I’m not even into puzzle games that much, but this was just a joy to play. It was so fun I sat through it in one session, up until I got to a complete CPU. I very highly recommend it to anyone.



  • To be honest, I saw an article/post about meshtastic, lookes up if it’s active in my city, which it seems to somewhat be (I mean, it has a webpage and like 10 nodes), and decided to give it a try.

    It never really occured to me to look up alternatives, first time I’m hearing about Reticulum, will look into it!


  • There really isn’t a reason not to switch to LibreWolf at this point.

    It’s a shame that Mozzila is set on wasting developer time on tools people do not want, and in turn wqsting LibreWolf dev time on removing it.

    Aodopting an opt-out model instead of opt-in is also bullshit. You should do opt-in, measure adoption and THEN maybe consider making it default, if it’s high. It probably won’t be. People who don’t care about what their tech does are already using chrome or edge.

    I’d be also surprised if it didn’t do stuff like re-enabling itself after updates or some shit.







  • First time I’m seeing Uiua, and I like it. It’s kind of cute, even though I know I’ll probably never use it.

    However, seeing one of their goals being “code that is as short as possible while remaining readable” is kind of ironic, given how it looks and reads. But I don’t mind, it’s still pretty adorable.

    It looks like it’s hell to learn and write. It’s possible that once you learn all the glyphs (which IMO adds unneccessary complexity that goes against their goal of being readable), it might be easier to parse. I’m probably not the target audience, though.



  • I was doing cybersecurity for a few years before I moved to gamedev, and I vaguely remember that at least the older versions of GUID were definitely not safe, and could be “easily” guessed.

    I had to look it up, in case anyone’s interrested, and from a quick glance to the GUID RFC, it depends on the version used, but if I’m reading it right, 6 bits out of the 128 are used for version identification, and then based on the version it’s some kind of timestamp, either from UTC time or some kind of a name-space (I didn’t really read through the details), and then a clock sequence, which make it a lot more guessable. I wonder how different would the odds be for different versions of the UUID, but I’m too tired to actually understand the spec enough to be able to tell.

    However, for GUID version 4, both the timestamp and clock sequence should instead be a randomly generated number, which would give you 122 bits of entropy. It of course depends on the implementation and what kind of random generator was used when generating it, but I’d say it may be good enough for some uses.

    The spec also says that you specifically should not use it for auth tokens and the like, so there’s that.