My initial reactions:<p>The good:<p>- network-crossing actor model, but with private addresses and built in routing and security capabilities<p>- object component security<p>- null means null<p>- immutability<p>- AWK-like pattern DSL<p>- functino is a cool way to have your infix operators cake and eat it too as prefix functions<p>The bad:<p>- no type checking on variables, parameters, record fields, record shapes, actor messages, etc<p>- practically need to buy a new keyboard to type all the symbols like '≈', '≠', 'ƒ', etc<p>- null punning seems great until you're looking at a null three function calls later and have no idea where it came from<p>Unsure:<p>- No reserved names means it's very easy to accidentally overwrite a primordial with no warning, I suspect someone will instantly build a linter that makes that a rule because this just looks like a foot-gun<p>Ultimately, this looks like JavaScript without all the foot-guns. Add in some modern features like actors, immutability, and a pattern matching DSL. Add in some new foot-guns like primordial renaming and null punning.<p>If I could snap my fingers and today be able to write Misty in the browser, I'd definitely use it for performance intensive code alongside Typescript until TypedMisty came out, then I'd probably switch for good.<p>However, I'd be absolutely shocked if any major browsers ever support Misty. So it'll probably remain a server side scripting language, which I definitely do not need. Why would I use this on the server for scripting over F#, Clojure, Elixir, or Go?