4 ms·
Is JavaScript a memory safe language?
by postalrat 3y ago
Is JavaScript a memory safe language?
- unilynx 3y agoIt is. and so is WASM, but both probably aren't fast enough
- Thews 3y agoI think there is a ~35% hit with emscripten
- albntomat0 3y agoYes, and so are Python, Lisp, Haskell, and a million other languages that were available in 2010. None of those are suitable options for an image decoding library on the range of WebP supported platforms.
- mrtksn 3y ago>None of those are suitable options for an image decoding library on the range of WebP supported platforms. What makes these unusable for this task?
- sp332 3y agoThey need a large runtime and are slow to start up.
- mrtksn 3y agoIs that true for all memory safe languages? Why?
- marcosdumay 3y ago> Is that true for all memory safe languages? No. That is true for the list upthread (well, if you consider runtimes measuring a couple of MB "large", it's reasonable but quite arguable). It doesn't have much correlation with any feature.
- pjmlp 3y agoModula-2, Ada, Object Pascal, D would be. What makes them unsuitabe is lack of widespread compiler support across those platforms, if we ignore how long Ada has been available in GCC. And Modula-2 is now in GCC as well.
- assassinator42 3y agoAda has the bounds checking, but doesn't (AFAIK) have a safe way to deallocate dynamic memory. At least as of now, there is a proposal to add something like Rust in the future. It also has memory unsafe concepts like specifying an address for a variable.
- pjmlp 3y agoYes it does, this isn't Ada83 we are talking about. Well Rust also has unsafe, better not use it.