I wish Javascript had a nice array slice primative (for objects). Or structs I could allocate on the stack. 🥲
@arichtman You can overflow it and there was a spec proposed for tail call optimization when ES6 was still the new hype, so I guess it does? https://gpx.github.io/posts/es6-tail-call-optimization/
@mauve so many languages from that era bet the farm on heap allocated everything and the faith that garbage collectors would get fast enough or that it wouldn't matter 😞
@nasser I mean they weren't wrong tbh. 😅 Most people don't need to care about memory management even if it isn't efficient. Maybe the growing cost of RAM will change things
@mauve@mastodon.mauve.moe i wouldn’t even know where to start my list. i hope i never know it well enough to HAVE a list lol
@ellyxir Item 1: replace WASM with BEAM 🤪
@mauve@mastodon.mauve.moe i wanna play with wasm, havent yet. the list is too long!
@arichtman @ellyxir Back when it was first coming out I tried my hand at some basic WAT coding. Doing for loops was surprisingly a major pain in the ass :P
@arichtman @ellyxir Yeah AFAIK WAT has been pretty stable after the first few years. It's been the closest I've gotten to actually coding in lisp :P
@arichtman@eigenmagic.net @mauve@mastodon.mauve.moe yeah its basically like waiting until a series is complete before watching it. lots of benefits.
@mauve come to think of it do runtime languages *have* a stack for your program? They must right?