vscode-theme-alabaster-dark
sixten
vscode-theme-alabaster-dark | sixten | |
---|---|---|
1 | 5 | |
7 | 748 | |
- | - | |
0.0 | 1.8 | |
over 2 years ago | over 3 years ago | |
Clojure | Haskell | |
MIT License | BSD 3-clause "New" or "Revised" 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.
vscode-theme-alabaster-dark
-
Tree Sitter and the Complications of Parsing Languages
While I don't fully disable syntax highlighting, I use a minimal theme [0,1] that only has highlighting for comments, strings and globals. It reduces eye strain, and I never find myself relying on highlighting to navigate through code. LSPs provide an "outline" which can be very useful to navigate through code. I find "jump to symbol" function in my text editor to be faster than scanning all of the code to find the line.
Also most themes dim the comments, but IMO if something in the code needed an explanation, it should be brighter, not dimmer.
[0]: https://github.com/tonsky/sublime-scheme-alabaster
[1]: https://github.com/gargakshit/vscode-theme-alabaster-dark
sixten
-
What do Haskellers think about Rust?
Immutable data structures don't necessarily require more memory: they can avoid deep copies. They are also automatically thread safe without expensive (slow) locking mechanisms. They also don't necessarily reduce cache locality. The reduced cache locality in the case of Haskell (I think) mainly comes from the representation of objects in its implementation (improved STG) which uses extensive boxing and jumps that hinder both spatial and temporal locality (require review/comment from GHC/Computer Architecture experts, take it with a grain of salt). Objects can be much more efficiently represented if not for the need to implement lazy (call-by-need) semantics. See sixten and futhark for examples.
-
Not well known programming languages with interesting features?
[Sixten](https://github.com/ollef/sixten): functional programming with unboxed data by default.
-
Tree Sitter and the Complications of Parsing Languages
I can't answer this well and don't know of any resources, but I have seen it before in the parser for sixten:
https://github.com/ollef/sixten/blob/60d46eee20abd62599badea85774a9365c81af45/src/Frontend/Parse.hs#L458
-
What languages have bit struct / field constructs?
Sixten is a language that allows precise control over memory layout of algebraic data types.
-
Designing a language where all types are memcpy/blittable.
For something more peripherally related, check out Sixten. Its focus is on using unboxed value representations, which is in spirit close to what you are proposing, and some of its ideas might be good inspiration.
What are some alternatives?
poet - An emacs theme that's well suited for modes using variable pitch: particularly org-mode and markdown-mode.
atom-focus-mode - Atom editor extension - fades editor content and highlights only the lines you are working on
pure - Pretty, minimal and fast ZSH prompt
tree-hugger - A light-weight, extendable, high level, universal code parser built on top of tree-sitter
rainbow-delimiters - Emacs rainbow delimiters mode
pony-tutorial - :horse: Tutorial for the Pony programming language
furo - A clean customizable documentation theme for Sphinx
felix - The Felix Programming Language
rust-analyzer - A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer]
ante - A safe, easy systems language
rust-analyzer - A Rust compiler front-end for IDEs
rainbow-identifiers - Rainbow identifier highlighting for Emacs