wscl
nyxt
wscl | nyxt | |
---|---|---|
4 | 150 | |
38 | 9,546 | |
- | 0.4% | |
6.9 | 9.8 | |
4 days ago | 3 days ago | |
TeX | Common Lisp | |
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.
nyxt
-
Google Common Lisp Style Guide
If someone invents another browser, Nyxt will be ready to wrap it with Common Lisp: https://github.com/atlas-engineer/nyxt
- Nyxt – The Hacker's Browser
-
Is there a bug in `watch-mode`?
I can't reproduce the bug report on flatpak. Bug reports should be reported at https://github.com/atlas-engineer/nyxt/issues/new/choose.
-
Rusty revenant Servo returns to render once more
For innovative new browsers, there's Nyxt: https://nyxt.atlas.engineer/
Both are looking for funding and sponsors.
- Nyxt browser: The hacker's browser
-
How about having an progress bar at the echo area???
good idea. I know there are some plans for this underway.... looks like just planning phase right now. https://github.com/atlas-engineer/nyxt/issues/3095
-
Web Environment Integrity API
I am not a hopeful romantic, but the EU has been investing on vendor neutral web-browsers like Nyxt [0] and the UR Browser [1] through the Horizon Europe program. I doubt that legislators (at least in the EU) will view this as a positive development, assuming EU legislators know what they are doing. On the other hand, lobbying by big tech is still very much a threat.
[0] https://nyxt.atlas.engineer/
[1] https://www.ur-browser.com/en-US
-
using keyboard
There are some keyboard centered browsers like Qutebrowser or Nyxt. For Firefox as well as for Chrome based browsers there exist several extensions to implement vim-like keybindings.
-
WEBKIT_DISABLE_SANDBOX_THIS_IS_DANGEROUS: Any alternatives?
Am I correct that this is not fixed until this issue is closed (I tried building from source the 3.3.0 release and master branch but both have the exact same issue)?
-
Dead link at nyxt.atlas.engineer
Go to the website -> Download -> Download for GNU/Linux -> Get Nyxt for GNU/Linux!
What are some alternatives?
gophernotes - The Go kernel for Jupyter notebooks and nteract.
qutebrowser - A keyboard-driven, vim-like browser based on Python and Qt.
SICL - A fresh implementation of Common Lisp
luakit - Fast, small, webkit based browser framework extensible by Lua.
whirlisp - A whirlwind Lisp adventure
blockit - WebKitGTK adblock extension with Brave's Rust-based adblock engine for backend.
clim.flamegraph - Flamegraph-style visualization of sb-sprof results in CLIM
emacs-application-framework - EAF, an extensible framework that revolutionizes the graphical capabilities of Emacs
ungoogled-chromium - Google Chromium, sans integration with Google
emacs-webkit - An Emacs Dynamic Module for WebKit, aka a fully fledged browser inside emacs
min - A fast, minimal browser that protects your privacy
exwm - Emacs X Window Manager