Right, but they generally keep it as a hidden implementation detail, and when you do get access to it it's not in any standardised way. For a lot of use cases you're better off unbundling it and newer datastores tend to be better at that.
Not just other squirrels. I have seen a magpie sitting on a wall waiting for a squirrel to finish burying its nut. Once the squirrel had finished, it descended to have a good poke around the burial area.
I would guess that their awake is asymmetrical (though in a different way) and so there might be a favored way to arrange them, but as they are inefficient compared to conventional turbines, and because the blades undergo a large cyclic variations of wind load with each rotation, they are not cmpetitive for large-scale commercial use.
There were a lot of Y2K related tasks in the course of many developers generally activity. Where I worked at the time, there were not developers solely dedicated to Y2K work. The Y2K issue pretty much caused an employment boom for software developers though.
I was fixing Y2K bugs at a company founded in 1997. Unless you never touched date stuff, I can't imagine being oblivious to Y2K issues working in IT in 1999.
The startups I worked in around that time - we were using recent hardware with 4 digit years and unconcerned about Y2K issues.
So while we were -aware- of the Y2K issue, it didn't impact any of us in a concrete fashion. We would talk about people we knew on Y2K projects, which were mostly mission critical legacy systems.
So it's not inconceivable for devs in the 90s to have only cursory awareness of the -real- issues that the people who worked on Y2K projects were facing and solved.
On the contrary; it permits it. Since its purpose was to prevant misattribution of internet-drafts to the ietf, we can surely now claim with certainty that the ietf teaches fake news about the demise of ancient egypt.
