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

help-circle




  • IDatedSuccubi@lemmy.worldtolinuxmemes@lemmy.worldHelp
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    1 year ago

    It very highly depends on the application

    For something used daily that’s more or less true

    For something that needs very complex configuration like specific ffmpeg transcoding rules and cmake build files - you’d have menus that are 5-10 pages long and full of super detailed selections and forms, while in reality you’d only want to switch on or off one thing, so it would be easier just to write the command

    When I made my small game engine I had a second window full of settings that I could change dymamicaly. After like 2 months of work it was so full of settings it was very hard to navigate even with all subdivisions and layouts properly made

    Also, GUI apps often lack specific or new settings for the terminal app they’re built on





  • I’m pretty sure it’s either a myth (that it doesn’t work) or some US-centric thing, because when I worked as a delivery guy, I used to go through probably hundreds of different elevators in high-density residential buildings, and most of them have doors that stay open very long to allow baby strollers and heavy appliances to be placed inside, and on pretty much all of these the door closing button works, immediately closing the door


  • This is what I and many other programmers have done (not the removal, but fake delays), because it improves user experience, actually:

    1.When the user clicks a button that should take long in their mind (like uncompressing a zip file etc) but is actually fast, it might seem like something is wrong and it didn’t work

    2.When the user transitions between layouts of the application, if it loads everything too fast it will look too abrupt, a fake delay will be made here if a transition animation is not possible/doesn’t fit