wordwarvi VS sublime-scheme-alabaster

Word War vi - side scrolling shootem-up kind of like Williams Defender.

At a very high level, set up an array of objects in your game. Each object has the ability to draw itself, and move itself. Each iteration of the game, move all the objects, and draw all the objects and sample user input. Set up a timer to iterate the game 30 or 60 times per second. Here's one game I wrote in C that works in this way: Word War vi If you dig through old commits in the repo you can follow the development from the very beginning, which begins with just creating a GTK window with a button). Almost every commit in that repo should compile and run. There may be the odd one here or there that crashes, but 99% of them should be fine, so if you want to advance through the commit history and see how the game progressed over time, you can do that. I wouldn't presume say the code is exemplary by any stretch, but it's fairly straight forward, and it works.

> Semantic Bovinator

Heh. A long time ago I wrote a video game[1] somewhat similar to Williams Defender, and casting about for some sort of "theme" for the game, I hit upon the "editor wars", the ancient storied battle between vi and emacs. You are ostensibly "vi", (a little spaceship vaguely reminiscent of the Vipers from Battlestar Galactica) cruising through system memory, evading system processes, GDB instances, etc trying to recover your ".swp" files. How to represent Emacs? Obviously, via a giant blimp! and I could display all sorts of messages on the side of the blimp, singing the praises of Emacs, and disparaging fans of vi. And the Emacs blimp had a "memory leak", which meant that pieces of the xemacs source code would literally leak out of the back end of the blimp, with the letters floating lazily away, like smoke. So that meant I had to take a look at the xemacs source, dig through it and try to find some funny bits to put in. Of course, "semantic bovinate" jumped out at me.[2]

[1] https://github.com/smcameron/wordwarvi

Honorable mention probably goes to Word War vi

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