• 1 Post
  • 79 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle
  • Because the lowest common denominator is much MUCH lower than you think it is.

    This means it’s easy to indoctrinate and easy to maintain that for a massive number of people.

    Scientific illiteracy is extremely high, and actual “6th grade reading comprehension” is the highest level of literacy for > 50% of a country like the U.S. and ~20% are low literacy or actually illiterate.

    This means that half of everyone in the U.S. can read and understand what they read at or below a 6th grade level. This isn’t “reading big words”, it’s “tell us about what you read”, “what is the relationship between x & y” type questions.

    This comment for example, up to this point only, would be difficult to understand & comprehend for > 50% of people in the U.S. (it demands an 11th grade reading comprehension). And may be misread, misunderstood, or not understood at all.

    People are driven to religions to cults and alt conspiracy theories when they don’t understand how the world works around them. They latch onto extremely simple often misleading or incorrect ideas of how the world works because they can understand it and it “makes sense” within their sphere of ignorance (we all have one, this isn’t meant to be a disparaging term).

    This means that the problem is that humans are just not smart enough to escape religion yet. It’s the simplest answer, and it appears to be correct.




  • The language it’s written in has very little, almost nothing, to do with how efficient larger applications are.

    This is almost entirely up to the design and day-to-day decisions of the developers. These almost always outweigh the efficiencies of the underlying languages themselves (within reason).

    A single location of poor data access patterns could negate the aggregate performance gains of your entire application, as an example. A framework that prevents you from making simple mistakes and drives you towards more efficient patterns goes much further than the language is written in.

    Between Rust, C#, Java, and Go you’re essentially even on performance for large applications (with C# pushing ahead of the pack). What you are not even on is engineering efficiency, it’s going to take considerably longer to build the same set of features in rust than any of the others listed. And the performance is likely the same, potentially even worse depending on the maturity of the ecosystem.

    Rust is a great systems design language and a great language to choose when developing high efficiency libraries & frameworks for I/O and data processing. It’s not really a great choice for application development due to how slow it is to actually get things done in.

    I fully expect to see alternate backends written in more operationally efficient languages over the next decade that will catch up to the official Lemmy codebase, and potentially even replace it. It actually sounds like a super fun project, funding is always a problem though.










  • They usually do yes however it’s all about prioritization.

    You may have hundreds or thousands or open requests and issues.

    With tens of thousands of closed issues that were either not reproducible, not actually problems, or largely indecipherable.

    There’s usually a feature roadmap which is where most of the development money and time is spent. If it’s an older business application then certain bugs might easily take weeks to find, fix, test, validate, go through user acceptance, A/B test, and then deploy. But fixing is expensive work, so if the bug isn’t severe it’s usually deprioritized next to higher priority work.


  • Not trying to start an argument here but I do want to point out that your argument foundations on blaming other competitors instead of looking at what can make the platform you’re passionate about more palatable.

    There are many, MANY, reasons people will choose Mac and windows on their own accord.

    Your argument hand waves that away to make a boogieman out of mac and windows, and erodes the true viability of Linux as a platform by not looking at how it can improve, and instead focusing on how the competition “is bad”.

    Taking the ego stance that Linux “would be great if it wasn’t being held back by the bad guys” doesn’t actually help Linux desktop adoption…



  • I mean if you’ve never seen or used a car before, and someone from a position of relative authority or trust gave you a very convincing argument that a particular part that you don’t understand is easy to remove and you’ll benefit from it…

    Yeah it’s pretty reasonable that the average person might shoot themselves in the foot by letting them remove that part (tell them a command to run).


  • douglasg14b@lemmy.worldtolinuxmemes@lemmy.worldsystemdeez nuts
    link
    fedilink
    arrow-up
    119
    arrow-down
    5
    ·
    edit-2
    2 months ago

    I mean you essentially just highlighted a primary user experience problem with Linux…

    Information & advice is fragmented, spread around, highly opinionated, poorly digestible, out of date, and often dangerous.

    And then the other part of it is that a large part the Linux community will shit on you for not knowing what you don’t know because of some weird cultural elitism…

    When you finally ask for help once you realize you don’t know what you’re doing, you’re usually met with derisive comments and criticism instead of help.


    Do you want Linux to be customizable so that users can control it however they want. Or do you want it to be safe so that users don’t mess it up? You can’t have it both ways, and when you tell users to “go figure it out” and then :suprise_pikachu: that they found the wrong information because they have literally no idea what’s good or bad, instead of helping, they get shit on.

    It’s the biggest thing holding Linux desktop back.



  • douglasg14b@lemmy.worldtoSelfhosted@lemmy.worldNPM - What services need what toggled?
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    8
    ·
    edit-2
    3 months ago

    Yeah I had literally no idea what you were talking about until you mentioned the actual name in the comments.

    NPM almost universally refers to node package manager in any developer or development adjacent conversation in my experience. Given that both the site, the command, the logo, and the binaries are “npm” makes that more appropriate.

    Nginix proxy manager is far to niche to be referred to universally by acronym when it’s only ever used as an acronym when the context for it’s usage has already been defined (ie. In it’s documentation).

    This becomes much more clear when you Google the acronym.


  • It is, but also it’s worrisome since it means support is harder, which means risk of abandonment is higher and community contributions lower. Which means “buying in” is riskier for the time investment.

    Not really criticizing, 10/10 points on making something and then putting it out there, nothing wrong with that. Just being a user who’s seen too many projects become stale or abandoned, and have noticed that the trend has some correlation to the technology choices those projects made.