3 ms·
The way around this is to build your own tools. For instance, I used esbuild as a library to write a custom obfuscator that links the hand written JS and GLSL t
by fidotron 2y ago
The way around this is to build your own tools. For instance, I used esbuild as a library to write a custom obfuscator that links the hand written JS and GLSL together. (This is why the shader link symbols are also obfuscated).
I came from many years of compiled languages in the games industry. I would not assume the current state of React and TypeScript is bad, far from it. There are reasons this stuff has eaten away at more native approaches, or inspired things like SwiftUI.
Edit to add: To also add that in my time I've seen more WebKit added to games in order to do the UI. For instance, that Sim City which was always connected to the cloud, or big bits of the PS4 interface.
- o11c 2y ago"build your own tools" is also known as "the ecosystem is lacking"
- leptons 2y agoOne tool does not necessarily fit all the things. And that would be true of any "ecosystem" that has as many diverse uses as Javascript does. Versatility is one of Javascript's strengths, not a weakness. And with that versatility you get what seems like too many frameworks.
- fidotron 2y agoI have never met an existing ecosystem where building your tools did not make your life easier, at least in the short term. The trick is knowing when to abandon them in favour of a standard solution. To put this in perspective one team I was on built their own Android NDK, until the normal one caught up.
- o11c 2y agoTrue, but I've never met an ecosystem where building your own tools is required.