summaryrefslogblamecommitdiffstats
path: root/2021/talks/unix.md
blob: 17cd176c1fd9f470541bb3cd2066dada6044c098 (plain) (tree)
1
2
3
4
5
6
7
8
9
10









                                                                                                         

                                                               










                                                                        
            
 

                    













                                                                        




                                                                                                                                         


         
                                                                      
                           

                                                                    
                           
                                                                     
                   













                                                                          
                                                          
 
                                                          
[[!meta title="GNU's Not UNIX: Why Emacs Demonstrates The UNIX Philosophy Isn't Always The Only Answer"]]
[[!meta copyright="Copyright © 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

[[!inline pages="internal(2021/info/unix-schedule)" raw="yes"]]

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.

# Discussion

IRC nick: thecatster

-   Q: So, how do you decide when it\'s not \"worth it\" to use Emacs
    for a certain thing?
-   Q: What\'s your opinion on EAF?
-   Q: What is your opinion on starter-kits and making emacs
    accessible, practical for people who want to keep things simple?
-   Q: Do you integrate tools via Emacs or you just jump between those?
    For example, did you need to integrate your C WM somehow with Emacs?
    -   A: mostly via keybindings. Thanks for the answer!
-   Q: Do you use Emacs for email?
    -   A: I do, and many more clients too.
-   Q: No personal website?
    -   A: <https://www.danielr.xyz>
-   Q:When will Emacs improve its GC and support truely multithreading?

Feedback:

- I really appreciate this talk's perspective! I'm very invested in living inside, Emacs, but this is also a great perspective!
- yes, nice perspective. Saying that I am struggeling with that is overstating it, but sometimes it does make me think. thank you Daniel!
- Nice talk, I feel like some Emacs purists could complain but let's be honest, this is a reasonable take on actually getting stuff done

# Outline

-   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.
-   Why thinking about computational philosophies might itself be an 
        impediment.

<!--
-   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/captions/unix)" raw="yes"]]

[[!inline pages="internal(2021/info/unix-nav)" raw="yes"]]