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.
The problem with the date format is that the US one absolutely totally insane. Whenever you use something ordered you have to choose ordering. For date US choose the absurd kind. Y-d-m should never have been used. Remove that and around 90% of the string based format problems disappear.
...it will come up with what I have used in the last few conversions.
Though I have seen Quinn Nelson (Snazzy Labs on YouTube) released a video recently that shows his process which is a bit more involved, but better. Apparently his method is better to remove risks of power surges from the controller board (I haven't experienced it yet...!), but his method also retains the speakers, and relocates the I/O inputs to be more accessible.
A good hybrid can do very well. Presumably by keeping the engine in exactly its sweet spot and designing aggressively for that. BYD for example claims 46% thermal efficiency. [0]
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.
I have worked as dev since age of 18, I am now 42. Never had any health problems. I do some irregular sports but not very much. I don’t pay much attention to ergonomics, I just simply change my sitting position often and also take short walks. I do use standing desk sometimes but not for whole day, just for short periods.
Congratulations, you're a sensible human being who has figured out that listening to your body and intuition works much better than all these "optimal" solutions everyone is chasing after. I've suspected for a long time that much of ergonomics is just snake oil and hardly based on any evidence at all. If sitting upright or in some specific allegedly ergonomic position is making me feel tense and wears me out, how is that helpful? I prefer to go with what millions of years of evolution have coded in me. Fortunately I don't have a desk job anymore so it's not of much concern to me.
If you can _rename_ desktops though, I've never seen how.
e.g. in Mission Control right now I have "Desktop 1", "Desktop 2", and full-screened iTerm2 on my external monitor, plus "Desktop 3" and about 6 other fullscreen apps on my laptop.
I have somewhat semantic meaning for what each of those three numbered desktops are, but it'd be nice to _name_ them.
I find it helpful to set a different wallpaper for every space. In fact, that approach has been so useful that I’ve mostly stopped wishing to rename the spaces – I can glance at the colors so much faster than I could ever read a written title anyway.
Yeah I do this too, I can't imagine not having different wallpapers. But when I'm pinning apps to desktops via the Dock it'd be nice to have the names then.
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.
reply