Depends on the field you are in. There are jobs where you can’t get apps that run on anything but windows.

The cost of using a textual format is that floats become so slow to parse, that it’s a factor of over 14 times slower than parsing a normal integer. Even with the fastest simd algos we have right now.

So it depends. Float parsing performance is only a problem if you parse many floats, and lazy access might reduce work significantly (or add overhead: it depends).

Exactly. My for use cases, this format is amazing. I have very few floats, but lots and lots of objects, arrays and strings with moderate levels of duplication and substring duplication. My data is produced in a build and then read in thousands or millions of tiny queries that lookup up a single value deep inside the structure.

rx works very well as a kind of embedded database like sqlite, but completely unstructured like JSON.

Also I'm working on an extension that makes it mutable using append-only persistent data structures with a fixed-block caching level that is actually a pretty good database.

if you data is lots and lots of arrays of floats, this is likely not the format for you. Use float arrays.

Also note it stores decimal in a very compact encoding (two varints for base and power of 10)

That said, while this is a text format, it is also technically binary safe and could be extended with a new type tag to contain binary data if desired.

and with little data (i.e. <10Mb), this matters much less than accessibility and easy understanding of the data using a simple text editor or jq in the terminal + some filters.

what do you mean by little data, most communication protocols are not one off

Also good luck parsing 10 MiB of JSON in a loop that can't tolerate blocking the CPU for more than 10ms.

What's expensive is very relative to the use case.

There is no taste difference, it’s just cheaper to produce since you can skip heating it for a few minutes.

Apple already sells that, it’s called MacBook Air.

you could sell physical items at any store where you have to show your ID and you get one for the age group you are.

that kills two birds with one stone, you can then show everywhere online you are human and how old you are without the services needing any personal information about you, and the sellers don't know what you use that id tag for.

People who are posting AI comments or setting up AI bots are... people. They can show their ID. If a website owner doesn't have a way to ban that specific human and the bad guy can always get another voucher, it's sort of meaningless.

In fact, even if you can ban the human for life, I'm not sure it solves anything. There are billions of people out there and there's money to be made by monetizing attention. AI-generated content is a way to do that, so there's plenty of takers who don't mind the risk of getting booted from some platform once in a blue moon if it makes them $5k/month without requiring any effort or skill.

Perhaps not only just show your id to get your "Over age X verification object", but your ID also gets irreversibly altered (like a punch card) that makes it one-time-use only.

That might make it less likely someone would ever sell it because to get a new one might take a very long "cool-down" time and it'd severely hamper the seller.

what’s to keep people from selling or giving away those id tags? seems like a nefarious entity could buy them in bulk

It's already sorta happening with SIM-cards/phone numbers that are sometimes used for similar purposes.

Same thing that keeps me from letting my agent do the online talking for me. That is to say… nothing.

law enforcement.

I'll sell you my proof-of-human-age badge for $1,000.

I would be overjoyed if a human-level amount of spam cost $1000 per year-or-until-caught.

So some future generations might get 23 hour days? That’s gonna be an interesting problem to solve for calendar implementations

25-hour days.

As another poster already said, there will be 25-hour days at some time.

The dinosaurs had days with fewer hours than us.

Where there fewer hours or were those hours just different length?

Now we have locked in second extremely hard underpinning all of our measurements. But you could consider that you have same number of hours in a day and length of those hours has changed...

You could look at it either way. I couldn't say which system the dinosaurs actually used.

I have it on good authority they just used unixtime for everyone but put all the leapseconds in the tz table.

A Martian sol (day cycle/rotation) is > 24 hours (by about 40 minutes). Locked in seconds seems to be the easiest for general use mathematically. 24 hours in a day is a bit of a leftover from sundials and 12 being one of the easiest large fractions of a circle and the Earth day was never really a universal anyway, just an accident of where and roughly when we lived. On the other hand, the modern metric second is now defined at exactly 9,192,631,770 periods of Cesium-133 for atomic clocks and other reasons, so a locked second is useful for a lot of reasons.

I’ve written a CBOR implementation as a mruby c extension in an afternoon and am about to officially release it soon.

It’s my first project where I’ve worked with claude: https://github.com/Asmod4n/mruby-cbor

Exercising in the sun for 3 or 4 hours a day doesn’t sound healthy? Compared to the guy who planned to spend that time in the pub?

If that means that bedtime falls within 3 hours of the sunset then so be it. I’ve survived this long at least.

I find that physical activity promotes sound sleep.

In Europe and the US all new vehicles now have a visible ID under their front window glass, it’s called a VIN. It’s even standardized where it must be.

I wonder what the first vehicle to have the VIN under the windshield was. I believe I saw that for the first time maybe 20 years ago (USA).

This says 1969

https://scholarlycommons.law.case.edu/cgi/viewcontent.cgi?ar...

Are there cameras that can actually read VINs on moving vehicles?

I'm pretty sure it should be possible if one really wants to do it. Think of a high-power IR flash and a high-res camera synchronized with the flash, with fixed focus on where the VIN would be passing. If the flash pulse is short but strong enough, it should be possible to read the VIN. Maybe some polarizing filters to remove glass reflections are needed.

Win32 Apps can access anything you can access and also read out some text fields from apps you have running, via accessibility APIs.