I read that entire article thinking it said driving instructor. Doesn't really change anything but it makes so much more sense that he's a part time diving instructor.
Their Oura comparison really didn't sit well with me because of that. The device clearly uses a fraction of the power that the Oura is using. If it had a rechargeable battery you would not have to charge it that frequently.
That lifespan is based on the user recording for 12 to 15 hours over those two years. It's a $100 device that can record
12 hours of audio and then you throw it away. You could expend the battery on your first day by holding down the button.
Honestly I can see a niche use but this device strikes me as quite weird and I'm not sure why it isn't a button on their new watch.
The issue with most of what you're saying here is that all of that works the way it does because it can, not because it has to. Code libraries, for example, may essentially prohibit what is being requested by SKG because they can. However, if they couldn't then they wouldn't. The companies selling the libraries aren't going to simply shut up shop.
Which is just to say, if there's money to be made then businesses will do so within the regulatory framework.
Right. The title seemed to be suggesting that the Nix way of doing things might have detected the backdoor. It's actually intending to suggest ways that Nix could be changed in order to detect the backdoor.
$100 profit on a $150 watch would be crazy. Rest of the post seems made up too. I don't know where these numbers are coming from. I'm genuinely confused.
If I'm reading this correctly, they are recommending a lock in this situation. However, they are saying the implementations has two options, either raise an error reporting the race (if the implementation is told to do so), or, because the value being read is not larger than a machine word, reply to the read with a correct value from a previous write. If true then it cannot reply with corrupted data.
Would "key-value" not have a place in the description?
This application may be very capable, but I agree with the person saying that its use-case isn't clear on the home page, you have to go deeper into the docs. "Smarter than a database" also seems kind of debatable.