|
You are here |
www.johnpapa.net | ||
| | | | |
zacs.site
|
|
| | | | | A few days ago, I decided to start an article about my writing setup. Over the years I have dialed it in, and today I have a pretty neat workflow. As I started on that piece, though, I realized that I had never talked about why I write in plain text. Most aspects of my workflow traces back to that choice, so today I want to explain some of the reasons I made it. | |
| | | | |
heydingus.net
|
|
| | | | | It took a few tries, but I've figured out how to use my favorite tools together to smoothly get from fleeting ideas to published blog posts. Let me | |
| | | | |
www.ssp.sh
|
|
| | | | | How (Neo)Vim and Markdown revolutionized my data engineering and writing workflow. | |
| | | | |
2ality.com
|
|
| | | Update 2012-01-22: "JavaScript myth: JavaScript needs a standard bytecode" is an updated version of this blog post. The web and thus JavaScript is slowly turning into a great platform. Part of the allure of the (partially) competing Java platform is that it has a core that goes beyond "Java the language": The Java Virtual Machine (JVM). There are now many languages that target the JVM, for example: Groovy, JRuby, Fantom, Jython, Scala, ABCL, Clojure, and Gosu. Java class files store JVM programs as Java bytecode, a compact binary format that source code is compiled to. Does JavaScript have something similar? | ||