Yeah, and we punish irresponsible driving in those cases too

Yeah, we enforce squash merges and it works pretty well

Yeah, humans looking to make money lack empathy, which is why regulation is needed to force them to act as if they do

Are you suggesting men aren't qualified to take care of children?

I'm not surprised at all, current Florida resident, and bike lanes in the city I'm living in are not safe, and definitely not regarded by drivers. Additionally, one of the things I noticed after moving down is that (and this might be confirmation bias but) it feels people are driving while on their phones way more than the other places I've lived.

I've found this fun phenomenon where drivers who don't immediately go when the light turns green cause they're on their phone don't get honked at every time. My theory is that it's because the drivers behind them are also on their phone

"Shaders could be authored directly in SPIRV" oh god please no lmao

Also to answer your question, no. The hlsl to dxil translation is basically owned by microsoft. There's been little effort to move away from that

Well... they are rewriting & upstreaming DXC to LLVM main (https://github.com/microsoft/DirectXShaderCompiler/wiki/Cont...) and want to kinda deprecate DXC. IIRC currently only compute shaders are supported but I may be very wrong.

llvm (apple) is a mistake, but I am not expecting microsoft to do anything else than mistakes anyway.

I am really serious about direct authoring of shaders using SPIR-V (with probably a little SSA checker on the side). We can reasonably think it will significantly increase the compatibility and bug avoidance of shaders among various drivers (and that is priceless when you think QA of big video games spaning many different drivers).

I am perfectly aware this will require a bit more upfront work to write shaders, but due to their life cycle, it should be benign and we should get all the benefits (not even mentioning to free the SDK dependency from a massive and complex high level shading language compiler).

I am going to give it a try. I need first a SPIR-V assembler, the one from the khronos spriv tools and the one from llvm are c++ diarrhea then a definitive nono, have to write my own. Let's think long run here: we don't have a _REAL_ standard very high level language yet (python? lua? javascript? perl5? ruby? so_many_others?), I'll go rv64 assembly then (I'll write a mini rv64 interpreter for x86_64).