Sun films have been available commercially for a long while. Choose how much sunlight you want reflected (generally more in bedrooms that you generally want dark and cool, less in rooms where you want a view), and either get a professional to apply or do it yourself—it just takes a bit of soap water and effort.
Generally better to have the sun rejection happen on the outside of the window, so as little as possible energy gets absorbed.
I’ve very barely dipped my toes in dbus before, and the option to have something else is on its face attractive (not a fan of XML and the late 90s/early aughties style of oop), but JSON for a system interface?
I mean, Kubernetes shows that yaml can work, but in this day and age I’d expect several options for serialisation, and for the default to be binary, not strings.
String serialisations are primarily for humans IMO, either as readers or writers. As writers we want something with comments (and preferably no “find the missing }” game), so for that most of us would prefer something like TOML if the data is simple enough, and actually Yaml for complexity at the level of Kubernetes—JSON manages to be even more of a PITA at that level.
But machine-to-machine? Protobuf, cap’n’proto, postcard, even CBOR should all be alternatives to examine
Yeah, JSON is essentially a side effect of having JavaScript already. It makes sense that it shows up a lot of places, especially web. But just like with JS, it’s not really good, just ubiquitous.