chfalck
Joined 4 years ago
Joined 4 years ago
Like most LLM generation though, it’s not a deterministic thing and like you mentioned originally it takes some verification of the output. I still think with the extra steps it saves time when applied to the right scenarios. The longer the input the higher the hallucinations count in my experience though, so I always keep the code provided in the smallest chunk possible which still has enough context.
>cultural hegemony See previous … what?
Let’s get down to brass tax.
A does foo. B notices A has done foo. B decides it will also do foo. A has influenced B.
There are other aspects about the original comment which were better targets than attacking the meaning of “influence”, such as America’s status as a melting pot whose traditions are in great part just the collection of influences from the multitude of ethnicities which can be represented by the single term “American”. Thinking America has such dramatic unique influence while ignoring its composition of influences from other cultures is not giving honest context. That’s the part I would have gone after.
Aside from that, no matter what you pick, standard Typescript configs are absolutely compiling to JavaScript, not any other step in the interpreting process. It doesn’t matter if it’s taking your async/await and polyfilling it to run on an older browser engine… it’s still producing 100% JavaScript.
It goes Typescript -> JavaScript during the build, and the JS is what gets distributed to clients.
The JavaScript produced by TS is sent to the browser which performs the same JavaScript -> abstract syntax tree -> byte code -> execution, as usual