Live data from Hacker News

Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary

github.com

141–150 of 165 posts

Re: Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary

#141

Earlier quoted context omitted.

Kind of funny seeing a serious (?), grown up, for-profit company acting the same way as my scatterbrain clinging into this month's fascination. Luckily, most of my things never see the light of day, so they don't get referenced a month later in a HN burn when I publish yet another project I'll stop working on in a month.

Is it really that bad of an idea to experiment, put things out into public, and see what works and what sticks? They haven't abandoned agent-browser and portless, which came out of these vercel-labs efforts because they're useful tools and people are using them.

> Is it really that bad of an idea to experiment

I don't think so, I literally think it's fun to see. Sharing projects regardless of how done, mature, reliable, correct or not they are, feels like a net positive for humanity.

Re: Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary

#142
post #118

Earlier quoted context omitted.

That doesn't change the fact that there is a lot of Angular out there. No one's doubting how useful Next.js may or may not be, it's just a matter of fact that plenty of systems were created before it was available and not everyone has the luxury of rewriting their entire product.

Moving goalposts, the point was about SaaS SDKs giving tier1 support for React and nothing else, thus giving Vercel their current market position. Invalidating the remark "I can't think of any serious company or project that would use this thing." Where's the example?

I'll be honest I have never heard of this nor do I understand why it matters. It looks like it's just internal Vercel marketing speak that basically amounts to them desperately trying to build a platform and extract rents off of it.

Re: Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary

#143
post #118

Earlier quoted context omitted.

Moving goalposts, the point was about SaaS SDKs giving tier1 support for React and nothing else, thus giving Vercel their current market position. Invalidating the remark "I can't think of any serious company or project that would use this thing." Where's the example?

I'll be honest I have never heard of this nor do I understand why it matters. It looks like it's just internal Vercel marketing speak that basically amounts to them desperately trying to build a platform and extract rents off of it.

It matters, because React is one of the reasons FE development sucks nowadays, and in many cases there are no alternatives, unless one loves yak shaving for their framework du jour.

Re: Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary

#144

Earlier quoted context omitted.

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.

With the exports rewritten? Maybe we should have a export of “ts” like we have “types” instead?

Not sure what you mean, but to expand on what I wrote, JSR rewrites the import statements to include file extensions and full version numbers for package dependencies, so that the imports can be resolved without looking for them in multiple places.

There's a way to download JSR packages and use them with npm too. I don't know what it does in that case.

Re: Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary

#145
post #124

Earlier quoted context omitted.

I think you are confusing React SDK with Vercel SDK.

They are both pushed by the same company, even more so since many React contributors became Vercel employees. React is designed with Next.js needs in mind nowadays.

Perhaps the newer features of React are but thankfully those bits can be completely ignored.

Re: Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary

#146

Earlier quoted context omitted.

> 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.

> > 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. Don't you think that even if you don't know someone personally, you can calibrate your trust in their ability based on reputation, track record.

> you can calibrate your trust in their ability based on reputation, track record

rarely. How many of the libraries you pull from package managers do you actually know the authors of?

Re: Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary

#148
post #116

Earlier quoted context omitted.

That's a one big hell of a contribution ;-) https://github.com/vercel-labs/scriptc/commit/725b931cf43ba7...

I get so irritated every time Claude says "honest". Anthropic talks about how they specifically engineer for it to be "honest". I'm convinced they're just measuring how many times it says the word honest instead.

I'm amused by Claude developing its own corporate jargon which, while clearly pulled from the corpus of human language, is quite distinct from the bullshit traded over the boardroom table.

I've had trouble unpacking some of the copy it generates because its default tone of voice is fairly unintuitive. It's almost like it's designed to induce psychosis because it makes you feel like you've discovered something novel.

Re: Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary

#150
Despite the hate it is receiving, I thought lets test it at least, and tried it to any project that I have locally. For every single of them the coverage generates hundreds of errors and so it is basically useless. I get that I can write a project from scratch, don't use any third party library, and it'll compile to binary, but then why should I not use Rust, Go, Zig, D, C, V, Ada, C++, Nim, Swift, Kotlin Native, Haskell... literally anything designed to be compiled and compiled well?
Post reply on HN