finally someone did this
Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary
71–80 of 165 posts
Re: Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary
#72Vercel 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…
From contributions tab, it looks like 99% was vibe-coded by 1 person, and it does not look like they have any compilers background. Edit: typo
that doesn't mean much. it has a lot of tests, the architect seems sane, it fits a niche (for example scripts baked into container images don't need full (Node + tsx + esbuild) or Bun/Deno)
Re: Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary
#73Vercel 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…
Edit: Removed.
Indeed I am a random, but does it make me less qualified than another random ? (look up ^ )
Re: Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary
#74Vercel 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…
Claude-directed code by someone being conscientious and getting involved in the important decisions is going to be better than a whole swathe of existing open-source that was hand-written.
Maybe if it's a business level tool made in house with claude vs contracted to a software house in India. Never for a compiler, who even is that person?
Re: Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary
#75Vercel 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…
Most SaaS products have Vercel as partner, with Next.js and React as the tier 1 SDK on their tooling.
Re: Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary
#76It'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 fr…
GCJ was always a prototype kind of.
Anyone serious would be paying for Excelsior JET, BEA JRockit, or the myriad of other commercial JDKs wihth AOT tooling.
In fact most likely one reasons why Excelsior is not more, is that now GraalVM and OpenJ9 exist as free bear.
PTC and Aicas still have it good, because few care about their embedded and real time customers.
Re: Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary
#77Earlier quoted context omitted.
Those are good reasons to publish untyped libraries as a rule, sure. But the contention that those reasons outweigh the value of types kinda boggles the mind, ngl!
Publishing a lib as JS with .d.ts type files gives you JS compatibility and TS types for using the lib, but no TS source so no types inside. I’ve seen people want to publish TS libs but there are issues: TS will type check the libs as well as your project. You can’t tell it to stop just because it’s going inside node modules. And the app may have tighter settings than the library and you will get type errors if your…
When publishing on jsr.io, you upload the TypeScript, and if using Deno, you also download TypeScript (with import statements rewritten.) Having nearly the original source code is better for debugging.
Deno doesn’t type-check external dependencies unless you ask.
Re: Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary
#78Earlier quoted context omitted.
Claude-directed code by someone being conscientious and getting involved in the important decisions is going to be better than a whole swathe of existing open-source that was hand-written.
Maybe if it's a business level tool made in house with claude vs contracted to a software house in India. Never for a compiler, who even is that person?
> Never for a compiler, who even is that person?
Why do you care?
It's a stranger from the Internet. Same as with any other software you're using. In particular, same as with any OSS tool you're using.
Re: Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary
#79One 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]: Pu…
I would use it for a focused command-line tool that needs to share code with a larger TypeScript project, not for code with a lot of dependencies.
Re: Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary
#80Vercel 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…
Also the same vibe-code leader as zerolang, "The Programming Language for Agents" which Vercel launched with much fanfare in May, landed 1200 commits and then stopped ~mid-June.