205 karma · joined October 20, 2014
this rabbit hole goes deep...
some implementations carry the same "uncomparable" logic when checking for unique constraints, while others drop the ball here.
programming language wise, it's kinda like null pointer or float NaN, both of which are also occasionally complained about, eg. indexing maps by float values can do bogus things in case of NaNs.
edit: clarified some things
that exists, see https://en.wikipedia.org/wiki/Rich_Communication_Services
Just shows how easy it is to be wrong by being lazy with http parsing.
So while usability is pretty similar, they're pretty different underneath.
>RFC 68388
what are these numbers, I don't recall RFCs going into 5 digits yet
There's also Jason's reply to apparently not-nice feedback of someone from NetGate: https://lists.zx2c4.com/pipermail/wireguard/2021-March/00649...
they recently frozen bitstream: https://gitlab.com/wg1/jpeg-xl/-/tags/v0.2
it has been. look up avif, you can already sorta try it out on firefox nighty.
see jpeg-xl
Games still can render more FPS than mandated by vsync.
I tried playing sauerbraten (with SDL2) on sway other day, it was butter smooth (no tearing) with vsync off in game, and I felt no input lag unlike when I switch vsync flag on in game which limits FPS.
It probably does triple buffering, but somehow on sway it worked better than triple buffering of intel's xorg driver back when I tried that.
https://devblogs.microsoft.com/commandline/announcing-wsl-2/
you aren't obliged to use it, are you?