• 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: July 8th, 2023

help-circle

  • I can wholeheartedly vouch for lichess.org. Not only because of their privacy policy but for what they offer in terms of chess. Besides the standard game you get an analysis engine that points out good moves, how likely a player is to win, let’s you switch sides, etc.

    But my favorite thing is actually the different chess variants you can play. There’s one where you are facing a legion of pawns, another where captured pieces explode and take down adjacent pieces and another where you get to replace captured pieces on the board. But my go to is simply chess with randomized but symmetrical positions in the backline (pawns stay the same). This makes every game unique and challenging; you actually need to think about your best moves from turn 1 instead of memorizing openings which is perhaps my biggest gripe with default chess.

    Give it a try, I say 😉.


  • One reason to keep in mind is backwards compatibility and the expectancy that every Linux system has the same basic tools that work the same.

    Imagine you have a script running on your server that uses a command with or without specific arguments. If the command (say tar) changes its default parameters this could lead to a lot of nasty side effects from crashes to lost or mangled data. Besides the headache of debugging that, even if you knew about the change beforehand it’s still a lot effort to track down every piece of code that makes use of that command and rewrite it.

    That’s why programs and interfaces usually add new options over time but are mostly hesitant to remove old ones. And if they do they’ll usually warn the others beforehand that a feature will deprecate while allowing for a transitional period.

    One way to solve this conundrum is to simply introduce new commands that offer new features and a more streamlined approach that can replace the older ones in time. Yet a distribution can still ship the older ones alongside the newer ones just in case they are needed.

    Looking at pagers (programs that break up long streams of text into multiple pages that you can read one at a time) as a simple example you’ll find that more is an older pager program while the newer less offers an even better experience (“less is more”, ¿get the joke?). Both come pre-installed as core tools on many distributions. Finally an even more modern alternative is most, another pager with even better functionality, but you’ll need to install that one yourself.







  • Good point.

    I guess just having a staggered temporal restriction is fine, don’t need to wait until you retire necessarily. You would still receive a portion of your salary package in the form of classic currency and plenty for a good life too. An example could look like this and I’m obviously making up the percentages and durations here, they would need to be fine tuned:

    • 40% of salary as cash
    • 10% of salary as stocks that can’t be sold within 6 months
    • 10% of salary as stocks that can’t be sold within 12 months
    • 10% of salary as stocks that can’t be sold within 18 months
    • 10% of salary as stocks that can’t be sold within 24 months
    • 10% of salary as stocks that can’t be sold within 30 months
    • 10% of salary as stocks that can’t be sold within 36 months







  • It’s so dumb that JSON doesn’t officially have comments.

    So much this.

    Used to work at a company where I sometimes had to manually edit the configuration of devices which were written and read in JSON. Super inconvenient if you have to document all changes externally. As a “hack” I would sometimes add extra objects to store strings (the comments). But that’s super dicey as you don’t know if it somehow breaks the parsing. You’re also not guaranteed the order of objects so if the configuration gets read, edited and rewritten your comment might no longer be above/below the change you made.

    Always found it baffling that such a basic feature is missing from a spec that is supposed to cover a broad range of use cases.