4 ms·

I believe you haven't tried to make contributions to something like gtk, especially the ones they have no roadmap item for. Modern big open source projects are

by wruza 3y ago

I believe you haven't tried to make contributions to something like gtk, especially the ones they have no roadmap item for. Modern big open source projects are an entangled mess of subsystems, dependencies, opinions and sometimes plain ego, so even if you're able to program the library, there's little chance to get the change accepted into mainstream, and there's no chance you'll be able to maintain a whole parallel distribution which would make this change effective at least for you. With years I learned that this claim: they owe you nothing, and nothing was stopping you from contributing your own improvements lands inside the [ignorance..rudeness..hypocrisy] triangle most of the times. It would be more agreeable if stated as: they owe you nothing, and nothing was stopping you from contributing approved improvements from their backlog

superkuh 3y ago
The paid gtk devs refuse to accept patches to gtkfilechooserwidget.c (it's "frozen"), you'd know this if you yourself tried to make contributions to gtk. They owe us nothing, but the fact remains they have been removing features (like respecting the gsettings (org.gtk.Settings.FileChooser location-mode) that would allow users to fix this bug). And they refuse to fix it themselves or look at patches from others. I ask once per year. Even just 2 lines in gtk/gtk/gtkfilechooserwidget.c swapping in priv->location_mode = LOCATION_MODE_FILENAME_ENTRY; would help. The same bug exists in gtk4 too and they also refuse to fix it there. https://gitlab.gnome.org/GNOME/gtk/-/issues/5872 https://gitlab.gnome.org/GNOME/gtk/-/issues/5872 So, to conclude, everything you said is wrong re: this specific instance even if it may apply generally.
- wruza 3y ago
  I'm a little confused whether your comment is the answer to mine or someone elses, cause we seem to agree on all points. In any case, I left G* lands ages ago (gtk2->3) and can only speak for that time. It coincided with the issues around their development policies.
  - superkuh 3y ago
    Ah, I didn't realize the italics were you quoting parent. woops.
PaulDavisThe1st 3y ago
> Modern big open source projects are an entangled mess of subsystems, dependencies, opinions and sometimes plain ego Do they differ in this respect from "Modern big proprietary projects" ?
- wruza 3y ago
  No, why?
  - PaulDavisThe1st 3y ago
    Then why single out "open source" ? If this is a characteristic of "modern big software projects" then it has nothing specifically to do with whatever happens or doesn't happen in open source development.
    - wruza 3y ago
      But you can't send patches to closed source projects by definition. So I see it as the scope of this discussion, not as singling something out.

by wruza 3y ago

superkuh 3y ago

The paid gtk devs refuse to accept patches to gtkfilechooserwidget.c (it's "frozen"), you'd know this if you yourself tried to make contributions to gtk. They owe us nothing, but the fact remains they have been removing features (like respecting the gsettings (org.gtk.Settings.FileChooser location-mode) that would allow users to fix this bug). And they refuse to fix it themselves or look at patches from others. I ask once per year. Even just 2 lines in gtk/gtk/gtkfilechooserwidget.c swapping in priv->location_mode = LOCATION_MODE_FILENAME_ENTRY; would help. The same bug exists in gtk4 too and they also refuse to fix it there. https://gitlab.gnome.org/GNOME/gtk/-/issues/5872 https://gitlab.gnome.org/GNOME/gtk/-/issues/5872 So, to conclude, everything you said is wrong re: this specific instance even if it may apply generally.

wruza 3y ago
I'm a little confused whether your comment is the answer to mine or someone elses, cause we seem to agree on all points. In any case, I left G* lands ages ago (gtk2->3) and can only speak for that time. It coincided with the issues around their development policies.
- superkuh 3y ago
  Ah, I didn't realize the italics were you quoting parent. woops.

PaulDavisThe1st 3y ago

> Modern big open source projects are an entangled mess of subsystems, dependencies, opinions and sometimes plain ego Do they differ in this respect from "Modern big proprietary projects" ?

wruza 3y ago
No, why?
- PaulDavisThe1st 3y ago
  Then why single out "open source" ? If this is a characteristic of "modern big software projects" then it has nothing specifically to do with whatever happens or doesn't happen in open source development.
  - wruza 3y ago
    But you can't send patches to closed source projects by definition. So I see it as the scope of this discussion, not as singling something out.