prepack
assemblyscript
prepack | assemblyscript | |
---|---|---|
8 | 30 | |
14,385 | 16,455 | |
- | 0.4% | |
0.0 | 7.7 | |
about 2 years ago | 26 days ago | |
JavaScript | WebAssembly | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
prepack
-
Ask HN: Interest in a Rust-Inspired Language Compiling to JavaScript?
Hello HN,
I'm considering the development of a new programming language, drawing inspiration from Rust's strengths, with a focus on compiling to JavaScript. Here what I'm considering are some key features:
Strict Type System
Algebraic Data Types
*Unsafe Mode for JS/TS Interaction*: Facilitate direct interaction with existing JavaScript and TypeScript code.
No Null Usage: Option/Result patterns to avoid null.
Trait Implementation
Backend Development Priority: Initially targeting server-side applications.
Efficient Compiler Design: Including features like dead-code elimination and partial evaluation, similar to the approach of Prepack[0] (by Facebook).
I believe this approach could bring significant benefits, especially with recent advancements like Uint8Array and worker threads.
Would this be of interest to the community? Looking forward to your insights and discussion.
[0] https://github.com/facebookarchive/prepack
-
Do any engines or optimizers product TS-specific performance gains?
You can still do optimisations based purely on Javascript semantics. This is similar to the first example you give with dead function elimination, and many minifiers do some amount of this already, but you can take it to some extremes. One example of this is the (no longer maintained) Prepack project from Facebook. The core idea is to evaluate as much Javascript as possible at compile time, with the expectation that the result will probably be smaller (albeit less human readable) than the initial code.
-
[AskJS] Are there JS minifiers that can compress the code by storing and reusing repeating property/method names and strings?
It's no longer maintained, but I think prepack is roughly what you're looking for.
- Can something like typescript or elm be AOT-compiled efficiently?
-
React I Love You, But You're Bringing Me Down
i've had code where it intentionally relied on the wrong behavior (missing hook dependencies) and when I fixed it it caused an unintentional bug (hook fired too often or sometimes infinite rerendering). Yes it is more of a bug in the code rather than React hooks issue but it is also really hard to fix/rewrite. while i'd love to jump on the hype train projects like https://github.com/facebookarchive/prepack and how concurrent mode is still experimental after five+ years doesn't give me a lot of confidence.
-
Memoirs of a lone JavaScript developer PART 2 : Svelte. An awful implementation of an old idea.
Some real examples in JavaScript can be seen on Prepack[2]. Consequently it is natural to wonder whether we can AOT compile components of client side frameworks, to achieve a reduction in the final bundle size, but also to increase application execution speed.
-
React 18 is now in beta
Less or more it’s likely to happen, and could have been expected 2-3 years ago.
Especially with https://github.com/facebook/prepack. They want to eventually ship pre-compiled components rather than React.createElement() to end user
-
Vercel Welcomes Rich Harris, Creator of Svelte
https://github.com/facebook/react/issues/7324
I also think this is why facebook had been investing in `prepack` - https://github.com/facebook/prepack
assemblyscript
-
Borgo is a statically typed language that compiles to Go
I like your take but JavaScript was literally the assembly language of the web until WASM came along. There was no other language that TypeScript could compile to.
This train of thought lead me to discover AssemblyScript! https://www.assemblyscript.org/
-
Let's Write a Malloc
Incidentally, it’s also what AssemblyScript uses: https://github.com/AssemblyScript/assemblyscript/blob/main/s...
-
Gentle Introduction To Typescript Compiler API
Use it as a Front-End for other low-level languages.
-
TypeScript Is Surprisingly OK for Compilers
> MHO typescript could just cut loose from its javascript compatibility. Why not compile it to wasm instead of transpiling it to javascript?
Check out AssemblyScript which is exactly that:
https://www.assemblyscript.org/
-
Do you think typescript will ever have native support on brosers? Or we will have only the JS type annotations?
If you're curious, check out AssemblyScript, that might describe better what needs to be cut from TypeScript to make it possible to be compiled to WASM.
-
Ezno's checker (a Javascript type checker and compiler written in Rust) is now open source
This is kinda the idea behind AssemblyScript, but IIRC it's more of a low-level typescript-ish syntax for WebAssembly.
-
Is there a TypeScript to native compiler available?
https://www.assemblyscript.org/ maybe, but I'm not sure exactly what you need.
-
Emerging Rust GUI libraries in a WASM world
Exactly, WASM was designed to be very very lightweight... you can put a lot of logic into a very small amount of WASM, but you need a good compiler to do that, or write WASM by hand to really feel the benefit. If you just compile Go to WASM, with its GC, runtime and stdlib included in the binary, yeah it's going to be pretty heavy... Rust doesn't have a runtime but as you said, for some reason, produces relatively large binaries (not the case only in WASM by the way). Probably, the best ways to create small WASM binaries is to compile from C or from a WASM-native language like AssemblySCript (https://www.assemblyscript.org).
-
Dan Abramov responds to React critics
Well we have all the new ECMA standards that will be introduced in 5 years now. It's looking more like Java actually. its accessor and typing patterns match it the most. TypeScript has had quite the profound influence over future ECMA design. There is a not so well known project called AssemblyScript which I think has a promising future. Since future ecma standards closely resembles it and TypeScripts popularity has exploded I have a feeling it may become a real standard as well.
- AssemblyScript – TypeScript-like language for WebAssembly
What are some alternatives?
react-18 - Workgroup for React 18 release.
rust-ffmpeg-wasi - ffmpeg 7 libraries precompiled for WebAsembly/WASI, as a Rust crate.
SvelteKit - web development, streamlined
Lua - Lua is a powerful, efficient, lightweight, embeddable scripting language. It supports procedural programming, object-oriented programming, functional programming, data-driven programming, and data description.
next-runtime - The Next.js Runtime allows Next.js to run on Netlify with zero configuration
interface-types
denoflare - Develop, test, and deploy Cloudflare Workers with Deno.
reference-types - Proposal for adding basic reference types (anyref)
jsx - The JSX specification is a XML-like syntax extension to ECMAScript.
ffmpeg.wasm - FFmpeg for browser, powered by WebAssembly
solid-realworld - A Solid Implementation of the Realworld Example App
rust - Empowering everyone to build reliable and efficient software.