Remix.run Logo
▲ rafram 3 hours ago

> We have 13 tests at this time.

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.

▲deskglass 3 hours ago | parent | next [-]

Turns out you're right! No AI allowed https://gitlab.gnome.org/GNOME/gimp/-/blob/master/.gitlab/me...

▲einichi 2 hours ago | parent | next [-]

> for contributors without Developer role

▲lukeify an hour ago | parent [-]

From the blame PR:

> 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 an hour ago | parent [-]

The future seems to be blocking external contributors and running the equivalent AI agents yourself.

▲echelon 2 hours ago | parent | prev [-]

Meanwhile I'm watching a community of hundreds of agents reworking game engines and chat apps. And it's progressing fast.

You have to serve users, not hold code up as a sacred relic.

Our own DNA was vibe coded. It's a mess. Stochastic hill climbing can get pretty far, and it can reach surprising fitness.

▲fuussssip an hour ago | parent | next [-]

It's ok to have principles. Some folks have extremely valid reasons to hold a hard no stance on AI. It's not me, but I respect that position as principled, logical, and reasoned. Just a very different set of values from me.

▲lukeify an hour ago | parent | next [-]

At this point it's like the Amish. Sure I can respect their principles, but at the same time I find it bloody bizarre.

▲fuussssip 11 minutes ago | parent | next [-]

I liken it to my vegetarianism. I'm not morally against eating animals. I have no religious convictions about it either. I just look at factory farming and think "that seems like torturing animals at scale to me" and choose to not participate.

The people looking at AI and taking a "none for me thanks" stance are looking at externalities and saying they don't like them, and they dont like them enough to not participate.

▲Xirdus an hour ago | parent | prev [-]

But there's no denying Amish food is much healthier and higher quality than regular store bought products (with some exceptions I guess).

▲alex43578 an hour ago | parent [-]

But there’s a dozen other invisible tradeoffs. It’s not a simple binary. The Amish don’t have their own grapes year round, for instance. The Amish would need to dedicate a major percentage of their population to farming, given the drastically lower productivity.

Our food supply has perfectly healthy options. People choose to buy and eat junk, then blow up to 400lbs. You can gild the lily by arguing over organic vs Amish-grown in terms of micronutrients and traces of pesticides, but even an inorganic ear of corn is 10x healthier than what the average American eats.

▲HlessClaudesman an hour ago | parent | prev [-]

If you start with the assumption that AI is the devil, than rejecting the devil and all the fruit he offers is logical.

If you start with the assumption that AI is a tool, then finding uses for the tool is logical.

Seems to me that some people really love riding a purity spiral, and collectively they have chosen a new tool to fill the role of the impure thing to be cast out.

▲fuussssip 14 minutes ago | parent | next [-]

I think you aren't being thoughtful enough.

Someone can believe AI was trained on material in a way that violated the consent of authors and artists and musicians. Someone can see the value of the tool, but not want that value to be primarily captured by megacorps. One can believe that the tool is having a deleterious effect on students, workers, and artists of all kinds, as it's being deployed. One can't be concerned about the added environmental effects, the impact to world markets, or the shortages it causes to consumer hardware. One can be worried about the copyright implications (can AI produce copyrighted material?) and not want to risk losing their IP. One can believe that art is necessarily a human enterprise, and art produced mechanically is just images and sounds, but not art nor music.

None of these are "the tool is the devil". All of these are "the tool has externalities, and those externalities come with a cost I am not comfortable paying".

I'm a vegetarian. Not because I think eating meat is immoral, but because I believe factory farming causes undue suffering to animals and the people who raise and process those animals. So I make a choice for myself, in my own life, and don't moralize to others.

It's the same thing. Some folks are making choices for their own lives based on their values for those externalities. You value energy use differently than they do. You value art differently than they do. You value corporate control over communications differently than they do. Neither of you is right, but standing here and pretending an eminently justifiable difference of opinion is just purity signaling is boorish.

▲Xirdus an hour ago | parent | prev [-]

From what I've seen, it's less spiritualism and more "they're taking our jobs!" kind of fearmongering. Like all "taking our jobs" fears, whether it's logical or not depends purely on whether they're actually taking these jobs or not.

▲bigstrat2003 43 minutes ago | parent | prev | next [-]

> You have to serve users, not hold code up as a sacred relic.

They are serving users, by not allowing AI slop. Software developed by people and not an LLM is of much higher quality, and I'm glad they are taking a stand.

▲ngruhn an hour ago | parent | prev | next [-]

At least DNA has a reward signal to clean up tech dept. Everything is use-it-or-loose-it. Don't use your eyes because it's always dark? Bye bye. Claude would maintain that as a fallback for all eternity.

▲globular-toast an hour ago | parent | prev | next [-]

It wasn't vibe coded, it evolved over millions of years. And we ended up with our eating hole right next to our breathing hole because there's no way up back out of that "decision".

▲mepiethree an hour ago | parent | prev | next [-]

Does free open source software “have to” serve users? You clearly aren’t the user they’re trying to serve. That’s okay though; there’s something for everyone.

▲keybrd-intrrpt an hour ago | parent | prev [-]

> Our own DNA was vibe coded.

No, that was Reinforcement Learning

▲adastra22 an hour ago | parent [-]

Neither, if we really want to get technical. RL is directed whereas evolution is not.

▲samuria 3 hours ago | parent | prev | next [-]

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.

▲forgotmypw17 3 hours ago | parent | next [-]

I recommend iterating on your prompts.

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.

▲doginasuit an hour ago | parent | next [-]

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.

▲skydhash 2 hours ago | parent | prev [-]

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.

▲HiPhish an hour ago | parent | next [-]

> 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.

▲0xcoffee 2 hours ago | parent | prev [-]

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?

▲Waterluvian 3 hours ago | parent | prev | next [-]

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.

▲hulitu 2 hours ago | parent | prev [-]

> Rather than calling out what the logic/code is wrong, it will make the tests conform to whatever is already broken.

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.

▲locusofself 2 hours ago | parent | prev | next [-]

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.

▲timcambrant 2 hours ago | parent | next [-]

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.

▲skydhash 2 hours ago | parent [-]

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.

▲aidenialislife 2 hours ago | parent [-]

Designing for testing helps as well. Pure functions for core logic, coding against interfaces etc.

▲HiPhish an hour ago | parent | prev | next [-]

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.

▲ares623 2 hours ago | parent | prev [-]

Look, guys, you are literally allowed to fork and go ham on the code.

▲mepiethree an hour ago | parent [-]

Yeah if people can make a better and more popular Gimp in an afternoon, go do it.

Gimp has millions of downloads this month. They are doing something right.

▲maskofthesea7 28 minutes ago | parent [-]

[dead]

▲nomilk 2 hours ago | parent | prev | next [-]

This raises questions of AI ethics; namely, is it conscionable to subject AI to GIMP’s UI?

▲hulitu 2 hours ago | parent | prev [-]

> any model released in the last six months would be able to write UI tests covering every single control in an afternoon.

Microsoft also seems to use "models" to "test" its programs. Look how shitty they are.