20 replies

1. Nick Nisi Bluesky moments later

   Welcome!

   1. Zach Leatherman Bluesky 1 min later

      You win this round, Nick!

2. Zach Leatherman Bluesky 3 min later

   Best of luck to JSX — of whom I do not predict will have the same success 😅

   1. Pelle Wessman Bluesky 2 days later

      Its kind of a slippery slope of Node.js here (prompted by Deno / Bun). By supporting a non-standard file format rather than waiting for eg. github.com/tc39/proposa... they have opened themselves up to requests to support lots of other syntax.

      1. Pelle Wessman Bluesky 2 days later

         Only good part is that its a strict stripping now – else we might have ended up with an equivalent of in-core support for Coffeescript in a couple of years

3. Zach Leatherman Mastodon 5 min later

   Best of luck to JSX — of whom I do not predict will have the same success 😅

   1. Axel Rauschmayer Mastodon 8 min later

      @zachleat I was wondering about that! Type stripping could lead to packages such as htm (*) becoming more popular.

      (*) https://www.npmjs.com/package/htm

      1. Zach Leatherman Mastodon 12 min later

         @rauschma and well deserved!!

      2. Olivier Forget Mastodon 3 hr later

         @rauschma @zachleat What is the relation between type stripping and JSX and htm? (Sorry I don't use JSX so I don't know how it's actually implemented.) Is it just the trend of moving away from things that need special transpilers to things that work natively in JS?

         1. Axel Rauschmayer Mastodon 3 hr later

            @teleclimber
            See https://satanacchio.hashnode.dev/everything-you-need-to-know-about-nodejs-type-stripping#heading-features-that-require-configuration

            Rule of thumb: Type stripping only removes type-level syntax. What remains must be valid JS.

   2. Rob Anderson Mastodon 1 hr later

      @zachleat lol what would JSX even be with --erasableSyntaxOnly

      1. Zach Leatherman Mastodon 1 hr later

         @r0b it would be… uh… https://github.com/developit/htm

4. ‮Jeff Eaton Bluesky 14 min later

   I was gonna say, that tiny handful of “extras” always felt like a deeply uncomfortable “It’s just X… except for these really weird bits…” caveat that complicated the otherwise clear case for it. Agreed that the 5.8 release is pretty huge for that reason.

   1. ‮Jeff Eaton Bluesky 16 min later

      (IMO the biggest obstacle in full ecosystem transition is the preponderance of nigh-impossible-to-type js libraries with self-mutating “everything objects” as their primary interface, but that’s a different matter…)

   2. Zach Leatherman Bluesky 17 min later

      Whew, yeah!

5. Konnor Rogers Mastodon 19 min later

   @zachleat Zach. There's *only* 109 configuration options currently. By my count, "erasablySyntaxOnly" should cross us over into 110 options territory!

   https://codepen.io/paramagicdev/pen/yyBWEdg

   1. Zach Leatherman Mastodon 19 min later

      @konnorrogers just one more, just one more config option — just one more. Good thing they’re all orthogonal right… right

      1. Konnor Rogers Mastodon 28 min later

         @zachleat 😅 😅 😅 😅

   2. westbrook Mastodon 26 min later

      @konnorrogers @zachleat So, 6?

6. Veikko Eeva Bluesky 18 hr later

   Would this mean specifically polymorphic and server side JS/TS?

   As a person who likes to do easy MPAs with HTML, CSS and JSS and some bundling, this appears interesting on the surface but does not seem to affect so much web development and so feels like "just interesting with ecosystem evolution".