Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)GR
GravelPieceOfSword @ GravelPieceOfSword @lemmy.ca
Posts
20
Comments
97
Joined
2 yr. ago

  • As someone who has done a lot of debugging in the past, and has also written many log analysis tools in the past, it's not an ether/or, they complement each other.

    I've seen a lot of times logs are dismissed in these threads recently, and while I love the debugger (I'd boast that I know very few people who can play with gdb like I can), logs are an art, and just as essential.

    The beginner printf thing is an inefficient learning stage that people will get past in their early careers after learning the debugger, but then they'll need to eventually relearn the art of proper logging too, and understand how to use both tools (logging and debugging).

    There's a stage when you love prints.

    Then you discover debuggers, you realize they are much more powerful. (For those of you who haven't used gdb enough, you can script it to iterate stl (or any other) containers, and test your fixes without writing any code yet.

    And then, as your (and everyone else's) code has been in production a while, and some random client reports a bug that just happened for a few hard to trace events, guess what?

    Logs are your best friend. You use them to get the scope of the problem, and region of problem (if you have indexing tools like splunk - much easier, though grep/awk/sort/uniq also work). You also get the input parameters, output results, and often notice the root cause without needing to spin up a debugger. Saves a lot of time for everyone.

    If you can't, you replicate, often takes a bit of time, but at least your logs give you better chances at using the right parameters. Then you spin up the debugger (the heavy guns) when all else fails.

    It takes more time, and you often have a lot of issues that are working at designed in production systems, and a lot of upstream/downstream issues that logs will help you with much faster.

  • I've used a lot of distributions over the years, and I don't think you have to worry about a different set of commands across most distributions. It's some variation of distropkgmgr followed by command, where command, where command is generally one of install upgrade refresh/update remove search to name the most common. If you use a software frontend like gnome-software or discover, you don't even need to worry about command line differences.

    The only exception to that is nixos, which I wouldn't recommend to someone just switching. It is very cool, just needs more experience.

    The shell commands are the same one installed for the most part.

    Out of curiosity, are you planning to use a different os when your ssd arrives? I switched from Ubuntu to endeavouros (Arch) to Opensuse tumbleweed on my primary laptop (i9 processor), no complaints 😁!

  • Very cool.

    Interesting timing that opensuse recently announced slowroll, which has a slower cadence for updates (updates with monthly frequency, rather than daily, while security updates are still ASAP.

    Depending on whether frequent updates is you thing or you prefer slightly delayed cycles.. you can easily convert your install to slowroll

    https://en.opensuse.org/openSUSE:Slowroll

  • Ubuntu uses snaps, which I've found sluggish on older ide hard drives. To be honest, even flatpaks are very slow for these in my experience.

    I think you might be better off with opensuse tumbleweed.

    Novelty recommendation besides tumbleweed: antix.

    While I haven't used antix except out of curiosity in a virtual machine, they are lightweight, but they have a hard stance against systemd.

  • Yep... definitely crazy. Tried easy, was thinking I seemed to be pretty smart up to 4 lines. Then it just kept screwing me with two alternating pieces and the holes started. It loves giving you angles that go the wrong way around given your current block layout 😅