> The majority of printing processes today are performed using different
> coloured pigments. However, there’s another type of colour called structural
> colour, which typically uses nanoscale structures that interact with light
> to produce a colour.
Doesn't the pigment act as ("natural") nanoscale structure as well?
Yeah, first I thought this is just a BeOS-inspired GUI theme, but there is more to it:
Nexus is Vitruvian's custom Linux kernel subsystem that brings BeOS-style
node monitoring, device tracking, and messaging to Linux — making it
possible to run Haiku applications on a standard Linux kernel.
Yes that's the best use of waste (next to not producing the waste in the first place). Also, those powerplants are usually combined type of powerplants which make them highly effective, i.e. they are producing both heat and electricity.
Nordics countries generally need lot of heating because of cold climate, which in cities is typically district heating, i.e. delivering the heat as hot water from big heating plants. Heat pumps are also very popular (air-to-air, air-to-water, geothermal).
For example, my house is entirely heated with 3 heat pumps, even in -25°C. From April to September 10 kW solar panels provide the most of energy, also charging my Tesla.
The rest of Europe needs an energy reform. They should take the Nordics countries as an example, where household usage of gas is very minimal / non-existent and everything is electricity based (electricity being the cleanest in the world). They are also leading the EV adaptation by big margin.
The old JS Date API is far from perfect and I'm happy it being replaced, but part of the problem is various string-based formats and people being sloppy using them. Not to mention general complexity in time/date concept with timezones, summer time, leap seconds, etc.
For string format, just stick with ISO 8601. If you need to parse less-standard formats, use a robust library of your choise. The standard library should not try to support parsing zillion obscure formats. Outputting localized / human-readable format should be a responsibility of localization API anyway.
I also think that many libraries/APIs involving formatting things have some US centric design limitations, i.e. tendency to treat US formats as native and international support is often a bit after-thought. Especially with older stuff like the JS Date API.
LFP is so cheap that small-scale thermal battery makes not sense for electricity generation. Even in big scale (like OP) it mostly makes sense for heat, e.g. district heating systems, industry process heat, etc.
That's an excellent example of those seemingly minor but annoying issues which seems to be hard to get right without a complete control of the software-protocol-hardware stack (like Apple has). Also, that's the reason many are more than happy to pay Apple the "premium".
Complex consumer standard implementations tend to be "buggy", that's how economy works. More robust implementation after "it mostly works" level would give diminishing returns for average consumer product company.
> However, in the context of the web (the client/server boundary), I think we need to be careful about how messaging is used. The web is made up of resources with URLs. HTTP is typically used for data transfer, and for good reason.
"Careful" == do not break urls, use pushState and make sure equivalent document is returned for GET.
Doesn't the pigment act as ("natural") nanoscale structure as well?