Alex Froio

just in using them I can already say they're garbage.

Just in trying to do ANYTHING safety related I can say they are garbage. Our tools have tools for fucks sake to hand-hold C/C++ so they don't harm patients.

A colleague suggested I listen to CppCast to try and rid myself of C++ anxiety, and I have never heard better arguments to step the fuck away from that space. Developers who bring out changelogs for C++ compilers and OPENLY ADMIT it is functionally different to work with different epochs, and then turn around and say "but there's no better way to do this so". They'll clutch onto their PERFORMANCE necklaces as you tear down why you should not need a 300-page book on initializing variables.

I look forward to reading this blog post and destroying my own brain once more.

there looks to be a partial sentence in the 1:N, N:1 section: "This means that any encoding where it does not produce 1:N data Were you writing to a file?"

EDIT: also an "all all" in "The collection of the cuneicode functions above are all all both strongly-typed" just under the "General-Purpose Interconnected Conversions Require Genericity" heading

EDIT 2: from context I'd presume "That is, while one platform will affirm that "C.UTF-8" is a valid locale/encoding," should be "C.utf-8"

EDIT 3: the link titled "previous definitions we talked about earlier" goes to an undefined anchor

EDIT 4: really like the article, and will likely use cuneicode if I need to do text wrangling in C in the future

your hatred is my hatred, friend.

can't believe i missed this when it first showed up. hell yes hell yes

oh shit i didn't see this when it dropped, i'm definitely going to have a good look at this and maybe fire icu4c in my projects because it's such an exercise in frustration and futility to actually use.