SaaSHub helps you find the best software and product alternatives Learn more →
Proof-is-in-the-pudding Alternatives
Similar projects and alternatives to proof-is-in-the-pudding
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
-
perry
A native TypeScript compiler written in Rust. Compiles TypeScript directly to executables using SWC and LLVM.
-
-
-
proof-is-in-the-pudding discussion
proof-is-in-the-pudding reviews and mentions
-
Perry Compiles TypeScript directly to executables using SWC and LLVM
> strict, deterministic subset of TypeScript
I'll add that page, thanks. Today, almost all of idiomatic TS is supported including most of its utility classes. Dynamic JS-style code is not supported, for example adding a function or a field into an object, prototype-based class modifications etc. I'll compile a list.
> Also, what's an "ambient surface" in this context?
I need to clean up the docs before v1. But the idea is that when JS gets transpiled into C# (or Rust, upcoming), JS globals and built-ins are invalid. The native "surface" is C#, meaning the string is .Net's string type and the methods that you expect on JS strings would be missing. But when you opt in to a surface, such as the "JS surface", the compiler applies surface defined translations such as substring becoming SubString, either directly or via a companion helper class. This allows you to write against standard JS and Node APIs, instead of relying on the stdlib/builtins of the target framework (currently only CLR).
For example, all the projects you see under this use the JS surface: https://github.com/tsoniclang/proof-is-in-the-pudding/tree/m...
-
Show HN: Tsonic – A TypeScript to native code compiler via CLR and NativeAOT
You can see some examples here: https://github.com/tsoniclang/proof-is-in-the-pudding
And a hugo clone (native code of course) here: https://github.com/tsoniclang/tsumo
-
The Performance Revolution in JavaScript Tooling
Actually TypeScript is an excellent language (in my view) for targeting native code. It reads cleaner than Java, C# and even golang in many cases - at least to me.
For example, JS/TS's file-path based imports are more intuitive; several languages do it via explicit namespaces when well-written code is already organized into directories. Of course, all of these design choices are subjective. In fact, disagreement with a few people in the C# user community is one of the reasons I started this project.
> At what point do JavaScript developers need to realise that this is all convoluted, and begin to use languages better suited for the job.
I'm curious to know what makes TS convoluted. Here's an example of multi-threading: https://github.com/tsoniclang/proof-is-in-the-pudding/blob/m...
-
A note from our sponsor - SaaSHub
www.saashub.com | 11 Jun 2026
Stats
tsoniclang/proof-is-in-the-pudding is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of proof-is-in-the-pudding is TypeScript.