Baby Marxist

Currently deprogramming and chewing though the reading list

https://www.mlreadinghub.org/

I like to argue to hone my ideas and concepts. If you keep responding then I will too.

  • 0 Posts
  • 6 Comments
Joined 11 months ago
cake
Cake day: July 26th, 2025

help-circle
  • Let’s not be obtuse, I was simply using one tool as an example. There’s a lot more, and there’s a lot of other reasons why Python is critical as a component of a Linux system.

    Let’s just start with systemD. Did you know that systemD requires Python to build? GTK4 has the same requirement.

    Systems that have replaced the Python component often use a different language like Lua in their place, like alpine Linux.

    Python is literally the glue that people use to bind all of your C programs together because it can be done quickly, easily, and efficiently unlike C and C++.

    You literally cannot use a modern Linux system without Python. It’s just straight up not possible Unless you’re using something that is specifically stripped and built for the removal of Python. It is assumed for a ton of packages and scripts, including major component tools like Ansible, which are critical in the commercial environment.


  • Sure, I think we can just ignore the fact that the Red Hat Core package manager was driven by Python for almost 20 plus years and only recently, as of two years ago, switched to C++.

    You are correct at seeing C as a backbone, but most tools, especially early tools were written in a language like Python. Its easy to prototype and adopt.

    I guarantee you if I go through a list of system tools that every Linux distro is dependent on, including something like a package manager, which the linux os is absolutely dependent on You would be genuinely surprised by the amount of tools written in a language like Python or Ruby.

    Also, a package manager is not core to a Linux distribution, Really? That seems like stretch.

    Yes, you can compile everything from source. Very few people do.




  • This is just a classic case of bad use of the tools provided. Agents are notorious for making shit up Or getting something that’s just like super close, but not quite accurate.

    I bet this dude also probably just uses the same session over and over and over and over again, which clogs up his context window and makes the model less accurate the longer it goes on to.

    This probably could have been prevented if it had been forced to show a plan before it tried to do anything. It’s hard to know because the article is so light on details. You also shouldn’t brazenly trust the thing so much. You should run a command and walk away. You should keep an eye on what it is doing.

    It’s a bit like giving a junior developer a production key and being like “don’t delete production!” and then walking away.

    The way the guy was prompting this agent also leaves a lot to be desired. It’s trained to work on emulating human thoughts, speech patterns. Turns out When giving instructions, it’s really difficult to figure out what to do from a list of things to not do. If the dude just instead told the agent what to do and how he wanted it to work and when it needed to bring things to his attention, instead of telling it to not guess, instead explaining that it needed to use whatever tools to go look up a documentation to understand the context and scope of the project it’s working on It does a better job.

    Giving a model the right context to do something is the difference between a model doing something like deleting your production database or your model acting like a magical machine that can get anything done.