Somewhat discrediting article. Anyway I for one am very happy with this PDF and the exposure to this problem, I and many others were not aware, and no we don't read all github stuff haha.
The PDF explains it a billion times more clear than anything else out there. So lots of thanks to this professor who took his valuable time to get to the bottom of this and make us all understand in good detail, I read most important parts, still got some more pages to go. Anyway the discrediting article has some points funny: 1. Yes it's a world wide problem and many many many software will have to be adjusted/fixed. 2. Yes it's not only about compilers. And the conclusion that we as a people may have to take is: FUCK UNICODE is broken. AND FUCK.... maybe we should think long and hard about what kind of language/code we are writing our communications and codes in. This should have never been possible in the first place. The people that designed UNICODE completely fucked up. Apperently it's not only a table of symbols... but much more... it's also control logic and there lies the flaw. Bye for now, Skybuck. On Tuesday, November 2, 2021 at 4:15:38 PM UTC+1 o...@ucm.es wrote: > >>> "s" == skybuck2000 <skybu...@hotmail.com> writes: > > > I haven't even read this document fully yet, but all signs point to > MAJOR > > TROUBLE AHEAD for open source projects: > > > https://www.trojansource.codes/trojan-source.pdf > > Relax: https://research.swtch.com/trojan > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/82d992a2-bfa4-4044-b61d-28a4714c1c68n%40googlegroups.com.
