minification-benchmarks VS TypeScript

Minifiers are used to reduce the size of the bundle. They can remove unused code, shorten expressions, and so on. And Now there are already several popular minifiers, and they continue to appear: more familiar ones - written in JavaScript - Terser and UglifyJS, even Babel has its own version of the minifier, there are also more modern SWC (written in Rust) and ESBuild (written in Go), and a bunch of other lesser-known minifiers. And I recommend you to look at this repository. It contains up-to-date test results of various popular minifiers.

This minify/gzip size effect is a well known quirk to developers of javascript minifiers. The minifier's symbol mangling algorithm often has a more pronounced effect than does advanced AST optimization.

This website has real life data on the matter for popular libraries:

* https://github.com/privatenumber/minification-benchmarks

Compare the trophies indicating smallest size for Minified versus Minzipped (gzip). Generally the smallest minified size yields the smallest minified+gzip size, but there are some notable anomolies outside the range of statistical noise. It is not practical for a javascript minifier to take a compression algorithm into account - it would blow up the minify timings exponentially.

It would be helpful to see how Bun's minifier compares to the others with popular libraries:

https://github.com/privatenumber/minification-benchmarks

JavaScript

There are many minifiers such as terser and uglify. But, because minifying also require to parse the JS, it is actually possible to use esbuild and SWC to minify the code. Here's a benchmark of the main minifiers.

Here's a comparison showing the major players with comparable stats at first glance. https://github.com/privatenumber/minification-benchmarks

https://esbuild.github.io/ https://github.com/privatenumber/minification-benchmarks

privatenumber/minification-benchmarks – JS minification benchmarks: babel-minify, esbuild, terser, uglify-js

I can't give advice about the trademark, other than that I've been through this kind of thing before and it sucks.

What I can say... is that I love what you've been doing on your Deepkit, and I was horrified to hear that this was happening to you.

Seriously, I've only lurked in the community so far, but it's possibly the most forward-thinking foundational library in the web space that I've seen.

Strong typing with annotations that can simultaneously influence runtime ORM and frontend generation, while being fully compliant Typescript? A hand-rolled lightning-fast Typescript compiler that emits the runtime reflection capabilities? Full-fledged DI as an inherent part of the design, not an afterthought?

It's such an incredible blend of beautiful tooling with pragmatic applications.

For anyone curious about this, https://web.archive.org/web/20230916074647/https://deepkit.i... is a fascinating read.

https://github.com/microsoft/TypeScript/issues/47658#issueco... provides context on why some of TypeScript's design goals around erasure hold it back from these features. My vision of the web is that it would be an even more vibrant and innovative place if TypeScript were to cast off those restrictions.

DeepKit actually solving this by implementing its own compiler, bytecode, and interpreter... it's truly incredible.

Marc, know that there are people out there who love your work, and who will continue to follow it avidly regardless of the name. You're doing amazing things.

This parser is not written in TS types, and this kind of pedantry (when claiming "no js here") is important. In fact, the parser includes both the use of ternary operators as well as the rest operator, both of which are absolutely not part of the type system and are most certainly part of JS.

While this tries to reach the levels of "TypeScript is Turing complete[1]" (which happens to be super cool), it is, in my humble opinion, not even remotely interesting.

[1] https://github.com/Microsoft/TypeScript/issues/14833

TypeScript- a strongly typed programming language that builds on JavaScript, giving you better tooling at any scale.

Type Safety TypeScript support is as good as Comlink, with all the type inference you expect.