hurrrrr

Numpy has masked arrays [1]. Though I can't say how well they work.

[1] https://docs.scipy.org/doc/numpy/reference/maskedarray.gener...

downsides: can't move really far when plugged into stationary device, breaks a lot (at least for me it's almost always the plug or cable that breaks), cable picks up random noise

upsides: my very old thingamajig with a broken display doesn't support anything else

raises hand not with gui but with cli.

Autocompletion stops early because 'SomeReallyLongSourceName.h' and 'SomereallyLongSourceName.cpp' are not the same after the fifth letter. It breaks globbing.

gcore creates dumps and you could do periodic dumps via cron. But performance triggers aren't easily possible afaik.

They all seem to be consistently wrong. The series is shifted by 1.

There is no "we trade districts and both profit" scenario (apart maybe cutting out 3rd parties that have no chance of winning anyway). If they trade one gets the strictly better deal, the other loses.

Human factor and stupidity excluded.

From what I heard buildup on the panels isn't that big a deal because the wind also blows it away. But if sunlight is cut off too long the battery becomes empty and the heaters won't work anymore. So it would literally freeze to death.

Also you're only allowed to read that char

The problem is that the API pretends that it already sanitizes user input to a degree. (from the design perspective, not necessarily documentation)

Sanitizing the input yourself means not using it. You can't sanitize it.