• 0 Posts
  • 74 Comments
Joined 1 year ago
cake
Cake day: June 4th, 2023

help-circle


  • We’re not talking about the same thing here. First off a large jack to small jack adapter would be needed in rare circumstances, if you happen to use a pair of headphones that only uses a large jack with a small device like a phone, which obviously only has a small one.
    That whole large jack discussion was started because of the quote from Wikipedia I posted, where they mention just how old the jack is. I’m guessing you haven’t read the rest of the comments since you brought it up?

    2nd of all a jack adapter is just “wire”, it’s passive ( doesn’t have any circuitry), and doesn’t require any support.
    For a dongle type of adapter that’s quite different. Software and hardware and compatibility come into play.
    Lots of dongles have a DAC built into them which is separate from the phone DAC. It’s duplicating something you already have, and if your phone has a good one buit into it (which it should), the flimsy dongle most probably has a very cheap one.
    I have a dongle and it only works if I plug it in before taking calls. If I already answer and then use the dongle the sound won’t work out of the headphones so it’s useless…



  • I think people who dislike the headphone jack must be young and not have (good) wired headphones.
    Older people (older than teenagers and young adults I mean) often have a few pairs of good headphones they got over the years, and it’s a massive waste to just throw them away and buy wireless because that’s what the trends demand. And in most cases wireless won’t sound as good, because the budget needs to go to bluetooth chips, and dacs, and batteries and all that crap, instead of just focusing on audio.

    According to Wikipedia, ‘The original 1⁄4 inch (6.35 mm) version descends from as early as 1877’, and it’s been an industry standard since then.
    You can use it not just for headphones but as a line out, to connect all kinds of audio devices between them. You can hook up your phone to a car audio system, an old radio (if it has input, I think most do), a guitar pedal or an amplifier, a reverb or an effects unit, etc., just with the “magic” of wires.





  • highduc@lemmy.mltoLinux@lemmy.mlManjaro OS
    link
    fedilink
    arrow-up
    2
    ·
    7 months ago

    I know you need a new nvidia driver every time the kernel updates, but why keep 50 kernel versions? My beef was them offering so many (outdated) versions instead of keeping the latest one which would make things very simple for users (imo).


  • highduc@lemmy.mltoLinux@lemmy.mlManjaro OS
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    7 months ago

    I know that these packages are “linked”, and for every kernel update you need a new nvidia driver, I don’t understand though why they keep so many kernel versions in the repo (and their respective nvidia drivers ofc). Just makes things confusing, I assume people generally want the latest kernel the distro has to offer, or if they want something else it’s a different kernel “flavor” like lts, zen, rt, etc.



  • highduc@lemmy.mltoLinux@lemmy.mlManjaro OS
    link
    fedilink
    arrow-up
    11
    arrow-down
    3
    ·
    edit-2
    7 months ago

    It’s not all “purists” and “tribalism”, Manjaro actually has issues. Besides the well known certificate issues and older packages, I have the following anecdote which made me really dislike it.

    A friend has Manjaro and one day his nvidia drivers stopped working after an update. I helped troubleshoot over the phone, while looking over the wiki. For nvidia drivers they have their own wrapper around pacman.

    Turns out there’s a different nvidia driver for each kernel version. Already a stupid design. So unlike arch where there’s 1 kernel package (the latest the distro offers) and 1 matching nvidia driver, Manjaro has dozens…

    The wiki never mentions how to install or update the drivers manually with pacman or anything like that. It pushes their own tool, a stupid wrapper around pacman, which is supposed to manage this for you.

    In my friend’s case, the tool failed. It was trying to run pacman but there was a conflict issue. But the tool didn’t show the pacman output, so we couldn’t figure out what the tool is trying to do, and why it doesn’t work. We tried removing the tool and re-installing, and all kinds of messing around with it. It failed to install the drivers, it failed to remove the drivers, it kept failing whatever we tried.

    Eventually we figured out the naming convention they used for the packages (again not mentioned in the wiki), and manage to install the correct kernel - driver pair manually, using pacman.

    Tl;dr: poor design, bad documentation, and they push their own crappy tools which hinder instead of helping