Does GIMP have a very restrictive AI policy or something? I get not wanting to ship a gigantic pile of UI tests without thorough review, but basically any model released in the last six months would be able to write UI tests covering every single control in an afternoon.
It’s frustrating to create tests with models, not sure if it’s everyone’s experience, but every time I asked it to create tests, it makes the tests conform to the sometimes broken code. Rather than calling out what the logic/code is wrong, it will make the tests conform to whatever is already broken.
It can’t magically know expectations. If the code is well documented or there’s decent associated documentation, I’ve found it has no issue writing tests.
Tests are usually the best documentation and often the only documentation. If humans bother to write anything it should be the tests, not ambiguous human language...beyond the high level 1-liner overviews.
I'm actually surprised at how well non-frontier/local models are able to infer the intent of code from the structure, method names and sparse random comments to the point that they are capable of writing reasonable tests.
Prodding an agent vs doing interesting things with my time? What should I choose?
To be fair, some people like to prod. But, for me, I'd rather take hours reading manuals than do trial and error prodding for 30 minutes (even if I knew it would be that short). Yes it's not optimal in terms of time, but it's better for my soul and well being.
It's a good use of your time to ask the agent to reflect and update it's skills if you intervene to manually steer it. Why wouldn't you want it to learn from your guidance?
> Yes it's not optimal in terms of time, but it's better for my soul and well being.
It is also optimal in terms of time in the long run. The prodder will have to prod over and over again because he has learned nothing. You on the other hand will actually understand what is going on and will be able to either do it yourself or give precise instructions to the machine next time. Don't let yourself become a meat proxy.
The problem I've had is even when it can explain back the issue, it still writes for itself awful instructions with extra fluff, strange points of focus, and borderline misinterpretations of what I said.
Maybe that's not a big deal, they can still be generally useful, but they seem important to commit with the project if they will be used going forward. I hate the idea of a massive amount of slop riding along with the code, and slop begets slop.
The idea I'm chasing now is writing the documents myself with the hope that enough examples and a document about writing documents will be enough to allow it to write clearly.
True. It's tough useful to build non-regression tests, that is build tests that test the current behavior, assuming it correct, to possibly spot bugs in the future.
Yeah, i'm sure they want to burn their own tokens, deny others to use AI, to hog all that foss money for themselves. Definitely not related to not wanting to review 10k ai generated prs no siree
thing is, we hav emuseums, well crafted historical relics.
Having projects with properly scaffolded code, et al, will be valuable when the FAA grounds all planes for a week because of <insert all the grusome things you know this administration turns a blind eye to>.
It absolutely is related to not wanting to review 10k AI-generated PRs. Those PRs are definitely going to be lower quality and more likely to contain backdoors than ones produced by your own AI. The back-and-forth during the review is also going to be much slower than the equivalent back-and-forth in the chat window.
If money/tokens are not an issue, never accepting external AI-made PRs makes perfect sense.
Not using AI to at least writes tests in this day and age is crazy work. I started a desktop application 2 months ago and it has almost 3,000 tests now, MANY of them UI tests.
AI is a bit too excellent at writing tests. The number of tests doesn't really convey any information on test coverage. At least I've found that agents that naively improve codebases will write tests for pretty much anything, including irrelevant behavior that has little value in ensuring stability, security or correct behavior. It would probably help to run a test review stage with a strong model, where agents attempt to correct and consolidate tests to guard behavior rather than ensuring that theoretical code paths are followed.
In my experience, designing tests cases to ensure that they're othogonal and verify your invariants (domain or technical) is very mentally taxing and not something you can truly delegate. The actual typing maybe, but testing is a lot of duplicate code and you can go far with just copy-pasting stuff around and building helpers.
I my opinion, AI only changes the ease of writing these tests, not really the quality.
I find that the human written tests on my project were the same. We were guarding not just the business behavior but also weird cases that have nothing to do with business, and also self-evident cases that basically boil down to x=x or assert(true).
Not to mention the stupid side-effect of not updating mocks when the APIs move but tests don't test that part so they are okay for a lot of time, and suddenly after a non-related change they are not.
I agree, some of my small projects have had an explosion of tests. It usually doesn't cause my any problems other than waiting for tests to run, but that isn't great.
Using AI to write tests in this day and age is crazy work. The machine is great at writing tests, but the quality of the tests is awful. It will write redundant tests, it will write tests that assert too many thing in one, it will not write tests that need to be tested. It's the part where I have to clean up the most every time. Quantity is not quality, and you really don't want to skip on the quality of your quality assurance. I'm writing a React + Django full-stack application, so there should be more than enough training data out there.
They made a blog post to announce that they’d written thirteen unit tests? Sure, there’s value in handmade software and all that but GIMP is not really a particularly excellent piece of software - if anything was to benefit from unleashing the agents it would be GIMP.
Lucky you. Making things testable seemed hard to me quite often and ensuring that the tests covered all the difficult bits without effectively mocking it to death so that one was testing almost nothing.
The blog article doesn't say they have written thirteen unit tests.
> *GIMP already has unit tests*. A unit test checks one small part of the code, for example how GIMP reads an XCF file. But our unit tests were not opening a real window. So it coult not tell us if a dialog opens, or if a menu item did its job.
> Note that GIMP *already had tests of GUI code*, usually interacting directly with the core code, and sometimes even simulating input devices’ events (pointer movements, clicks, drags…). But nothing can beat interacting with the real interface. Furthermore such legacy tests directly hijacking core code come with their own problems, such as breaking all too often (and not because they detected a bug), all while not being able to detect whole categories of bugs.
> UI tests check the program as a whole, in the same way as you use it.
It'd be really interesting to look back the comparison between projects with strict non-AI policies (e.g. GIMP) and ArtCraft in 2027.
My personal prediction is that ArtCraft will blow all the old non-AI projects in similar fields out of the water and GIMP will be remembered as a thing of the past. But if I got proven wrong I'd be happy too: at least we will know the value of non-AI policies.
GIMP is far from the best FOSS image editor for many use cases. IMO for many simple editing tasks that people usually need unless they're professional photo editors, even Inkscape, a primarily vector editor, is a better photo editor than GIMP.
Inkscape is what made me believe ArtCraft would be the clear winner, btw. It's very hard to imagine using Inkscape ever again since I tried VectorCraft. (And I'm fully aware that some Path Effects can only be done quickly in Inkscape.)
Funny how GIMP spawned the Gimp Toolkit, aka GTK, which is widely used in Linux, and yet GIMP's own UI seems to have long languished as a rather outdated design. Glad that they have tests, though, and hope they continue to improve it.
Timely, as I removed Gimp from my Macbook today after successfully testing PhotoCraft [1] for a week (the AI Photoshop clone written in open-source rust which has had an absured number of updates since you last tried it).
It makes me so HAPPY to remove the dinosaur Gimp, and to run "Adobe" software for free (it's good enough for me, maybe good enough for you). I expect to lose Internet points for saying that.
I have a long history with Gimp. I created Gimpshop... the Gimp maintainers did not appreciate that little stunt, I'll tell ya! :D
I have canceled my Adobe subscription as of last month and have fully moved over to Photocraft. Even if development of Photocraft stopped today, I would be able to do whatever I need to get done in Photoshop without paying Adobe or wrestling with Gimp. It's good enough for me as well. I had been using Adobe Photoshop for more than 30 years now and was bought in enough to spend a significant amount of effort making Gimp act like Photoshop. Bye Photoshop, bye Gimp, bye Gimpshop.
Same with VectorCraft. I spent over a decade looking for an Illustrator alternative. Muscle memory and specific workflows won out. VectorCraft is extremely close.
AI bros can't stand the thought that not everyone agrees with them about LLMs. It's like a religion to them, they feel compelled to get everyone else on board. Never mind that if they are right, it will become apparent to everyone without them having to preach.
When a group of people relentlessly insist on hijacking any discussion to refocus the topic onto something unrelated but more interesting to them it stops becoming a preference and starts looking more like bullying at the hands of a religion or cult. For instance:
So why do you need to pivot every discussion about "software development process" to AI? Do you believe that the GIMP authors have not yet heard the good word? Do you think they need to be saved from their primitive non-AI practices?
There's a difference between discussion and proselytizing. And, yes, that rises to the level of bullying when AI bros relentlessly drag every discussion back to "WHY U NO AI???". It's absolutely bullying when you make it impossible to discuss non-AI related subjects.
Seriously. This comment thread is why I’m spending less time on HN and more on lobsters. All these fresh accounts losing their minds over Gimp not using ai, even when that’s not what the article is even about.
The tests should simply take a screenshot and send it to an LLM with the question "Is the UI absolutely horrible?". If the answer is yes then the UI is working as expected.
I created all the designs for flyers, announcements, invitations etc. in Affinity for my wife. I migrated to Linux and didn't like any of the apps. I was lost.
Then Affinity announced they'll add Linux support.
But for some time now my wife just uses Codex/Claude to do her day-to-day nothing special design work.
I feel, just like ArtCraft, Gimp will not be relevant in some years (months?).
Are you me?! I've also happily used GIMP for that long, just swap out Affinity for Paint Shop Pro or Adobe CS. I would probably feel just as lost going back to them now.
There are people who want to use Gimp (or Affinity etc), and there are people who want to have used Gimp. It’ll only lose relevance for the second group.
rafram | 19 hours ago
Does GIMP have a very restrictive AI policy or something? I get not wanting to ship a gigantic pile of UI tests without thorough review, but basically any model released in the last six months would be able to write UI tests covering every single control in an afternoon.
samuria | 19 hours ago
Waterluvian | 19 hours ago
t43562 | 15 hours ago
alyandon | 7 hours ago
forgotmypw17 | 19 hours ago
Prod your agent first until it can explain back to you what's wrong with the tests.
Then ask your agent to write a better prompt for writing tests (and save it to an .md file)
Then reference that .md file and iterate on the tests again. It may take a couple of tries, but I've had good results with this strategy.
Ended up with a whole prompting framework.
skydhash | 18 hours ago
To be fair, some people like to prod. But, for me, I'd rather take hours reading manuals than do trial and error prodding for 30 minutes (even if I knew it would be that short). Yes it's not optimal in terms of time, but it's better for my soul and well being.
0xcoffee | 18 hours ago
thisismyanon2 | 16 hours ago
HiPhish | 17 hours ago
It is also optimal in terms of time in the long run. The prodder will have to prod over and over again because he has learned nothing. You on the other hand will actually understand what is going on and will be able to either do it yourself or give precise instructions to the machine next time. Don't let yourself become a meat proxy.
doginasuit | 18 hours ago
Maybe that's not a big deal, they can still be generally useful, but they seem important to commit with the project if they will be used going forward. I hate the idea of a massive amount of slop riding along with the code, and slop begets slop.
The idea I'm chasing now is writing the documents myself with the hope that enough examples and a document about writing documents will be enough to allow it to write clearly.
hulitu | 18 hours ago
It is the same like humans: if they say your code is wrong, you will hire someone else who doesn't find so many bugs. It doesn't look good.
alerighi | 15 hours ago
deskglass | 19 hours ago
einichi | 18 hours ago
lukeify | 17 hours ago
> Of course, core developers don't need to check this monotomous checklist. This is only useful for the newcomers.
So this is saying core devs already know not to use AI, only new developers shouldn't.
It's quaint at this point. Embrace the future.
Xirdus | 17 hours ago
desterothx | 15 hours ago
cyanydeez | 10 hours ago
Having projects with properly scaffolded code, et al, will be valuable when the FAA grounds all planes for a week because of <insert all the grusome things you know this administration turns a blind eye to>.
Xirdus | 3 hours ago
If money/tokens are not an issue, never accepting external AI-made PRs makes perfect sense.
6wf9j | 9 hours ago
Or is it just me?
stratos123 | 15 hours ago
jasonvorhe | 11 hours ago
locusofself | 18 hours ago
timcambrant | 18 hours ago
skydhash | 18 hours ago
aidenialislife | 18 hours ago
npteljes | 12 hours ago
I find that the human written tests on my project were the same. We were guarding not just the business behavior but also weird cases that have nothing to do with business, and also self-evident cases that basically boil down to x=x or assert(true).
Not to mention the stupid side-effect of not updating mocks when the APIs move but tests don't test that part so they are okay for a lot of time, and suddenly after a non-related change they are not.
locusofself | 6 hours ago
ares623 | 18 hours ago
mepiethree | 17 hours ago
Gimp has millions of downloads this month. They are doing something right.
HiPhish | 17 hours ago
byronturncoat | 10 hours ago
hulitu | 18 hours ago
Microsoft also seems to use "models" to "test" its programs. Look how shitty they are.
rafram | 6 hours ago
nomilk | 18 hours ago
masfuerte | 7 hours ago
joegibbs | 18 hours ago
Jolter | 18 hours ago
hulitu | 18 hours ago
AI can write tests now ? For its own software ? Can it evaluate the results ? Correctly ? /s
aidenialislife | 18 hours ago
t43562 | 15 hours ago
desterothx | 15 hours ago
altmanaltman | 18 hours ago
> *GIMP already has unit tests*. A unit test checks one small part of the code, for example how GIMP reads an XCF file. But our unit tests were not opening a real window. So it coult not tell us if a dialog opens, or if a menu item did its job.
> Note that GIMP *already had tests of GUI code*, usually interacting directly with the core code, and sometimes even simulating input devices’ events (pointer movements, clicks, drags…). But nothing can beat interacting with the real interface. Furthermore such legacy tests directly hijacking core code come with their own problems, such as breaking all too often (and not because they detected a bug), all while not being able to detect whole categories of bugs.
> UI tests check the program as a whole, in the same way as you use it.
[OP] qtqtqt | 18 hours ago
WD-42 | 18 hours ago
[OP] qtqtqt | 18 hours ago
slopinthebag | 18 hours ago
raincole | 18 hours ago
My personal prediction is that ArtCraft will blow all the old non-AI projects in similar fields out of the water and GIMP will be remembered as a thing of the past. But if I got proven wrong I'd be happy too: at least we will know the value of non-AI policies.
flexagoon | 16 hours ago
raincole | 16 hours ago
t43562 | 15 hours ago
plant-ian | 17 hours ago
dllu | 18 hours ago
alexey-salmin | 18 hours ago
veltas | 17 hours ago
yjftsjthsd-h | 17 hours ago
> GTK is a free and open-source project maintained by GNOME and an active community of contributors.
and
> GTK and the GTK logo are trademarks of the GNOME Foundation.
YuechenLi | 18 hours ago
ModernTimes | 18 hours ago
It makes me so HAPPY to remove the dinosaur Gimp, and to run "Adobe" software for free (it's good enough for me, maybe good enough for you). I expect to lose Internet points for saying that.
[1] https://getartcraft.com/apps/photocraft
Aozora7 | 18 hours ago
plasticbugs | 18 hours ago
I have canceled my Adobe subscription as of last month and have fully moved over to Photocraft. Even if development of Photocraft stopped today, I would be able to do whatever I need to get done in Photoshop without paying Adobe or wrestling with Gimp. It's good enough for me as well. I had been using Adobe Photoshop for more than 30 years now and was bought in enough to spend a significant amount of effort making Gimp act like Photoshop. Bye Photoshop, bye Gimp, bye Gimpshop.
hackshack | 17 hours ago
TeddyDD | 15 hours ago
fuussssip | 18 hours ago
I'm surprised, tbh. I understand that UI is very much an afterthought in GIMP, but I figured it'd still at least have tests.
slopnt | 6 hours ago
aquafox | 18 hours ago
fishgoesblub | 17 hours ago
bigstrat2003 | 17 hours ago
Aozora7 | 16 hours ago
Besides, GIMP has always been unpopular long before AI.
thisismyanon2 | 15 hours ago
Hey we added UI tests to GIMP
AI bros: YOU SHOULD HAVE USED AAAAAAAAAIIIIIIIIII
This is more complex than a few unit tests
AI bros: YOU SHOULD HAVE USED AAAAAAAAAIIIIIIIIII
Can we please discuss GIMP?
AI bros: STOP PERSECUTING US
Aozora7 | 15 hours ago
thisismyanon2 | 15 hours ago
There's a difference between discussion and proselytizing. And, yes, that rises to the level of bullying when AI bros relentlessly drag every discussion back to "WHY U NO AI???". It's absolutely bullying when you make it impossible to discuss non-AI related subjects.
npteljes | 12 hours ago
I also hated the UI, coming from Photoshop, but what I found is that when I go back to Photoshop, I'm just as lost as I was before switching to Gimp.
I'm glad that they hadn't lost their courage over the years. Gimp is a solid project, and the FOSS ecosystem would lose a real gem if they stopped.
WD-42 | 8 hours ago
snissn | 17 hours ago
iLoveOncall | 16 hours ago
zkmon | 16 hours ago
It feels good when I see spelling mistakes. It feels organic, human-sourced, non-AI. It feels like a good old village again.
BTW I love GIMP for everything it did to the world of graphics work. Such an awesome thing. Thank you folks.
KingOfCoders | 16 hours ago
Then Affinity announced they'll add Linux support.
But for some time now my wife just uses Codex/Claude to do her day-to-day nothing special design work.
I feel, just like ArtCraft, Gimp will not be relevant in some years (months?).
bayindirh | 16 hours ago
It's a matter of getting used to things. I feel lost in Affinity tools, for example, despite having a license, I use them less and less.
JamesLeonis | 9 hours ago
mcv | 16 hours ago
cissikatt | 9 hours ago
inbalboa | 16 hours ago
KingOfCoders | 12 hours ago
skrebbel | 16 hours ago
mamouri | 15 hours ago
gauntr | 15 hours ago
grim_io | 14 hours ago
stuaxo | 8 hours ago
So much of this tech like ui tests was built for the web, and it can be a pain to get working for plain old GUI apps