What were the challenges out of interest. Some of it is the use of gcc extensions? Which needed an equivalent and porting over to the equivalent

`asm goto` was the big one. The x86_64 maintainers broke the clang builds very intentionally just after we had gotten x86_64 building (with necessary patches upstreamed) by requiring compiler support for that GNU C extension. This was right around the time of meltdown+spectre, and the x86_64 maintainers didn't want to support fallbacks for older versions of GCC (and ToT Clang at the time) that lacked `asm goto` support for the initial fixes shipped under duress (embargo). `asm goto` requires plumbing throughout the compiler, and I've learned more about register allocation than I particularly care...

Fixing some UB in the kernel sources, lots of plumbing to the build system (particularly making it more hermetic).

Getting the rest of the LLVM binutils substitutes to work in place of GNU binutils was also challenging. Rewriting a fair amount of 32b ARM assembler to be "unified syntax" in the kernel. Linker bugs are hard to debug. Kernel boot failures are hard to debug (thank god for QEMU+gdb protocol). Lots of people worked on many different parts here, not just me.

Evangelism and convincing upstream kernel developers why clang support was worth anyones while.

https://github.com/ClangBuiltLinux/linux/issues for a good historical perspective. https://github.com/ClangBuiltLinux/linux/wiki/Talks,-Present... for talks on the subject. Keynoting LLVM conf was a personal highlight (https://www.youtube.com/watch?v=6l4DtR5exwo).

Or want to diversify to reduce exposure, after all a loan inherently has a risk. Doesn’t mean ( it could ) it’s a fire sale a eggs basket situation

Not within a mayor’s control

Not kill children is the start , then not kill the innocent and then move to the civilized world conduct. Fairly low bar to meet.

So just ignore the atrocities Hamas/male Gazans committed and move on? Not exactly realistic?

they are not synonymous as you’d like to make us believe, just cant be a homogeneous group.

Yes I think countries shouldn’t kill innocent people, you’d think people that experienced a genocide wouldn’t commit genocide so easily

The disclaimers speak loudly what are you trying to say

Writing the plugin seems to be a hard problem. It’s not clear from the link if there are non trivial plugins written for real formats, not toy not POC but a for reals plugins

All that is true and the spin I focus on is can Microsoft have implemented it such that they have zero (ish) knowledge by default.

We know iCloud has configurations that can’t disclosed, and I wonder if there is a middle ground between if you loose the recovery key you are stuffed and maybe have a recovery key unblocked by a password similar to ssh keys

That is more interoperability than guest language situation. I don’t think c++ is a c guest. Ts has a different approach to the js self.

C++ started as a C macro preprocessor, designed to work as C in UNIX, and by CFront 2.0 there was already too much compatibility to throw away.

Ts is basically a linter, everything else is JS.

c++ bootstrapping as a transpiler back when it was a 1 man show is hardly where it’s at today. The point about self handling in ts should demonstrate there is more than just strip the types going on

There is the whole fit into the same UNIX compiler toolchain as C, without additional changes to the linker, include files, object and archive files.

Oh like how gnu compiler includes an ada compiler ? Or the C++ name mangling ?

Obviously there a common heritage and the shared ancestor is c.

C++ name mangling was exactly designed to be able to link C++ code with a standard UNIX linker that only knows C.

GNAT has zero compatibility with C source, doesn't even make sense.

> presenting things

I don’t have a dog in this race, have to say thou the vagueness of the hand waving in multiple comments is losing you credibility