Use more TypeScript?
be5invis opened this issue · 2 comments
Just for better code organization...
I'm open to this. The code started as just a rough prototype for playing with curves but is growing and will no doubt continue to grow more, as there's still major functionality missing (such as the ability to edit more than one subpath). I will probably hold off until I get a better idea where the codebase is going, whether this will be the main place it's developed into a real tool or not.
Research prototype should be plain Javascript, IMO.
Make a production implementation in Rust and compile it to wasm.
YMMV, but I find Javascript syntax more or less okay (in terms of programmer productivity) for numerical stuff if you do everything in inefficient ways creating tons of unnecessary tiny temporary arrays, using way more function calls than necessary to increase the level of abstraction, etc. But start trying to do efficient numerical code in Javascript which avoids unnecessary data movement etc. and it quickly becomes ugly and painful to write/edit.