• 0 Posts
  • 23 Comments
Joined 11 days ago
cake
Cake day: February 3rd, 2026

help-circle
  • Alberat@lemmy.worldtolinuxmemes@lemmy.worldGUIs
    link
    fedilink
    arrow-up
    1
    ·
    4 hours ago

    that could be it… I’ve just thought about it a lot and came up with a new theory.

    it seems to me that the limitations of screen real estate seem surmountable. eg: a settings menu could have a search bar like in android, meaning your options can be accessible even though they’re buried in the gui. then, your settings could be “stable” and repeatable by adding flags like in google chrome (another gui program).

    you can actually use chrome from a cli with selenium or the headless command (–headless) and I’ve used this to scrape websites locked behind Javascript. but average chrome users don’t demand the further development of these features.


  • Alberat@lemmy.worldtoMicroblog Memes@lemmy.worldNot a bad idea
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    5 hours ago

    you base the random dice roll on the proof of work of the block chain. proofs of work generate randomness because (proof by contradiction) if they didn’t it would be easy to find the next block and make a bunch of money.

    EDIT: more concretely, in a blockchain, “miners” compute a “hash” of the chain up to the latest block, with an extra random “nonce”. they then check if this hash has a certain distinguishing feature (eg 5 leading zeros). if it doesn’t have this feature, the recompute the hash with a new nonce. the rest of the bits in the hash thus become random. thus, if you commit to using a future hash to determine your lottery, it can be guaranteed to be random (or prove you have enough money to manipulate the block chain which is very difficult)


  • Alberat@lemmy.worldtolinuxmemes@lemmy.worldGUIs
    link
    fedilink
    arrow-up
    2
    ·
    7 hours ago

    yes, great example. also: when the creators of that program decide the want to redesign the ui, all of your tutorials on how to do things break.

    my theory is that its not something inherent about using text instead of graphics: a maintainer of a cli program could also decide that they want to redesign the command line options. but its more that users of guis don’t demand stability or repeatability. they are impressed by a ui redesign and so that’s what they get.



  • i think one difference between guis and clis that people don’t think about is composability. you cant do something like “pipe the contents of a folder into vscode and do a regex find and replace” but that’s what pipes let you do on the command line. with gui programs, you always have to do these things manually… which is nice the first time but then time consuming each subsequent time.