coffeescript VS TypeScript

That said, there are ways to embrace the JS ecosystem without actually using JavaScript. Many popular languages have transpilers that will convert code written in that particular language into something that will run natively in a web browser (in other words, JavaScript). Even TypeScript is a language that gets transpiled into JavaScript, so it's not that outrageous of a concept, it just gets more difficult to do the further you get away from languages that don't already look like JavaScript.

As a front-end web developer, do you still use CoffeeScript or jQuery? Unlikely, as TypeScript, ES/TC39 and Babel (and the retirement of Internet Explorer thanks to @codepo8 and his EDGE team) have helped to transform JavaScript into some kind of a modern programming language.

CoffeeScript

On the other hand, companies choose React because that's where all the developers are. If you want to build something that can be maintained years from now, you better not choose the next hype train that goes straight to nowhere (remember CoffeeScript ?). You want something battle tested that has stood the test of time, where you won't have trouble finding developers to scale once you need to. And nobody ever got fired for choosing React.

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.