If I could use Nim to replace my Angular & node dev, currently done with typescript, I would be so happy... desperately missing operator overloading.
Wouldn't this be much more straightforward than targeting vanilla JS, anyway? But I understand there will be some language impedance... anyway, would dearly like to read thoughts.. I want to use Nim, but I can't use it right now - with an established asset base, if I could I would jump immediately as I prefer to encode IP with an elegant and fast-moving language. Typescript gives the word 'conservative' a bad name.
I think would be nice to patch the JavaScript codegen to add types,
...but using Facebooks FlowType, because is literally plain vanilla JavaScript with comments, types go inline tiny comments, kinda /*: int */, that way it can still run directly in anything that has a JavaScript interpreter, and you do not lose strict static typing, I would be interested on that.
Also making Nim comments emit JavaScript comments would be nice anyway.
I think it would be more correct to say integrate Nim with JS/TS (and Angular / React / Svelte etc.).
So it would be possible to convert some part of project to Nim and make it work well with the rest of the project done in JS/TS.
I also would like to be able to do that and would use Nim instead of TS.
But the way Nim currently works, it replaces JS/TS, instead of integrating with it. And it makes pretty much impossible Nim usage in FrontEnd Development.
Interfacing with the JS world is possible and frequently done...
But the way Nim currently works, it replaces JS/TS, instead of integrating with it.
Yeah well, what does that even mean...
<script lang="nim">...</script>
Wouldn't this require Nim to be compiled in the browser?