This was a great post, but is the last state of the macro actually bad for performance in any way? I get that it's ugly (and we should only choose to make code less readable like this when there's actually an issue) but is it worse for runtime performance?
Someone just suggested to me that I should be putting my chocolate bars in the freezer first. I've never heard of this, but apparently it's a thing that I've been missing out on for a while.
So I guess I'm the one who can't believe that I don't do it.
I was today-years-old when I learned the ideal way to eat a banana.
Waldo is hiding in there somewhere, btw.
This was a good, short read. Worth the time.
How does it handle multiple potential outcomes?
Example: unformat!("a {} b {} c", "a x b b y c")
Would it return Some(("x b", "y"))
or Some(("x", "b y"))
?
I expected "Started new project"
Cursorless. It's a spoken-language programming interface that allows the programmer (of basically any language) to use specific words to target existing text, move the underlying cursor/selection relative to that target, and then run a specific modification. Think of VIM but for voice. It runs in VSCode atm as a couple extensions along with an install of the audio tool Talon. https://www.cursorless.org/
From my experience JS is primarily used to manipulate the DOM. I haven't looked into it, but if you're correct that WASM cannot manipulate the DOM then your question, to me, is tantamount to "Why aren't people using forks to eat soup?".
I would love a staticly-typed, compiled language to come along and replace JS. If anyone is aware of how I can write Rust in place of JS, please let me know. For now, I suffer/enjoy JS.
The aliens haven't yet consumed our planet in this timeline. Consider yourself lucky.