The battlefield changes as kids age. It’s impossible to have any realistic discussion about sleep habits without discussing the elephant in the room. What is your device policy and how do you manage screen time, what your bedtime routine is (you better have one!) and how good you are at sticking to the timing on a daily basis.
Same, as the father of three children, I believe a lot of it has to do with sleep pattern conditioning. You are literally training minds to sleep on a rigid schedule to keep your own sanity. That implies sticking to rigid timing as much as possible and creating the optimal environment for success. E.g., correct lighting, air movement, sound (I highly recommend “Hey Siri, play Pure Meditation playlist”) at a low volume, and if you live in an otherwise particularly hectic environment, appropriately dosed and timed melatonin supplements. You reap the rewards of your own hard training work, or suffer the consequences of the lack thereof.
> async/await came out of C# (well at least the JS version of it).
Having been instrumental in accelerating bringing async/await to JS, it definitely was the case that it came from C# and we eagerly were awaiting its arrival in JS and worked with Igalia to focus on it and make it happen across browsers more quickly so people could actually depend on it.
You should always seek out the best. From watching lots of Everyday Astronaut streams over the years, I knew the stream would be the best live experience because they care about and focus on the production. NASA cares and focuses on the rocket, astronauts, mission. I'm fine with that.
I feel like those not involved in this space might not realize so much stuff that benefits the entire web/world comes from volunteers like anba and companies outside the usual browser vendors. Whether you’re an individual contributor or you want to push your employer to contribute or let you contribute, the best time to get involved is always now. We owe anba a big one. Thank you!!
Yes, please try! One of the main motivations for doing all this work is to slim down both the amount of code that has to be delivered and executed by providing everything that's needed by the platform. In addition, you're slimming the potential bug/attack surface as well, which is always nice.
Depending on the situation, the data lives either within the browser or within the OS. Chrome releases ship versions of tzdata that correspond to the version of tzdata shipped with the ICU it uses, and they do backport updates to prior Chrome releases within a certain window. Apple has a sideband way of deploying tzdata to all devices that doesn't appear via the normal Software Update mechanism. So it all depends on which particular OS/browser combo you're interested in and the decisions those owners made.
reply