[–] 2 points 6 days ago

I dont know what you mean by that. Do you mean that the NSA would leave a bug in accidentally? Or intentionally?

Accidentally is definitely plausible, they are only human after all.

Intentionally would be incredibly stupid. The offensive side of the NSA spends billions developing malware that can't be easily found and attributed to them. Inserting one of those malwares into a piece of software they have publically claimed ownership off completely defeats the point. If they wanted to backdoor an open source software, why wouldn't they do it anonymously...

  • source
  • parent
  • context
  • [–] 11 points 6 days ago (12 children)

    Ghidra is used by the best and brightest malware inspectors. If it was backdoored, it would have been discovered almost immediately.

    The NSA has two conflicting missions, one is to hack everyone, and the other is to protect American networks and interests. Ghidra is from the later, its goal was to make malware analysis cheap and accessible so that more people can investigate and defeat malware.

  • source
  • [–] 24 points 6 days ago

    With Open Source software, I need a reason not to trust it. With proprietary software, it's the other way around. Developer being the NSA has been a reason for me not to trust Ghidra.

  • source
  • [–] 19 points 6 days ago (1 child)

    IMO the most important part of open source is the Ulysses pact called "right to fork". It's like the developer says "if I ever become a tyrant, you have an easy way out of my tyranny".\ That's what makes me trust it more than closed source. Not Linus' Law.

  • source
  • [–] 3 points 6 days ago* (last edited 6 days ago)

    I think also, people forget that open source projects need maintainers who are properly invested.

    It's difficult to imagine a meaningful future for a codebase that you spun up with AI and don't actually understand yourself.

    There's an expectation of stewardship beyond "yeah I spent 2k on tokens"

  • source
  • parent
  • context
  • [–] 4 points 6 days ago* (last edited 6 days ago) (2 children)

    Believing these apps will succeed is based on an assumption along the lines of LLMs being able to produce quality code at 100x the speed of a competent human engineer. Maybe they can produce slop that fast, but using LLMs in a disciplined fashion to produce a quality product usually means LLMs are only providing a modest productivity boost in my experience.

    It’s not realistic that these apps are anything but slop given the timeframe and scope spanning multiple complex apps that each took a decade or more to develop.

    In my 20+ years of experience as a software engineer, I’ve never seen a successful project that hastily pumped out a massive pile of buggy code and then went back and fixed all of the problems later without doing a complete rewrite. You have to build incrementally and bake in quality every step of the way. LLMs may make the process a little faster, but the same rules still apply.

    A poorly built codebase will always eventually collapse under its own weight. What I anticipate is that they’ll play whack-a-mole for a while and then give up. If they were targeting a small subset of one app’s features over a timeframe of months, I might believe it, but several massive apps all at once and it will all be done weeks from now? Stop bullshitting yourselves.

  • source
  • [–] 1 point 6 days ago* (last edited 6 days ago)

    "Guide" is doing a lot of heavy lifting there. There's an infinity of difference between asking an AI to make something and using an AI to do the scutt work, looking over the code it made, running IRL tests, asking "why X? Why not Y?", swearing at it like a junior dev, asking it to fix a,b,c then finally getting acceptable code.

    And even with all that - when you set it up correctly - it's still faster than doing it yourself (in certain circumstances).

    It feels more like doing project management / "software engineering" than clacking the keys. It's amazing how different LLMs approach the same task though; I find Codex to be much more by the book than Claude, for example. The Qwen's are like Labradors - eager to please, clumsy, crash into things a lot. GLM and Kimi are different again. Etc.

    You can't let anything just "make me X, make no mistakes". By the time you type in a ticket (with GO/NO GO gates, acceptance criteria etc) you might be looking at 500-1000 lines of text (which is why a re-usable template and procedures are important). You need repeatable procedures, acceptance tests - the lot.

    And so it goes.

  • source
  • parent
  • context
  • [–] 1 point 6 days ago*

    Those damn woke ipad kids with their programming languages and being who they are and being unashamed of being gay, how could you possibly let them be themselves?

    before anyone misconstrues i'm literally gay and making fun of Lunduke

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