wscl
PurefunctionPipelineDataflow
wscl | PurefunctionPipelineDataflow | |
---|---|---|
4 | 172 | |
38 | 439 | |
- | - | |
6.9 | 7.4 | |
4 days ago | 15 days ago | |
TeX | ||
GNU General Public License v3.0 or later | - |
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.
wscl
-
Practical Common Lisp
You can't seriously say that, just because one targets a well-specified machine, that the language being used is well-specified. The determinism of a Clojure-on-JVM program would also be dependent on the particular code the Clojure compiler generates. In Common Lisp there is the Armed Bear Common Lisp implementation, which runs on a JVM. Does it benefit from JVM determinism or not? It probably does not, because the JVM is simply not aware of undefined behaviour that ABCL or Clojure are implicitly defining.
When it comes to having different platforms, it would also be necessary for any other compilers to generate semantically identical code. Different Clojure systems do _not_ do that. For example, arithmetic in ClojureScript uses JS floats where Clojure-on-JVM and others use integers of some size.
In my experience, writing a non-conforming CL program is hard, and much harder than writing a program without undefined behaviour in C. I am not sure why, other than vaguely suggesting the UB is more "localised" in some way. But there is also a modification of the ANSI standard being worked on, which attempts to eliminate undefined behaviour <https://github.com/s-expressionists/wscl>.
-
Collective Code Construction Contract
Common Lisp was standardised by an ANSI committee. Here is a list of issues that were voted on. Nowadays there is also the Well Specified Common Lisp project, but no issues have been voted on yet.
-
Why Lisp?
SICL is still an implementation of Common Lisp, and not of a new programming language (give or take some additional features, such as first-class global environments). That said, there is some overlap between the authors of SICL and the authors of Well Specified Common Lisp <https://github.com/s-expressionists/wscl>; but WSCL only really defines some undefined and contradictory behaviour in the ANSI Common Lisp specification.
-
Revisited: A casual Clojure / Common Lisp code/performance comparison
The HyperSpec is a (derived work of a) language specification - its job is precisely to explain infrequently used things in too much detail. (And it ironically fails in many places.) Generally, one does not want to read a specification, unless they know they need to check something specific.
PurefunctionPipelineDataflow
-
Goodbye, Clean Code
Implement relational data model and programming based on hash-map (NoSQL)
-
How can I learn functional programming?
The Math-based Grand Unified Programming Theory: The Pure Function Pipeline Data Flow with Principle-based Warehouse/Workshop Model
-
Does Intel have an answer (or developing one) for AMDs Infinity Fabric?
I criticized "AMD Infinity Fabric Architecture" at the end of my article "Prediction: Intel will use "RISC-V plus x86 compatibility layer" or "RISC-V plus x86 heterogeneous computing architecture" to develop a new generation of "warehouse/workshop model" CPU".
- The Math-based Grand Unified Programming Theory: The Pure Function Pipeline Data Flow with principle-based Warehouse/Workshop Model
-
What should I do to defend my rights if the architecture of the Apple M1 chip is plagiarized from my theory and architecture?
What's more, you're being somewhat liberal with your "invention" dates here anyway. I'm sure you realize that anyone can review the commit history to see when content was added to the repo. As of Nov 2020, the day Apple announced a fully operational and tested, ready-to-ship silicon package the repo was a just series of bullet points listing out well-known concepts of functional programming sprinkled with some religious analogies and inspirational quotes. The farther you go back in the repo commit history, the less content is there.
- Apple M1 Ultra's architecture is a mistake, and Why Apple is not the creator of the M1 architecture? (with comment from chip designer who have worked at Apple for decades)
- M1 Ultra's architecture is a mistake, and Why Apple is not the creator of the M1 architecture? (with comment from chip designers who have worked at Apple for decades)
What are some alternatives?
gophernotes - The Go kernel for Jupyter notebooks and nteract.
concurrencpp - Modern concurrency for C++. Tasks, executors, timers and C++20 coroutines to rule them all
nyxt - Nyxt - the hacker's browser.
SICL - A fresh implementation of Common Lisp
verona - Research programming language for concurrent ownership
whirlisp - A whirlwind Lisp adventure
clojurust - A proof of concept version of Clojure in Rust.
clim.flamegraph - Flamegraph-style visualization of sb-sprof results in CLIM
refterm - Reference monospace terminal renderer
BetterDummy - Unlock your displays on your Mac! Smooth scaling, HiDPI unlock, XDR/HDR extra brightness upscale, DDC, brightness and dimming, dummy displays, PIP and lots more! [Moved to: https://github.com/waydabber/BetterDisplay]
chromium - The official GitHub mirror of the Chromium source