News for hackers. Stuff that matters.
Re:A Rust Shaped Hole by ashishb on Wednesday July 16, 2025 @02:43PM (#44585536)
TypeScript is good as a language. You can't generate static binaries out of it (except Docker images) and that itself is a deal breaker.
Re:A Rust Shaped Hole by genshii on Wednesday July 16, 2025 @02:48PM (#44585577)
Yeah, that's definitely a huge drawback. Bun lets you get pretty close though with the `--compile` flag: https://bun.sh/docs/bundler

Too bad the binaries are 60MB at a minimum :(

Re:A Rust Shaped Hole by wk_end on Wednesday July 16, 2025 @02:52PM (#44585619)
I'd love to see someone develop a compiler for TypeScript that got, say, Ocaml-like performance. There's a bunch of reasons why that'd be tough though - you'd probably want a language very-similar-to-but-not-quite-like-TypeScript.
Re:A Rust Shaped Hole by williamstein on Wednesday July 16, 2025 @02:57PM (#44585676)
This is probably the closest thing to that: https://www.assemblyscript.org/
Re:A Rust Shaped Hole by wk_end on Wednesday July 16, 2025 @03:09PM (#44585767)
The documentation is really incomplete. It's not at all clear how similar to TypeScript this is...does this support structural subtyping? Type manipulation? Iterators/generators? Async?
Re:A Rust Shaped Hole by ellg on Wednesday July 16, 2025 @02:57PM (#44585668)
its called C#
Re:A Rust Shaped Hole by wk_end on Wednesday July 16, 2025 @03:06PM (#44585739)
C# is a lovely language but it's not that similar to TypeScript. The big distinction (for me) is that it's nominally-typed and much more rigid. Unless things have changed a lot since I last touched it (admittedly a while ago):

You can't synthesize ad hoc union types (https://www.typescriptlang.org/docs/handbook/2/everyday-type...)

There's no notion of literal types (https://www.typescriptlang.org/docs/handbook/2/everyday-type...)

There's no type narrowing (which gets you a kind of sum type) (https://www.typescriptlang.org/docs/handbook/2/narrowing.htm...)

Most of the type maniuplation features (keyof, indexed access types, conditional types, template literal types...) are missing (https://www.typescriptlang.org/docs/handbook/2/types-from-ty...)

Re:A Rust Shaped Hole by pragmatic on Wednesday July 16, 2025 @06:36PM (#44587582)
Close but not quite.
Re:A Rust Shaped Hole by abhijat on Thursday July 17, 2025 @10:52AM (#44594065)
There used to be reasonml but I'm not sure how active it is these days.
Re:A Rust Shaped Hole by wk_end on Thursday July 17, 2025 @07:20PM (#44599400)
ReasonML is just OCaml with a different syntax. It sort of very loosely resembles JS syntactically in that it's got curly braces, but that's about as far as the similarities go - about as much as Rust resembles C. The type system and language are very different from TypeScript or JS, and much more rigid.
Re:A Rust Shaped Hole by Tade0 on Wednesday July 16, 2025 @02:50PM (#44585595)
I mean you can, they're just inappropriately large.
Re:A Rust Shaped Hole by skybrian on Thursday July 17, 2025 @01:37AM (#44590035)
You can’t? I haven’t used it, but what’s wrong with “deno compile?”

https://docs.deno.com/runtime/reference/cli/compile/

Re:A Rust Shaped Hole by shim__ on Thursday July 17, 2025 @05:02AM (#44591247)
Sounds like electron but for cli
Re:A Rust Shaped Hole by chainwax on Thursday July 17, 2025 @01:01PM (#44595488)
I does indeed bundle it's runtime into the executable, but this is not dissimilar from Go bundling it's gc into every executable.

Granted a compiled hello world Go program will be <2mb while a similar compiled Deno program will be more like 70. I imagine many usecases may not have a storage constraint though, and in that case why not?

Re:A Rust Shaped Hole by ashishb on Thursday July 17, 2025 @02:14PM (#44596323)
My problem is running post install step of 100+ npm packages on my machine. Any of those could be malicious.

https://www.sentinelone.com/blog/unseen-threats-in-software-...

Re:A Rust Shaped Hole by ashishb on Thursday July 17, 2025 @02:12PM (#44596302)
You are the fifth person who told me that this can be done but have never used it.

If this compile approach is so awesome why don't devs use it?