lambda-8cc
williamcotton.com
lambda-8cc | williamcotton.com | |
---|---|---|
13 | 1 | |
598 | 2 | |
- | - | |
10.0 | 7.4 | |
over 1 year ago | 8 days ago | |
Common Lisp | F# | |
MIT License | - |
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.
lambda-8cc
-
React Use C
ycombinator siding with the Amazonian cult of the carcinisation?! blasphemy! this submission is like a wanted poster for react-use-lambda to be summoned into existence from the great beyond https://github.com/woodrush/lambda-8cc
-
Any recommendations for advanced Lambda Calculus?
It is not what you want exactly, but there is a x86 C Compiler written in lambda-calculus, it has a pretty detailed "How it was done" in details.md - maybe you will find it interesting.
- This formula here is known as the “Standard Model Lagrangian”. It's an equation that encapsulates everything we currently know about particle physics.
- Show HN: Lambda-8cc – An x86 C compiler written in untyped lambda calculus
- GitHub - woodrush/lambda-8cc: x86 C compiler written in untyped lambda calculus
- Any projects want/need help?
-
lambda-8cc: An x86 C compiler written in untyped lambda calculus
That said, I'm not sure where is the actual compiler implementation, files in src/ seem to be various tools: https://github.com/woodrush/lambda-8cc/tree/main/src
williamcotton.com
-
React Use C
These conditional checks are an obvious sign that they’ve cleaved the rock in the wrong location.
These conditional checks on server state exist because they didn’t create the shared environment between web server and web browser at deep enough of a level.
The key is to replicate the server-side pattern of “user actions cause HTTP request”. That is, you make a version of express that runs in the browser. Then you make parallel middleware that runs in both the browser and the server. Then you make your React components fire off mock HTTP requests that are handled by the browser express router.
So you write the same route handlers and components for the browser and server to run but then you write environment specific middleware.
Browser middleware:
https://github.com/williamcotton/williamcotton.com/tree/mast...
Server middleware:
https://github.com/williamcotton/williamcotton.com/tree/mast...
I’ve expanded beyond express in the above application to add controllers, a routes file, and views, all code that has no conditionals and runs in both the browser and server environment.
What NextJS demoed is poorly conceived. There’s no need to autogenerate a link to an API.
Instead, your frontend middleware has req.update() defined to make an API request and the server middleware has req.update() defined to make the SQL update.
And there you go, sane server and client side rendering.
What are some alternatives?
react-use-rust - Use Rust in your React!
react-use-c - Use C in your React!
8cc - A Small C Compiler
gameboy-brainfuck - Implementation of a brainfuck interpreter written for the Game Boy.
picoc-js - The picoc interpreter compiled as WASM.
cps - A formalization of continuation-passing style calculi in Coq [WIP]
vellum - Data Frames for Common Lisp
lambdavm - A programmable virtual CPU written in untyped lambda calculus
AIT - Algorithmic Information Theory, using Binary Lambda Calculus
lambda-calculus-devkit - A collection of lambda calculus interpreters and development tools