oldmangrumpy: Hi! Gimp 3.0 will be able to open any .xcf files created in 2.10, so it will be backwards compatible in that sense. Gimp 2.10 will be able to open .xcf files created in 3.0 as long as they don't use any 3.0 exclusive features (like layer effects).

oldmangrumpy, nelo: Yes, we have one more 2.10 bugfix release planned (likely in April) before 3.0 comes out. People are free to use whatever version of the software they like.
We'd also talked about compiling lists of most-used 2.10 scripts and trying to assist with porting them, though that would likely be after 3.0.

I want to make new plugins that call Gimp 2.99.19's native gegl:inner-glow and gegl:bevel and even GEGL Styles (as a dependency)


but 2.10 and 2.99.18 users won't have access to them. I can't push GEGL to new heights if I am limited to Gimp 2.10 or even 2.99.18

May 2024 is on its final two days and there is still no GIMP 3 RC1 and these days I don't feel the same passion for GIMP that I use too but I still maintain my GEGL Plugins.

My Layer Effects engine is in GIMP 2.99.19 but the casuals are still stuck on 2.99.18

well, don't give up!
I've been using GIMP since around 2001-2 when I installed Red Hat on my old laptop.

Since then I make sure to install GIMP on every Linux OS I have. Real life can often get in the way and the pandemic just made things worse.

When I have time I enjoy using GIMP. I love people like you who have worked tirelessly to make wonderful scripts, etc. I'm just here to say I appreciate your efforts.

GIMP is really important!
I'm using it all the time. I'm constantly using paths, the rectangle, etc selection tools, and most of the tools, including things like the cage tool, scale tool, the text tool, etc. e.g. to make comics captions.
AI is not as important to most users as some think. Besides, the various AI algorithms have some serious downsides, not easily fixed.
Having manual tools at our disposal is vital. I am eager for GIMP 3.
I hope, in particular, that the primitive, clunky Text Tool is improved. And that Save All, and Export All, are added.
Also, I couldn't get Python working in Gimp 2 on Win 10 (I need Windows for Daz Studio, alas, or I would use Linux, which is my goal anyway). I am hoping Python integration is easier for GIMP 3!
A massive thank you to the developers and team! Good luck!
Best,
James Eadon

DaviesMediaDesign is still saying the "once GIMP 3 releases interest in GIMP will explode" line.

I fully disasgree, if it was 2010s yes non-destructive editing would be a big deal but in the world of AI it doesn't stand a chance. GIMP's team has confirmed they will never adopt AI generation features (text to image) but a possibility of AI background removal remains though very unlikely. AI plugins will exist but they will likely be proprietary and non offline usable defeating the point of FOSS.

I totally understand you're frustration. To me, Gimp has good potential and I think there is time for it to shine but it will require a load of communication around it and creating more advance image creation with it with comprehensive guides for the tools and process. Alot of people using Gimpg as a daily professional tool. Search Gimp on Artstation to see.

But as long as gimp doesn't implement layer effect, no way in can compete. And this is a full time freelance designer using Gimp talking. Honestly, I really love gimp, and I am frustrated to see tools like Krita that implement basic stuff like layers effects in no time that should have been implemented in Gimp a long time ago regardless of the number of people working on it.

If Gimp gives to people the basic necessity, it will get more traction, and more people will donate and contribute to it. Look at Blender. It is amazing to see what it has become and I truly believe Gimp still has the potential to reach that point. I truly believe it.

Hi! You'll be happy to know that GIMP has had layer effects in the development version since February: https://www.gimp.org/news/2024/02/21/gi ... er-effects

We've made many improvements to them since then, including being able to apply them to layer groups to cover all layers within that group. We're still making changes and bugfixes as we close in on the 3.0 RC1 release, but you can try out 2.99.18 now if you'd like to see the initial implementation.

Or the latest commit to 2.99.19 which is way better.