Live data from Hacker News

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

github.com

51–60 of 165 posts

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

#51
post #14

Earlier quoted context omitted.

Putting aside the whole “team of professionals putting out a product vs solo dev fine tuning their opus” of it all: Can you clarify what about the architecture is ‘idiotic’? Not trying to catch you or demand a defense, just looking for a vague description. I don’t even know how to start examining the architecture of something like this.

Yeah - using quickjs at all in a thing that needs perf. Quickjs is hilariously slow. Midwits use it because it has “quick” in the name. - using floats for numbers and deferring int optimizations for later. Inferring ints is like half the problem of fast JS. - rejecting inadequately annotated or too dynamic code without a whole heck of a lot of self-reflection about how unlikely that is to work out. The observation th…

"This project reeks of weapons grade AI psychosis" - fantastic quote: I will shamelessly steal & use. Apologies to pizlonator

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

#52

this is interesting , so i can turn electron into a native app now? whats the use case for this , make it hard to reverse engineer my node projects?

This is a really important question. If true, it could end a lot of Electron wastefulness.

Don’t see how compiling Typescript changes how little Electron cares about the host OS in terms of UI and how it just ships Chromium in order to show any UI at all

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

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

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

#54

Earlier quoted context omitted.

Christ. Imagine if bridges, skyscrapers, dams, cars, airplanes were designed and built like that. I vibeslopped thousands of pages of blueprints, nobody reviewed them, but another team of digital monkeys with the intellect of an ant have already built the bridge, and it seems to not have collapsed yet , so we're already directing traffic there. I can't imagine actual engineers feeling anything but deepest contempt fo…

"Actual engineers" don't really care about software engineering, much less a strong emotion at all like the "deepest contempt" and many of them already vibe code today for their work anyway.

Oh no, we do, because the software world has been abusing what engineering means for decades, in order to inflate job titles. Most people are programmers, not software engineers, and that's OK.

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

#56
post #50

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…

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

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

#57
post #50

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…

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

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

#58
Shameless plug but worth reading :

I have forked Fabrice Bellards QuickJS and extended it heavily to adopt anti-npm/node stance.

all of the essential standard lib and top npm packages will be built natively in C17 with every build and minor release focred through CPU, IO and memory profiling.

Currently it supports MacOS and Linux, FreeBSD and Windows in future.

https://github.com/corporatepiyush/dynascript

API reference : https://github.com/corporatepiyush/dynascript/blob/master/do...

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

#60
post #50

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…

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.
Post reply on HN