[–] 4 points 1 month ago* (last edited 1 month ago) (2 children)

Appreciate the honesty and reply.

Finding your PS aggressive myself, especially since I tried to scrub my comment free of aggression. Definitely failed on that. This is a very charged and hot-button topic for me. Sorry.

Probably going to abandon this account and become @andioop@piefed.social or piefed.zip, because they have a nice filter on posts and I'll use it so I can actually browse programming.dev without having to see the many, many LLM and AI and vibe-coding posts and comments (whether for or against) that clearly get me upset and unable to communicate in a way that people are okay with. (Well, maybe it can't filter out the comments, I forget, but I know it does posts.)

Thanks for not getting into personal insults despite not liking my comment. It's one thing I really don't like that Fedi often does.

(my goal: trying to express my frustration too, I'd feel like a pushover if I did not and just swallowed it. But also trying to de-escalate the situation and learn from how I still came across aggressive to you, because I have always gotten along with people and making anyone feel bad is generally something I'd like to avoid.)

  • source
  • parent
  • context
  • [–] -1 points 1 month ago

    Yeah, that’s a bit much.

    Why.

    We've mechanized this process. Doing it repeatedly, and quickly, is what that looks like.

    This isn't a decomp searching for exact compiler output. Function-for-function means, there is a Gaussian blur filter, and it responds to the same shortcut and settings. It's not bit-for-bit identical. Is that supposed to take a month, by itself? Why wouldn't this move very quickly, once the most important functions are good enough?

  • source
  • parent
  • context
  • [–] 5 points 1 month ago (1 child)

    "Sorry, not buying that" is just brushing aside that they say they did exactly what you asked for.

    They can say lots of things. I don't believe everything I'm told. Do you?

    What is so unthinkable about producing compatibility with a file format that has a test suite?

    Nothing - that's something I can believe.

    Or cloning any particular feature from a high-level description and a screenshot of its dialog?

    Any particular feature? No problem. The entire software suite function-for-function in just a few weeks? Without "cheating?" Yeah, that's a bit much.

  • source
  • parent
  • context
  • [–] -2 points 1 month ago* (2 children)

    Yes you plainly did. "Sorry, not buying that" is just brushing aside that they say they did exactly what you asked for.

    What is so unthinkable about producing compatibility with a file format that has a test suite? Or cloning any particular feature from a high-level description and a screenshot of its dialog?

  • source
  • parent
  • context
  • [–] 43 points 1 month ago (4 children)

    Yeah, the guy that just released all Adobe products a week ago that barely work, surely releasing another suite of tools next weekend instead of fixing the plethora of bugs is a good sign that he is capable to keep maintaining a project in long term.

    I did try the PhotoSlop, and within the like 20 minutes I couldn't make the canvas the size I asked for, the work (mostly trying random stuff, but that's not the point) did not get saved when I saved it, and it froze when I alt-tabbed, so I lost all of it.

    I'm sure it's getting them a lot of attention, but why would I use anything of his when he got bored with it and moved to another project in literally a week while it has absolutely blocker issues?

  • source
  • [–] 8 points 1 month ago* (last edited 1 month ago) (3 children)

    I didn't say anything of the sort. We all know AI code isn't original, and for the purposes of this discussion, that's fine.

    My issue is the idea that he's replicated virtually every last detail of several major closed-source apps simultaneously in under a month using documented specs alone without "cheating" by using their code in some manner. Plain and simple. Prove me wrong, and I'll issue a mea culpa.

  • source
  • parent
  • context
  • [–] 12 points 1 month ago (2 children)

    Neoliberalism sure has poisoned our minds.

    Despite what bosses and market pundits will tell you when they’re trying to underpay you, the value in a software development effort is not just the end product that you can sell to customers — it’s also the knowledge of how the codebase works, and how to modify it over time.

    I’m not an ostrich when it comes to AI-powered development. I’ve been to multiple conferences and courses over the past year specifically about developing with AI. My Youtube and Substack and podcast history is multiple hours per day of content about AI news, practices, and opinions. My weekly visit to my bookstore has been mostly to pick up or place an order for books about AI. I use agents for my daily coding tasks at work. I have multiple local LLMs on multiple machines at home that I use from multiple harnesses. I have ralph loops, I have full-AFK workflows, I have custom sandboxes.

    I could go on, but you get the point: I’m not standing on the sidelines when I say…

    The vast majority of AI use today is horrifically irresponsible. Current AI use is digital asbestos in the walls of our technological society. It will take generations to fully recover from this. I am not excited, I’m not gonna “get over it”, and I’m not gonna grant any degree of false equivalence between actual FOSS and these slop stunts.

    The bubble cannot pop soon enough. Not just so that we can minimize the economic damage, or so that hardware prices can once again experience gravity, but so that we can actually be honest about what this stuff is and how to use it.

  • source
  • parent
  • context
  • [–] 11 points 1 month ago* (last edited 1 month ago) (5 children)

    Which brings us full circle to not original code, but I get that's par for the course with AI. However, I can't see completing all those apps - with full compatibility - in that time span with nothing but documented specs (especially nowadays when full documentation has long become an afterthought that never becomes reality far too often).

    Sorry, not buying that there wasn't decompiling involved. Dude needs to prove his "work" by releasing every detail of how he accomplished it so others can replicate it before I'll eat my words. And he needs to do so now - so current tools, hardware, etc can be validated by Joe Public.

  • source
  • parent
  • context
  • [–] 10 points 1 month ago

    Yup. Experienced it myself. Had a manufacturer who used Linux drag their feet at releasing certain kernel module sources (even though the binary clearly states they're GPLv2).

    Threw Claude at it and overnight it managed to reconstruct most of the modules, instruction for instruction, even throwing in a few bugfixes for free...

  • source
  • parent
  • context
  • [+] -7 points 1 month ago (6 children)

    This project is weeks old. I dunno what detailed writeup you expect to exist. But the project's Github page says: "Implemented from public specs and observed behaviour only. No proprietary code, shaders or assets."

    There's no secret sauce in Photoshop. Image editors have been done. Every individual feature is a tractable problem. You can now buy your way out of those, in bulk.

  • source
  • parent
  • context
  • [–] 11 points 1 month ago* (last edited 1 month ago)

    Yes, yes. It's common knowledge that passwords magically become unsafe after a period of time and need to be changed. It's the same with certificates. Sadly, there is no way of revoking them when the secret becomes compromised, so reducing the validity time is the only way out. Yes, yes.

    Seriously: gladly there is a the acme client to automatically renew certs. In most of the cases. (Good luck with appliances that don't provide automatic cert renewal though. :)

  • source
  • [–] 13 points 1 month ago* (last edited 1 month ago)

    I'm with you on your first paragraph - unless we're doing some pioneering work, we learn it from somewhere.

    But the possibility of decompiling means you don't have to have access to the source just so long as you can access the code is some form - including the generated executable.

  • source
  • parent
  • context
  • [–] 14 points 1 month ago* (last edited 1 month ago) (7 children)

    May I ask where this is documented? I tried searching, but there's just too many results to parse, and/or my Google-fu is failing me.

    I find it hard to believe near full feature parity could be achieved in under a month for multiple major apps even for an experienced dev using AI. It's a bit hard to buy.

  • source
  • parent
  • context
  • [+] -13 points 1 month ago (3 children)

    Right, because clean room means you've never seen any code in your life.

    People - spicy autocomplete was not going to derive C from first principles. Neural networks are example-based. The model still obviously never saw Photoshop's source code, because that shit's not on Github.

  • source
  • parent
  • context
  • [–] 1 point 1 month ago (5 children)

    I just ask because NetBSD is the only “real” operating system that has an anti LLM policy. Linux/Gentoo has A LOT of LLM assistance. Linux has litterally thousands of LLM assisted commits per minor release.

    I don’t know if it runs on NetBSD or not. I only asked because I though you might have been a “no LLM assisted software” person.

  • source
  • parent
  • context
  • [+] -10 points 1 month ago (8 children)

    Clean room implementation would be taking the spec, API calls, etc. & writing the code that implements them from scratch.

    Which they did.

    This is not a decomp. They gave the tool all of the available specs, and the expected behavior, and let it run. They had a suite of test PSD files but no Adobe software.

    Please explain to these other commenters how and why that counts.

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