2019: "Our incredibly fragile tools only work with one micromanaged theme nobody likes. Please take systems integration advice from webshit design nerds because branding"
- via @firstname.lastname@example.org
Damn I didn't read something this stupid since so long it's worth loosing time replying.
- The UI toolkit is GTK, hence C.
- CSS was and still is a right choice: it's a well defined specilized language that which benefit theme maintainers greatly, there is no point reinventing the wheel.
- When you develop an application you very often have to create new specilized widgets, and sometimes you need to style and the styling machinery may not provide all the tools you need, so you have to adjust your custom style extensions to the themes you are targetting. You can't support all the themes the next season's fashion will make distros ship by default.
- Breaking apps downstream and sending issues upstream to fix our downstream quirks is a no go. Sending our users to complain upstream is even worse.
Also: please don't call some of the finest developers and designers I know "webshit design nerds". If you don't understand an issue, STFU, lurk moar, and don't insult persons who actually studied an issue and try to fix a broken status quo.
@KekunPlazas do you feel better now, after ranting 6 posts into my notifications in response to a joke
1) GTK haven't manpower to maintain theming API (or is it a decision by design?)
2) Some GNOME developers keep spreading that CSS stylesheet can be used to provide third party themes that users or distro can apply
3) Some GTK apps developers complain for CSS stylesheet abuse
Maybe 1) could be made clear so users, app developers and distro that want theming will know that they have to use another toolkit, like Qt?
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!