The article lists all flashy JavaScript proposals, and none of them are part of the language.

Here’s what actually is new: https://2ality.com/2025/06/ecmascript-2025.html

Iterator helper methods will be a nice addition!

I believe this article is largely wrong and misleading.

Pattern matching is still Stage 1, meaning it’s not a standard: https://github.com/tc39/proposal-pattern-matching

Pipeline operator is Stage 2 and won’t use the “|>” syntax: https://github.com/tc39/proposal-pipeline-operator

This is written by an LLM. Can we have less of these on HN?

> You’ll Fall in Love With

I'm going to press Circle to Doubt.

Oh look, every section header starts with an emoji. Gee, wonder who wrote this.

That said, it is nice that they finally borrowed the pipe-forward operator from the ML languages. Record and tuple syntax is gross though.

Hmm... one moment. The first example function they provide:

    function handleResponse(response) {
        return match (response) {
        when ({ status: 200, data }) -> data
        when ({ status: 401 }) -> throw new Error(’Unauthorized’)
        when ({ status: 404 }) -> throw new Error(’Not Found’)
        when ({ status: s if s >= 500 }) -> throw new Error(’Server Error’)
        default -> throw new Error(’Unknown Error’)
      };
    }

Is less readable to me than the way I would write it without the match/when construct:

    function handleResponse(response) {
        status = response.status;
        data   = response.data;
        if (status === 200 && data) return data;
        if (status === 401) throw new Error(’Unauthorized’);
        if (status === 404) throw new Error(’Not Found’);
        if (status  >= 500) throw new Error(’Server Error’);
        throw new Error(’Unknown Error’);
    }

The match/when approach also needs more code. 393 instead of 360 chars.

From the article:

  As front-end developers, staying ahead of JavaScript’s evolution isn’t optional — it’s survival.

  When the ES2025 proposals dropped, many developers (myself included) were shocked.

Isn't this hyperbole par excellence? There are some new language features, that is all. The whole article looks like written by this LLM prompt: "write about the new features of es2025 and hype it up as much as possible"

To be honest this whole article feels like it was AI generated. And em-dashes being used everywhere doesn’t help to shake off this feeling.

It's every section header starting with an emoji that's blatant LLM slop indicator. I'd love to know why LLMs love emojis so much.

I get what you mean, but the point of the article was to show how JavaScript is evolving to feel more like a functional language — not like Java or C#. That shift is actually what makes it cleaner and more expressive, not robotic.

<arrow in target emoji> You nailed it!

People have got to start prompting their LLMs to stop with the goddamn emoji.

<thumbs-up emoji> You nailed it!

   const result = data
     |> Object.entries(%)
     |> (%.filter(([k, v]) => v != null))
     |> Object.fromEntries(%)
     |> Object.values(%)
     |> JSON.stringify(%)
     |> encodeURIComponent(%);

Looks kinda awful to me. Am I strange that I prefer the 'spaghetti' version?

I’ll die on the hill that the tacit pipe operator would have been the right choice. IIRC the main objections came from engine implementors.

Why do people breezily say that a new and unfamiliar thing is more readable? What’s more readable is almost always the thing you are used to seeing.

  when ({ status: s if s >= 500 }) -> throw new Error(’Server Error’)

Is it only me or this doesn’t look like JavaScript anymore?

JavaScript is moving toward functional programming languages — I don’t see what’s wrong with that.

Open article.

"X isn't Y — it's Z"

Close article.

> As front-end developers, staying ahead of JavaScript’s evolution isn’t optional — it’s survival.

how long til it's in the browser for these?

Potentially never. Despite what the article says, pattern matching is not in ES2025 and is still at stage 1 of TC39 so it could be a couple years to never. The pipe operator is at stage 2 and not in the ES2025 spec.

That said, with transpilation/Babel/etc. you could in theory be using some of these features right now (e.g. `@babel/plugin-proposal-pipeline-operator`).

The original article here is terrible, clearly not written by anyone with a clue and potentially even by an LLM.

Never, because the LLM made most of it up.