7,480 karma · joined September 13, 2011
meet.hn/city/51.0493286,13.7381437/Dresden
Socials: - bsky.app/profile/rurban - github.com/rurban ---
I also switched to local qwen recently, but have to block such outgoing requests.
gcc: 244 fails
clang: 826 fails
Both should be zero. In all my compilers I'm thriving for zero.I see. https://nvd.nist.gov/vuln/detail/cve-2026-98432 affected versions format is the culprit. Entirely unusable. We do have versions, branch names and tags for a reason.
3336 bytes for the case tables are not comparable to the ICU mess, and easily shippable.
But he was extremely successful as manager then. Just like the ex-NAZI NASA leader then a bit later.
That was the golden time of German management.
Even the very best models favor to divide the work and share information with each other. Even if they could have easily found it out by themselves.
So why do human devs still fail to do so? They rather reinvent the wheel, don't talk to similar projects who solved the same problem already.
Linux has the very same disturbing not invented here syndrome, rewriting good features by their own, making them worse.
As we see over and over again in python core development. It's the worst.
Only 3-4 compilers stayed secure in this regard, by either disallowing unicode names, or by using TR39.
What else is a high security riscs? All names, such as path names or user names on OS kernels, like filesystems. Filesystem or user db's with unicode support but without identifier support such as TR39 can also lead to security attacks. Apple once had at least HPFS which did normalization, but the recently gave up, because nobody cared. And Linus still calls garbage in, garbage out valuable. Even if the famous ssh attack used such an homoglyph attack to stay undetected.