• 298 Posts
  • 1.98K Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle






  • It’s not about their actual effectiveness, it’s about the justification people use to force more “AI” reasons to fire people, reduce pay, eliminate jobs, and so on, and so on…

    Literally the first point in this speech, though broad, is making that case. A very small number of people are forcing this shit down people’s throats, and using it to justify the loss of monumental numbers of jobs.

    Feel free to look up Amazon’s upcoming waves of layoffs, Salesforce, Google, HP…etc. Amazon alone claims they will be replacing 150k jobs in the US alone in the next year with robots. Again, first point brought up by Bernie.






  • That’s…an opinion that is not backed by any facts at all. What in the world are you talking about with “bloat” 🤣

    So you’re a newbie, and making lots of wild claims and taking awfully opinionated positions in this thread all over the place. I don’t think you want help, so just be on your way 👍


  • This…is not accurate. Not being pedantic, just correcting the misunderstanding so you know the difference.

    LTS releases are built to be stable on pinned versions of point release kernel and packages. This ensures that a team can expect to not have to worry about major changes or updates for X years.

    Rolling Releases are simply updating new packages to whatever versions become available when released. Pretty much the opposite of an expected stable release for any period of time.

    Doesn’t have anything to with “forced reinstall” of anything. If you’ve been having to fully reinstall your OS every time a new LTS is released, you are kind of doing extra unnecessary work.




  • just_another_person@lemmy.worldtoLinux@lemmy.worldNew to Linux
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    2
    ·
    3 days ago

    You won’t need a terminal unless you refuse to use the GUI tools that do the same thing.

    If you want to use the terminal, go for it and use the default. If you eventually find it lacking THEN start investigating different options.

    Just use everything as you normally would otherwise, and you shouldn’t notice a huge shift.




  • (typing quickly, excuse errors)

    Title: The title is both confusing and misleading to the actual topic being discussed, which is CVEs being used to identify vulnerabilities to be exploited. The tool is irrelevant, and the tool in the headline is actually mentioned very little in the content.

    Staying on topic: the title sets out a few things as the topics: 1) NPMScan 2) Vulnerabilities 3) Frameworks being exploited.

    It then shifts in the first details to middleware exploits, and how routes are mishandled. So a reader might be asking "Wait, is this a post about middleware attacks, or something specific to NPMScan/CVE exploits?

    A title or headline should be a simple summarization of the topics discussed, and the content should stick to what those topics are. A more accurate title to this piece would be “How Hackers use CVE information to craft exploits in X, Y and Z”

    Diversion from topics: While keeping the meat of an article as close to the main topic thread, it’s important explain the when/where/why you are diverting from that thread for context. When doing so, you’re explaining the relationship between your main topic, and this new information being pertinent and important to the discussion overall.

    Just adding a bunch of unrelated information leaves the reader confused about what those ties to the main thread are, and usually will be forgotten or skipped if they came to your content based on the headline and looking for specific information.

    An example of this being used horribly all over the place is recipe sites. You go looking for a Holiday Cookie recipe, and are presented with with pages of journal entries about the authors childhood cookie memories. It’s not pertinent to the actual content being requested, and people will skip it.



  • Well, no. Not to shoot down your comment or anything, but you’ve only learned a lot about Nix still in your example.

    For instance, if someone presented you with an Arch system of some sort and asked why a certain systems unit wasn’t working, or why the speakers on their laptop don’t work but the headphones jack does, or why their Nvidia kmod modules aren’t loading.

    Your experience with Nix is t going to help with some of the more basic functions of a traditional Linux system because of the abstractions in top of abstractions that you’re used to interacting with on Nix.

    I’m not even digging on Nix, like I said, it was designed for a very specific purpose. I’ve run hundreds, if not thousands, of various build system permutations on Nix over the years, and even I wouldn’t even think about using it for really basic stuff like running a Desktop 🤣