3 ms·
> but I think there are two really good reasons: 1) circumstances change, and 2) we have learned something Gtk has been around long enough that the boiling sho
by ryanmarsh 10y ago
> but I think there are two really good reasons: 1) circumstances change, and 2) we have learned something
Gtk has been around long enough that the boiling should have at least been reduced to a simmer by now.
- wpietri 10y agoI could well believe that. But assuming that GTK really should be at a simmer, I'd want to see an argument not for generic stability, but for areas of stability vs change. E.g., "Foo is now well understood, so that should be a stable core API. Bar, though, is an area that will keep evolving, so GTK should do A, B, and C." I'm not opposed to providing stable APIs. I just don't like the myth that if perfect people sit and think really hard, perfect software results.