alexpdp7 VS deno

Details also here: https://github.com/alexpdp7/alexpdp7/issues/10

I wrote some thoughts about this at: https://github.com/alexpdp7/alexpdp7/blob/master/programming/python/creating_nice_python_cli_tools.md

JSX can become valid, standardized ECMAScript syntax.

But first we need a valid syntactic sugar transformation, which I propose here.

Then we need to implement it in things like babel[0] bun[1] and deno[2].

Then, frameworks would adopt it as an optional alternative implementation.

Eventually, it could gain widespread support and become standardized.

[0] https://github.com/sdegutis/vanillajsx.com/blob/main/site/un...

[1] https://github.com/oven-sh/bun/issues/13630

[2] https://github.com/denoland/deno/issues/25312

Ha, in what I believe Ryan's first talk about Deno, he mentioned something about avoiding cute features or so, then he said Deno has URL-based imports "because they're cute". It didn't take long for someone to raise it up in 2018:

https://github.com/denoland/deno/issues/195

We've come full circle :)

So, does that work now? Can we simply npm run test? Really? Well, almost. Unfortunately, Node, in comparison to other runtimes like Bun or Deno still is JavaScript only, so we have to transpile from TypeScript it to JavaScript first.

Deno

NodeJS is the dominant Javascript server runtime environment for Javascript and Typescript (sort of) projects. But over the years, we have seen several attempts to build alternative runtime environments such as Deno and Bun, today’s subject, among others.

https://github.com/denoland/deno/issues is the ideal place -- we try to triage all incoming issues, the more specific the repro the easier it is to address but we will take a look at everything that comes in.

Install Node.js (or Bun, or Deno, or whatever JS runtime you prefer) if it's not there

QUIC is very exciting, after seeing what it can do for performance in Cloudflare network and Cloudflare workers, I can't wait to finally see it in Deno[0] 1.41.

[0] https://github.com/denoland/deno/pull/21942#issuecomment-192...

So as an end user it's kind of like https://deno.com/ where you buy into a runtime + comes prepacked with DBs (k/v stores), scheduling, and deploy stuff?

> by storing Unison code in a database, keyed by the hash of that code, we gain a perfect incremental compilation cache which is shared among all developers of a project. This is an absolutely WILD feature, but it's fantastic and hard to go back once you've experienced it. I am basically never waiting around for my code to compile - once code has been parsed and typechecked once, by anyone, it's not touched again until it's changed.

Interesting. Whats it like upgrading and managing dependencies in that code? I'd assume it gets more complex when it's not just the Union system but 3rd party plugins (stuff interacting with the OS or other libs).