1 files changed, 51 insertions, 0 deletions
diff --git a/2021/talks/unix.md b/2021/talks/unix.md
new file mode 100644
index 00000000..2516aaec
--- /dev/null
+++ b/2021/talks/unix.md
@@ -0,0 +1,51 @@
+[[!meta title="GNU's Not UNIX: Why Emacs Demonstrates The UNIX Philosophy Isn't Always The Only Answer"]]
+[[!meta copyright="Copyright &copy; 2021 Daniel Rose"]]
+[[!inline pages="internal(2021/info/unix-nav)" raw="yes"]]
+
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# GNU's Not UNIX: Why Emacs Demonstrates The UNIX Philosophy Isn't Always The Only Answer
+Daniel Rose
+
+The talk targets users who are curious about computational philosophies,
+or those who might not know how to best utilise Emacs conceptually. The
+talk will cover what the UNIX philosophy is, the GNU Free Software
+principles, a typical (Neo)Vi(m) user's approach, and then how one might
+accomplish this in Emacs combining the aformentioned ideals. The
+listeners will learn how they can approach Emacs ideologically, and how
+blocking themselves into one philosophy or the other will limit their
+efficiency. Although you may be a veteran GNU/Linux and Emacs user,
+understanding how to use both philosophies together will still allow you
+to be more performant than without.
+
+
+
+# Outline
+
+-   5-10 minutes:
+    Cut out the portions of explaining the whole UNIX and GNU philosophies
+    and instead talk about concrete examples:
+    -   How can one limit their usage of CLI tools while still maintaining
+        the ideals of both.
+    -   How using CLI tools can still perfectly flow into Emacs.
+    -   How having all programs in Emacs and unified keybindings is akin
+        to a terminal user.
+
+<!--
+-   20 minutes:
+    Go more in-depth about both philosophies, and how the ideas can play
+    off each other. Follow the same outline of the 5-10 minute version but
+    in more detail and with more interactivity.
+
+-   40 minutes:
+    Based on the 20 minutes format, play more off the ideas of the
+    audience. Interact with them more, and ask for their input and
+    examples that they can contribute to the conversation. Use more
+    examples, demonstrate my workflow.
+-->
+
+
+[[!inline pages="internal(2021/info/unix-schedule)" raw="yes"]]
+
+[[!inline pages="internal(2021/info/unix-nav)" raw="yes"]]