Really confused by this new GTK versioning system. How do GTK+ using application authors feel? Is it clear to you?
AJ Jordan, Douglas Perkins likes this.
AJ Jordan, AJ Jordan, Douglas Perkins, Douglas Perkins and 2 others shared this.
Not sure how this will work out but Gtk+3 hasn't quite stable, deprecating API after two release, and making some replacement only available in the last version. Non-withstanding breaking theme on a regular basis. As an application developer, I can tell THIS is already bad.
Hubert Figuière at 2016-06-18T03:10:51Z
Christopher Allan Webber likes this.
I get it. What helped me is mentally replacing the numbers without dots with codenames. E.g. "GTK+ 4" becomes "GTK+ bobcat" or something. Then you can understand that basically, they treat GTK+ 4.0 as the first release of the "bobcat" series, which continues evolving until they reach the highest 4.x release, which then is finalized as the final, "guaranteed stable" "bobcat series" API. That finalization happens every two years.
That being said, it's confusing at best, braindead at worst, IMHO. So I sure can't blame you for not getting it.
AJ Jordan at 2016-06-20T08:47:46Z
Christopher Allan Webber, jrobb likes this.
Honestly, this just makes me more thankful that npm packages universally adhere to semver. Because every other scheme seems crazy (or crazier, at least).