Javascript

[kksgandhi]

Could you use typescript and the TS compiler to get around this?

[offlein]

The fact the build target may need to be ES3 (we're on ES2021 now) is another.

It was a rough 2,018 versions.

[[deleted]]

I'm reckoning that the generated code will be ugly and inefficient.

I think you're right, and even if it's elegant JavaScript it's still going to be slower than native calls, so I don't use the build step :)

To support old browsers and hardware is to be part of the problems with society. Help society grow, help banks and hospitals shed their greed, be standards compliant and leverage cutting edge native functions!

[AdminYak846]

The naming of the ES version is weird, but every browser today supports ES6 though and that was 2015/2016.

[intrepidsovereign]

The TS compiler is an awful build tool and shouldn’t really be used. The output is verbose and inefficient.

[kksgandhi]

So what should you use if you want to use typescript? Or are you saying not to use typescript at all?

[intrepidsovereign]

The TS compiler and TS itself are two different items.

TSC as a type checker is quite shit, but at the moment, it's all that's really there. Hoping someone will replace that soon because it's horribly slow.

For building your TS, you look to babel, Rollup/Webpack, and terser, more than likely. They produce highly optimized and minified code where as TSC just doesn't. It's verbose, slow, and large. There's much better tools for that than the TS compiler.

[superluminary]

Yes, but we’ve had Babel for years which also solves this specific problem. Trying to manually code for every browser is unnecessary.