sixten VS sublime-scheme-alabaster

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.

[Sixten](https://github.com/ollef/sixten): functional programming with unboxed data by default.

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

Sixten is a language that allows precise control over memory layout of algebraic data types.

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.

I use Alabaster[1]. Contrary to most themes, it is quite minimalistic and it emphasises comments instead of de-emphasising them. I like the minimalism, because it lets me focus, instead of marking every single thing on the screen as a different colour of “important” making my head spin.

[1]: <https://github.com/tonsky/sublime-scheme-alabaster>

I have been tinkering away at my personal take on what a modern, monochrome-esque Emacs might look for some years now and it is finally in a place where I think other might find it useful. The approached draws wisdom from the realization that "highlighting everything is the same as highlighting nothing" and tries to remedy the de-facto practice of theme by way of fruit-salad with more considerate approach. Inspired by alabaster's use of backgrounds for subtle syntax highlighting, typographic ideals and my endlessly sore eyes, it leaves text a comfortable black/white while drawing attention to constants, comments, declarations, and strings. A customizeable highlight color (by default a golden beige) provides a bit of life to the otherwise monochrome palette.

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