gimp VS CppCoreGuidelines

GIMP: C, not C++

GIMP - https://gitlab.gnome.org/GNOME/gimp

GIMP

How are they implement? https://gitlab.gnome.org/GNOME/gimp https://github.com/figma

As u/schumaml said already, we have an issue tracker: https://gitlab.gnome.org/GNOME/gimp/

The former might be something you want to report as an issue at https://gitlab.gnome.org/GNOME/gimp, with the XCF file used for your cover image - or a mockup exhibiting the same issue - attached.

As Gimp is open source, I already had a look in the source code but it's written in C, which is different enough from C++ or C# that I have a rather difficult time understanding it, at least in terms of project structure. I'm pretty sure I found the handling of the tool itself in gimpoperationcolorize.c but I don't know where to go from here.

> Gotta be real, Gimp's not that far off from just one guy (https://github.com/GNOME/gimp/graphs/contributors)

GitHub only shows people with an email address linked to a GitHub account in that chart; the last time I checked it was 4 or 5 people working on it regularly, which is still a very small team (none are working on it full-time) so your point still stands (it's a point I've made myself a few times before when people compare GIMP to Photoshop or the like).

Maybe not the best example. The one on github is just a mirror of this one.

If you aren't aware of the c++ core guidelines[1] - it should be on your radar.

Also, it might not be a popular opinion, but I think Bjarne's books are just fine.

A Tour of C++ (3rd edition) [2]

Principles and Practice Using C++ (3rd Edition) was just published in april 2023 [3]

[1] https://github.com/isocpp/CppCoreGuidelines/blob/master/CppC...

You need to talk to Bjarne and Herb...

"C++ Core Guidelines" - https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines

In addition to the other comments -

TypeScript deliberately takes a "good enough" approach to improving JavaScript, instead of designing an ideal but incompatible approach. For example, its handling of [function parameter bivariance](https://www.typescriptlang.org/docs/handbook/type-compatibil...) is unsound but works much better with the existing JavaScript ecosystem. By contrast, a more academic functional programming language would guarantee a sound type system but would be a huge shift from JavaScript.

By analogy, Herb Sutter is arguing that something like the [C++ Core Guidelines](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines), with tooling help in this new Cpp2 syntax, can bring real improvements to safety. Something like Rust's borrow checker would bring much stricter guarantees, backed by academic research and careful design, but would be incompatible and a huge adjustment.

https://www.youtube.com/watch?v=2olsGf6JIkU

Take a look at Effective Modern c++ by Scott Meyers and the ISO c++ core guidelines. These resources are great for learning how to write better, more modern C++. I don't think it would be hard to grasp if you're already familiar with the language, just make sure to actually write some code which makes use of this stuff, otherwise it's easy to forget.

Look to the C++ Core Guidelines. It's not perfect, it has some flaws, including some sabotaging advice apparently adopted for political reasons. But at least it has some C++ authorities (Bjarne and Herb) as authors.