Comments

Hacker News

Funny to see vercel is loosing all credibility under the influence of AI. Never liked their products anyway, so I believe it's a net positive for the industry :)

by localhoster

I desperately want to see some of these projects used in production by the companies or people making them, at best it might prove that it isn't just a sloppy publicity stunt

by notsylver

This look very promising.

We are increasingly using a subset of typescript in our backend so as to be amenable to a tool, in the long run, which can convert the ts subset to rust source code.

This project will enable an alternative of that vision earlier - except of course without the parallelism.

Also I am curious as to whether this will compile to a static lib which can be linked to an existing cpp app to be run on android/ios targets. In theory it should be able to. The docs mention ffi, but I didn't dig deep.

by elendilm

It's nice they acknowledge and confirm the need for small, fast native executables.

Having followed the story for this in Java over the decades I'm skeptical about the practicality. GCJ existed in the 90s and the technology was good, but there was no ecosystem support.

After many small steps between GraalVM Native finally tackled the problem more holistically and the ecosystem followed. All the major libraries and frameworks put effort into being GraalVM compatible.

And, still it's a major pain to make even simple existing applications run flawlessly natively.

I'm glad something like scriptc exists but I'm afraid until this is of practical use it will be s long thorny way.

by weinzierl

One of the strengths of TypeScript besides its expressiveness is that it's compatible with the massive npm ecosystem. Most packages only ship untyped JavaScript with type declarations defining the interface,[0] so realistically you'd still need a JavaScript engine if you use any packages.

But if you're starting from scratch and know you won't be using any npm packages, you might as well use AssemblyScript.[2]

[0]: Publishing packages in TypeScript is explicitly discouraged by Node[1]. TypeScript isn't backwards compatible even in minor releases, and its compiler settings aren't portable for packages.

[1]: https://github.com/nodejs/node/blob/main/doc/api/typescript....

[2]: https://www.assemblyscript.org/

by sheept

this is enough to keep them on the first page of HN and similar services. Its a growth strategy: invest tokens, build some "nice" project nobody wants, get some reach through publishment. Rinse and repeat.

Heads up, in 12 months from now, 90% of open source projects will be vibecoded, without actual users - only looking "interesting" (if not already?).

Its easy to vibe code a full blown compiler these days, the question is: will it be maintained? A catchy title is not enough to get sticky users, long term maintenance, community around the project is (or at least used to be).

Having said that, the only viable reason for these kind of projects I see is getting attention for a moment, boosting reach of Vercel logo across the web and then disappearing (or stop development).

If Vercel would think seriously about this project: they would show skin in the game - for example implement it as their own experimental runtime.

by piterrro

Porforr<https://porffor.dev> has been working towards the same goal for a while. The creator, CanadaHonk<https://honk.foo>, is extremely talented and the project still only passes ~68% of Test262. I'm more than a little suspicious of how Vercel has made so much progress so fast, unless I'm misunderstanding the scope of this project.

by acmnrs

Vercel sloping it's way to clout again, they do this every month or so, clearly they want to stay in the news and some how credible and relevant.

I can't think of any serious company or project that would use this thing.

P.S: I just checked the contributors list, I have the utmost respect to them (notably simonw), but clearly this code is claude'ish but it is not among the contributor which makes it even more suspect.

by JoeDohn

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • Funny to see vercel is loosing all credibility under the influence of AI. Never liked their products anyway, so I believe it's a net positive for the industry :)
  • I desperately want to see some of these projects used in production by the companies or people making them, at best it might prove that it isn't just a sloppy publicity stunt
  • This look very promising.

    We are increasingly using a subset of typescript in our backend so as to be amenable to a tool, in the long run, which can convert the ts subset to rust source code.

    This project will enable an alternative of that vision earlier - except of course without the parallelism.

    Also I am curious as to whether this will compile to a static lib which can be linked to an existing cpp app to be run on android/ios targets. In theory it should be able to. The docs mention ffi, but I didn't dig deep.

  • It's nice they acknowledge and confirm the need for small, fast native executables.

    Having followed the story for this in Java over the decades I'm skeptical about the practicality. GCJ existed in the 90s and the technology was good, but there was no ecosystem support.

    After many small steps between GraalVM Native finally tackled the problem more holistically and the ecosystem followed. All the major libraries and frameworks put effort into being GraalVM compatible.

    And, still it's a major pain to make even simple existing applications run flawlessly natively.

    I'm glad something like scriptc exists but I'm afraid until this is of practical use it will be s long thorny way.

  • One of the strengths of TypeScript besides its expressiveness is that it's compatible with the massive npm ecosystem. Most packages only ship untyped JavaScript with type declarations defining the interface,[0] so realistically you'd still need a JavaScript engine if you use any packages.

    But if you're starting from scratch and know you won't be using any npm packages, you might as well use AssemblyScript.[2]

    [0]: Publishing packages in TypeScript is explicitly discouraged by Node[1]. TypeScript isn't backwards compatible even in minor releases, and its compiler settings aren't portable for packages.

    [1]: https://github.com/nodejs/node/blob/main/doc/api/typescript....

    [2]: https://www.assemblyscript.org/

  • this is enough to keep them on the first page of HN and similar services. Its a growth strategy: invest tokens, build some "nice" project nobody wants, get some reach through publishment. Rinse and repeat.

    Heads up, in 12 months from now, 90% of open source projects will be vibecoded, without actual users - only looking "interesting" (if not already?).

    Its easy to vibe code a full blown compiler these days, the question is: will it be maintained? A catchy title is not enough to get sticky users, long term maintenance, community around the project is (or at least used to be).

    Having said that, the only viable reason for these kind of projects I see is getting attention for a moment, boosting reach of Vercel logo across the web and then disappearing (or stop development).

    If Vercel would think seriously about this project: they would show skin in the game - for example implement it as their own experimental runtime.

  • Porforr<https://porffor.dev> has been working towards the same goal for a while. The creator, CanadaHonk<https://honk.foo>, is extremely talented and the project still only passes ~68% of Test262. I'm more than a little suspicious of how Vercel has made so much progress so fast, unless I'm misunderstanding the scope of this project.
  • Vercel sloping it's way to clout again, they do this every month or so, clearly they want to stay in the news and some how credible and relevant.

    I can't think of any serious company or project that would use this thing.

    P.S: I just checked the contributors list, I have the utmost respect to them (notably simonw), but clearly this code is claude'ish but it is not among the contributor which makes it even more suspect.