• 1 Post
  • 12 Comments
Joined 1 year ago
cake
Cake day: August 6th, 2024

help-circle






  • It definitely is, and yes, you’re right, I should open a bug report.

    But then again, you could make the argument that a user-friendly OS shouldn’t require developer level expertise that’s necessary for opening bug reports in the first place. After all, bug reports require a certain quality level that’s not obvious to newbies (like how to reproduce et cetera).



  • glorkon@lemmy.worldtolinuxmemes@lemmy.worldDeveloper appreciation time!
    link
    fedilink
    arrow-up
    9
    arrow-down
    1
    ·
    edit-2
    9 days ago

    Unfortunately in Linux, UI tools often take away some of the transparency you get with the CLI tools they’re made for.

    I’ve recently tried setting up a VPN connection to my workplace using the EndeavourOS configuration UI. It basically just said “can’t connect, haha, fuck you”, so I had to dig deeper. Finding out how to use the CLI commands necessary to identify and fix the problem took some time and effort, but in the end, I managed to set it up successfully (turned out most Windows admins still think l2tp is hot shit while the Linux world considers it obsolete).

    In this case, UI wasn’t as user friendly as CLI, because it hid vital information that was necessary to solve the problem.

    A better UI would probably have solved that problem quicker and easier. In an ideal world, you get intuitive GUI tools that cover all use cases and you still have the option to use the CLI if you want to dig deeper. So yeah, I agree with the point you’re making - Mint trying to be as user friendly as possible by offering accessible UI tools is a good thing and one of the reasons why Mint is so popular. (It’s also a reason why Windows sucks ass, because for most UI things the CLI equivalent is either non-existent or cryptic as hell…)

    The point I’m making - GUI tools should always try and make using the CLI unnecessary. Taking away complexity without taking away functionality is the key, and as a consequence, those GUI tools will not be underappreciated for sure.






  • Lossy audio compression algorithms work based on psychoacoustic effects. The average human ear will not detect all the “parts” in a lossless signal - there are things you can drop from the signal because:

    • Human ears are most sensitive around the frequency of human speech, but less at others
    • If there is a loud signal, a much more silent one very close will be masked if it occurs within a couple of milliseconds around the loud one
    • There are other more subtle aspects of the human ear you can use to detect signals we just won’t notice.

    So in order to determine exactly which parts of an audio signal could be dropped because we don’t hear them anyway, they measured a couple of thousand people’s listening profiles.

    And they used that “average human profile” to create their algorithm.

    This, of course, has a consequence which most people, including you apparently, do not understand:

    The better your personal “ear” matches the average psychoacoustic model used by lossy algorithms, the better the signal will sound to you.

    In other words, older people, or people with certain deficiencies in their hearing capabilities, will need higher bitrates not to notice the difference. In the 90s, I used to be happy with 192 kbps CBR MP3. But now, being an old fuck, boy, can I hear the difference.

    Ironically, I can detect the difference not because my ears are “trained” or “better”, I can detect it because my ears are worse than yours!

    So the whole bottom line is this: While it may be true that you, personally, do not require lossless to enjoy music to the fullest, other people do. Claiming that lossless isn’t needed by 99.9% of the population is horseshit and only demonstrates that you have no clue about how lossy compression works in the first place.