[jerrygoyal]

As modern JS is getting closer to typescript in terms of new methods, latest syntax etc. What is the future of TS? will it be there for just type checking?

[lucacasonato]

Yes.

[egeozcan]

could you imagine that some JS proposal adds the ability to ignore TS-like type annotations to the engines, so we don't even have to strip them?

this may help development heavily, also making the browser and deno nearly identical environments.

[lucacasonato]

Yes, this would be great, and it will probably happen eventually. This is something we want to work on soon - expect something in the coming weeks.

[ducaale]

Since TS/Deno has native support for JSX syntax, do you think Browsers will eventually support it as well?

[lucacasonato]

No, I don't think so. JSX is too proprietary and not specified well enough. It is also rather ambiguous.

If you want a "no compile" JSX:

```jsx

const x = <div color="red">hello</div>;

// is the same as

const x = h("div", { color: "red" }, "hello");

```

[eyelidlessness]

This is more true as a mental model/to the type system, but slightly more complicated when compiled.

First, there’s the “new JSX transform”, which involves auto-imports, has a different function signature, and defines fallback behavior for certain circumstances.

Second, JSX is only specified as a syntax extension. Some implementations—like SolidJS and its underlying dom-expressions compiler—don’t compile to hyperscript at all.

[brundolf]

It’s always been there just for type checking, hasn’t it?