Yeah, I actually really don't like JSON. It looks simple but actually isn't, that's a bad combo.
CBOR is much nicer, but annoyingly they made their human readable debug version of it similar enough to JSON that people assume it's just a binary form of JSON, it isn't.
The entire number and math system is just a straightforward implementation of IEEE 754.
Yeah, but using doubles for everything is its own downsides e.g. it's why JSON "can't" store 64bit integers for starters.
They did add the BigInt class recently, which annoyingly you can't use with JSON because it requires specialized handling (Because of the aforementioned issue with JSON).
(So you "can" store 64bit integers in JSON, the spec just says not to, so people just ignore the spec. You just then run into silent truncation issues with clients that do follow it, like browsers.)
Windows Terminal is the terminal emulator that hosts the shell (cmd or PowerShell, or anything else really). It's the modern replacement for "conhost".
It's also a fantastic app, some of the devs are on Mastodon too.
This behavior is actually in line with what I'd expect, as Unicode support in Windows predates UTF-16, so Windows generally does not handle surrogate pairs and instead operates almost exclusively on WTF-16 code units directly.
So it's just straight UCS-2, and the software does enforce that, pretty much the opposite of "WTF-16".
Edit: Pretty sure "modern" (XP+ I think) Windows actually does enforce UTF-16 validity in the system, but there's always legacy stuff from the NT4/2K era that might turn up.
Landrun as well, takes the restrictions on the command line. Can look messy, but does make it entirely standalone, so you can e.g. drop it into a service file as the readme shows easily enough.
Webp is a smaller file size than jpeg for the same image quality in almost all circumstances
For lower quality images sure, for high quality ones JPEG will beat it (WebP, being an old video format, only supports a quarter of the colour resolution than JPEG does, etc.) JPEG is actually so good that it still comes out ahead in a bunch of benchmarks, it's just it's now starting to show it's age technology wise (like WebP, it's limited to 8bpc in most cases)
It also doesn't hurt that Google ranked sites using WebP/AVIF higher than ones that aren't (via lighthouse).
Edit: I should clarify, this is the lossy mode. The lossless mode gives better compression than PNG, but is still limited to 8bpc, so can't store high bit depth, or HDR images, like PNG can.
Phones and tablets? They've displaced computers for a fair few people, and it's hard to consistently run a P2P client on those devices (And that's ignoring metered connection costs)
Edit: Ok the "apparently" is doing heavy lifting, since now I can't find the original source I read about it. Turns out "X" is a garbage name with no searchability, only an idiot would use it.
Inertia? Easier to stick with what you know than learn something new (aka pay money to train up staff), and chicken-and-egg issues with not deploying things because of worries of bugs, but then bugs stick around because nobody encounters them.
My ISP is relatively new and couldn't actually afford much of a v4 allocation, so they've had to be a v6 first provider pretty much from the start. In the beginning they hit a bunch of issues in supposedly mature networking gear because they just hadn't been stress tested at that scale before.
Edit: Oh yeah, and also people who just don't like IPv6 at all and refuse to consider it, and they can end up in positions of power.
That'd at least make sense, this is a (literal) black box. Seriously, my monitor takes long enough to wake that it's at the boot loader screen by the time it's ready.
I found a post on Reddit claiming it's a RAM thing, and I should enable XMP to avoid it. But I've already got XMP enabled so I need to poke around it again.
And also disable the 5 second delay in the bootloader, not like I'm ever using that fallback option.
Yeah, but that's still not a lot of data, like LTR/RTL shouldn't be varying within a given script so the values will be shared over an entire range of characters.
What strikes me as odd is the decision to position itself as just another AI‑enabled web browser, picking a fight with big techs and better‑funded startups whose users are less hostile (and sometimes enthusiastic) about adding AI to web browsing.
It's about "being better", except at one point that meant acting better, but now it means trying beat their metrics.
Yeah, I actually really don't like JSON. It looks simple but actually isn't, that's a bad combo.
CBOR is much nicer, but annoyingly they made their human readable debug version of it similar enough to JSON that people assume it's just a binary form of JSON, it isn't.