[–] 6 points 3 weeks ago (3 children)

Torvalds is doing an illicit substitution of Claude, Gemini, Copilot et al. for the vague term AI, which also includes local models, open-weight models and things that aren't LLM (machine translations, for example), thus ignoring the ethical issues associated with the operation of commercial AI/LLM services.

  • source
  • [–] 2 points 3 weeks ago

    Correct - knives do more good than harm, even when some people use them irresponsibly. My point is that AI doesn't; even when some people could arguably say that they use it responsibly and do good work, those that use it for slop, to perpetuate disinformation, and to further degrade our ability to think critically outweigh those people.

  • source
  • parent
  • context
  • [–] 12 points 3 weeks ago

    Software Developers need to learn that there is a world outside of their projects. I do not care if it makes your life easier, this technology is having worldwide impacts we are not prepared for. It's leaf blower mentality. They don't care that the neighborhood stinks like 2 stroke exhaust, they don't care that it's loud as hell, they don't care where the leaves go, their yard is clean and that's all that matters.

  • source
  • parent
  • context
  • [–] 4 points 3 weeks ago

    just because AI can find a working pattern doesn't make it good

    I have seen so much from AI supporters saying "it can be a good tool" to save time, but I'm not sure I've ever heard anyone try to make the claim that it's a tool that leads to better code. That should be very telling.

  • source
  • parent
  • context
  • [–] 3 points 3 weeks ago (2 children)

    Usually shorter. The better is the first thing to wear out, even if it's not used much. But it often can be replaced, even if the manufacturer doesn't officially support replacement.

    Ignoring that, they are still built more compact, which makes some components more prone to failure (in particular cooling). But they can still last a decade+ if taken care of and/or repaired.

  • source
  • parent
  • context
  • [–] 2 points 3 weeks ago (1 child)

    I used the github copilot tui (since that was what my subscription was through) and told it what the devices were and what I was trying to accomplish. From there it was a mixture of different things to figure out how the protocols worked, like running the apps in wine and having it log and capture data as I changed settings, or have it flip bits and I would report to it what changed. If it discovers a component in the device is something off-the-shelf, have it find reference material from the component manufacturer.

    As you figure out how a particular protocol works you have it document it until you have everything you need to build your own CLI to interface with the device. At that point you have a pretty good idea of how the device works and it's capabilities and you can build out whatever features you want around it.

  • source
  • parent
  • context
  • view more: ‹ prev next ›