882 karma · joined April 28, 2020
I'd be more than willing to use a more degradable plastic for something that needs to get a chilled product from the meat department to my home.
I would lean in on the unified schema aspect, I think that distinguishes it from a lot of web-focused ORMs. It actually feels like it could be compared against GraphQL given the schema and API features.
Of course, that leads me to wonder about the hairy stuff: permissions, rate limiting, schema evolution, etc.
I'd be interested in some more context on this. I think it's pretty clear that you can encode more than 1bps in a 60kHz signal, but I'm curious how the encoding was chosen. There's some more detail on it here:
https://en.wikipedia.org/wiki/WWVB#Modulation_format
The WWVB 60 kHz carrier, which has a normal ERP of 70 kW, is reduced in power at the start of each UTC second by 17 dB (to 1.4 kW ERP). It is restored to full power some time during the second. The duration of the reduced power encodes one of three symbols:
If power is reduced for one-fifth of a second (0.2 s), this is a data bit with value zero.
If power is reduced for one-half of a second (0.5 s), this is a data bit with value one.
If power is reduced for four-fifths of a second (0.8 s), this is a special non-data "mark", used for framing.
This is apparently the IRIG H encoding, which dates to the 50s and is probably designed to be easily decoded. By what, I wonder?
The other early-career people I know are having trouble as well.