In my opinion, pre-designing your code is generally a good thing. Hours of planning saves weeks of coding
Lucky
joined 2 years ago
Try deleting all obj and bin folders in the repo and restart VS. Sometimes it gets stuck on an old project reference and can't clear out the cached files
To clarify for OP, the only time you need this at all is when the object has a reference to something that the garbage collector won't dispose of naturally. Things like an open file stream, db connection, etc.
You won't need to dispose of an object you created if it just has properties and methods
The second comment explains a lot. There is a build script that generated the binary, which they are using to reduce the overall build time. They mention this resulting from a limitation on cargo and this being a workaround
It seems like you could build it all from scratch if needed with a bit of effort
Why does the way you present the data change how the memory is managed? I think you are mixing data storage with display logic.
I'd imagine one of those killer features is using a language with a solid standard library. Npm dependencies are notoriously complex because js as a language is missing basic functionality that is standard in other languages. Just a few years ago the Internet broke because "pad left" was pulled by it's maintainer, that simply doesn't happen in other languages
From a maintenance perspective npm is a nightmare. From a security perspective it is worse. Being able to build your entire website using a language that eliminates most dependencies, and the ones you take on don't pull in a zillion dependencies either, is absolutely a killer feature
Of course that isn't the full story and using js still has it's advantages as people have already pointed out. If wasm closes the gap in those areas then it would absolutely be worth the switch
They didn't say anything about "forced simplicity". Not everything is a slippery slope