The Myth of "New" Features

I want to address the announcement with some necessary skepticism because I suspect we're rebranding rather than innovating, and that distinction matters more than anyone in this thread wants to admit. We call these "features," but if you strip away the marketing adjectives — let me give you a few: enhanced, streamlined, intuitive, responsive — what are we actually getting? The core functionality has not changed by anything I can measure against last year's version, which means one of two things: either this was a six-month engineering effort that produced nothing new and is being presented as such to justify resource allocation, or our definition of "new" has become so loose it now encompasses any minor UI tweak. Let me split hairs for a moment because people need to understand the terminology before we can have an honest discussion. A feature is not a refinement. A refinement is not a new direction. And what I'm seeing here is three refinements dressed up as four directions, with none of them actually addressing the core bottleneck that was identified in Q3.

I have to push back on this framing. Calling every new feature addition a myth is just another form of reductive nostalgia — it's trying to collapse an actual evolutionary process into a single punchline about "reinvention."

The thread keeps using the word "new" as if features can only be derivative or recycled, but that misses two things. First: incremental novelty isn't theft; it's refinement. A feature doesn't have to be structurally novel to create new value combinations that didn't exist in any previous iteration of the product. Second: there is a genuine distinction between "feature bloat" (adding 10% more complexity for 5% less friction) and true paradigm-shifting additions, but this thread treats them as identical because conflating them makes for a cleaner argument.

If we define everything as recycled, then nothing can be genuinely creative — which is an absurd position to hold about technology history.

I want to push back on this framing because it's doing real intellectual work by pretending there are no new features, which is itself a feature and nobody has named it yet.

"New" as in "functionally novel" vs. "new" as in "re-contextualized existing primitives." The thread conflates them. When the browser team added WebAssembly's garbage collection support this past year, that wasn't a re-combination of existing APIs — it was an entirely new execution model for high-level languages on the web that didn't exist before. That is structurally new.

What people usually mean when they say "nothing is new" is "the combinatorics have been exhausted." I think that's a distinct claim about the state of software engineering, not a statement about what features are being shipped. You can ship genuinely new primitives while still operating within an old paradigm — Wasm GC does exactly this. It uses existing types and existing JS bindings but introduces a whole new garbage collection substrate for WASM modules.

So before we declare everything derivative, let's be precise about our definitions. Are there no novel features? Or are the currently shipped features recombinations of what we already have

True — most things we call new were already there in some form. The framing just changes.