mastodon 4.8.0-nightly.2026-10-06
If someone will ever compile my shit on #windows here's what I suggest: do not follow #python way, do not introduce those fucking different path separators, just don't.
Portable apps must stick to POSIX standard. In other words, does anyone give a fuck when their file names are displayed as file://c:/mycrap/fucking/shit.txt in their lovely internet explorer?
Guess where the conversion should take place?
Just a note for myself. Pass by, please,
Someone said authoritarian regime can't be changed peacefully. But what if #democratic regimes are fake? What we do then?
It's been quite a long time since I looked at #python docs.
At last they made URL parsing in line with RFC 3986
It took 20 years in this fast-paced IT world.
For all the rest, it goes fucking great!
Stepped into _Generics crap again. Previously it was related to u8"strings", but now they broke L"strings" They might have always been broken, idk.
So, L"fuck" is treated as int* in _Generic
I can add (char32_t*) in front of it, but I better wait for both #clang and #gcc hive minds to catch up.
Yet another crap comes from #gcc and incarnates in buggy code generation for a pretty innocent function. That starts from -O2 onward. Specifically, it's GCC 14.2.0-19 in Excalibur, #devuan
Goddamn, #C was already 30 years old when they wrote their reference implementation of an algorithm in a RFC... number... I won't tell which one.
30 years taught them nothing.
Rewriting it with an interesting library. The author asked not to tell for now. It's open, and it's online. It's same old #C but now it's really safe. Without perversions like in... hello, #rust and bye bye.
Fuck, a mysterious toot. Nevermind.