Sorry, book broke

  • 0 Posts
  • 18 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle

  • sorrybookbroke@sh.itjust.workstoLinux@programming.devWhy do some people hate Manjaro?
    link
    fedilink
    English
    arrow-up
    82
    arrow-down
    1
    ·
    edit-2
    11 days ago

    Their devs constantly make mistakes that harm the ecosystem, they suggest poor practices, and are generally incompetent.

    They ddosed the aur twice the second time the exact same way as the first. No solution was put into place to fix the root cause and it caused a major issue. They didn’t learn.

    The lead arm Dev pushed an update to Asahi (trusted, due to their position) that broke the system for half of the users (those using xorg) showing the dev didn’t test it on xorg at all. The problem? They upped a version for a dependency which had nothing to do with their code. The issue was documented. This dev, their lead arm dev, didn’t check the docs before upoing the version. Didn’t test at all either. This is a lead dev. That’s their standard

    Before asahi was released they claimed manjaro worked on the m1 macbooks with a marketing page and all shipping a random dev version of the Asahi kernal known to not even boot. This was lucky as if it could, the build had a chance to break the computer. What did they do this? Who knows.

    They forgot to update their SSL certs 5 times telling people to change their system clocks the first time. You can automate SSL cert renewal by the way. It’s easy and takes at max twenty minutes if it’s not cooperating and you’ll never have to worry again. This shows, again, they’re not competant and don’t learn from their mistakes.

    They suggested, and strongly defended, using sudo pacman -Syyu which forces a database refresh for every install. This is not likely ever needed unless something fucks up bad and puts unnecessary stress on the repos.

    A lot more too but I’m sleepy. I rarely say a distro is a bad choice but manjaro is the strongest exception for me. You can’t trust their devs. Of course the entire AUR and update issue but that’s hit or miss on whether it effects you

    If you want a semi rolling release like manjaro I’d suggest OpenSuse tumbleweed. Same release idea but with consistantly competant devs.

    Manjaro is a wet fart. I don’t want them sitting in my lap man











  • sorrybookbroke@sh.itjust.workstoArt Share🎨@lemmy.worldSazed
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    3 months ago

    Yoo best boy reading it up. I’m so glad I started that series and Cosmere as a whole but I strongly doubt I’m finishing it any time soon. Taking a break after way of kings to read some Joe Abacrombie. Going full on book-tube with my reading list. I consistently fail to read/wwtch the popular thing because I’m a contrarian hipster at heart so this is my concerted effort. So glad a friend of mine recc’d me tress of the emerald sea to get me into this kick.

    Anyway, since this is an art community I should likely talk about the art. I love the colour choice in the clothing. It makes me think I know how they’d feel




  • Strong preference to the left. The one on the right I never know where to look. Way too busy and I always miss what I’m looking for at a glance. Searching and searching every time sucks shit. On the left, it’s just a list. My overworked brain can handle that easily. Also, I prefer more angular designs over the bubbly pattern that’s so common today. Lastly, when it’s always there it’s easier for my brain to know where things generally are spatially.

    Of course, the left one does waste a good amount of space breaking from a more minimalist idea. You don’t need a menu when you’re already in the settings view you need. Benefits to both, negatives too. I prefer the left version.

    Lastly, I do disagree with the idea that MacOS was doing a “form over function” as the function is clear. It’s a waste of space and, usually, mind function to put things that are un-needed in front of the user at times they don’t need them. MacOS Strives to lower the amount of visual overhead given at all times allowing you to focus on exactly what you’re doing without the rest of the UI in your way.

    I don’t like it aesthetically as though I like minimal design I find taken to the extreme it can be too boring but it absolutely has a function.



  • I’d argue this is more like “I want to build a competitor to spotify so let’s decide between using mariaDB or writing an SQL compliant database from scratch”

    In your example, a database is the end goal and you can either start with a premade or make your own.

    Here, a social media platform is the end goal. Activitypub is a very important part of it but it’s not the entire piece.

    If we replace the parts of your analogy with the original your example would parse out to “I want to make a competitor to lemmies ActivityPub integration, so let’s start with fedify” which is not the same as the article states.

    Now, should you re-impliment a protocol yourself or use a generic library is the real question. Both have their benefits. With option A you have full code ownership and can wrap your solution around your end goal without the issue of dealing with the original to get needed changes accepted. You don’t have to worry about code not written by or understood by you. With option B, you get a more robust and almost certainly more accurate implementation. Along with, for free, better integration with any service using the same library. Very useful for a federated service when talking about cross platform.

    Both have many more positives and negatives of course and each person should decide on their own how to proceed.

    My opinion? I think it’s usually best to own anything which could feasibly be understood by a single dev. Even if each dev doesn’t. Anything larger shouldn’t be internal in my strong opinion unless very good, specific reasons apply that makes an external solution impossible or increadibly difficult. Most negatives of an external library also apply at that point with enough time.