Do you have only those two dirs at the top level? If so how are you finding it? I tend to have a docs dir at the top level, along with other build stuff

I've had no trouble so far. I'd have no problem with ephemeral build artifacts going either at the root, or in src.

edit: I have had one pain point: devs/managers ask me why I do that, and that I stop. I refuse.

Took me a while to understand what you meant by "on each end". I'm guessing you mean as a connection to some public transit in the middle?

Yeah. For example, if I lived in Cupertino, have it manage:

Home -> waymo -> Caltrain -> Waymo -> sf concert venue

For me smoothly

In the script tag you only have access to JS. This allows you to escape JS and have native code execution. It is still sandboxed by os-level primitives, but it is an escalation/first step in successful exploitation.

I see, so there are certain things that arbitrary native code could try do (let's say, try to execute a certain syscall) that native code produced by the JIT compiler wouldn't normally be able to attempt?

It's specifically about the mechanics/physics rather than the model, but yes.

It has the vertices, the surfaces, the textures and the animations.

There's a minecraft mod too, you press m and f5, boom you're mario.

The Linux kernel is pretty small

This does still look like it uses XLA, fwiw.

It is not a stupid concern, butt there is architecture around making sure you can't just save a request for later and replay it

It is mostly developed by AMD and used to be hosted on the AMD github iirc

You cannot explain everything to everyone all the time. Besides, this is not even a paper. Sometimes you are not the target audience and have to put some words into Google.

While that is true, it's not like I can use two laptops at once