JavaScript and TypeScript features of the last 3 years
hmm... I&#x27;ve been using JS&#x2F;TS for almost as long as they&#x27;ve existed. A lot of these are nice. Some less so. Some quick thoughts:<p>- Tagged template strings. This just feels dirty to me. Probably won&#x27;t use, but when I see it in a code base I won&#x27;t be so confused at least<p>- matchAll. I&#x27;ve never needed this. I&#x27;ve used match with g a bunch, but I never need the capture group.<p>- Promise.allSettled. THIS is useful. I&#x27;ve implemented this (under a different name) in almost every code base I&#x27;ve worked on, and got bit HARD by not understanding this behavior long ago (huge production outage that took hours and many engineers to discover)<p>- globalThis. EW. Don&#x27;t think I have to elaborate<p>- replaceAll. It&#x27;s always annoyed me needing to use RegEx for simple replace all. so Yay!<p>- ??=, &amp;&amp;=, ||= These seem really useful, but also potentially hard to read, but I think if I get used to their existence they&#x27;d become second nature<p>- # private... not sure why they didn&#x27;t just use the &quot;private&quot; keyword, but I don&#x27;t care. I almost always use TypeScript anyways<p>- static ... YAY! finally. Again, if they could do this i don&#x27;t see why not &quot;private&quot;<p>For the TypeScript stuff I&#x27;ll just say the type system has kinda jumped the shark, but I don&#x27;t hate it. It&#x27;s SO robust and of all the new stuff being added I&#x27;ll maybe use 1&#x2F;10 of it, but it&#x27;s good to know I can describe literally anything* with it if needed.<p>* EXCEPT IF I WANT TO USE AN ENUM&#x2F;TYPE AS A KEY IN AN DICT WHICH I REALLY WANT TO DO!!