@ucodery It make it easy to pick tools that does a single task #UnixPhilosophy ♥

It's hard to state how much these 300 odd pages have not only shaped the software I've written, systems I've developed, and the career I've had so far, but what increasingly seems to be a large part of my personality. 🤣

#introduction

#unix #unixphilosophy @robpike

Switched from a connected smart watch to a cheap #casio digital watch. It is liberating that this watch only does time-related things (time, alarm, timer, stopwatch) and it does these things very well: 10 years of battery life and a simple and consistent user interface. A material example of the #UnixPhilosophy.

https://en.wikipedia.org/wiki/Unix_philosophy

Rather than buying a #dildo with a built-in clit stimulator, I think it's more in the spirit of the #UNIXPhilosophy to buy the dildo and vibrator separately.

#ed is the standard editor. I'm https://www.gnu.org/fun/jokes/ed-msg.en.html was the actual man page for ed years old.

From what I understand, grep is from the ed `g/re/p` pattern - g for global, re being your regex, and p being print. Fun times!

Well, ed only operated on actual files, but there was a need to do the same thing but for streams. And wouldn't you know it, the #UnixPhilosophy pops up again: let's call the program `sed` for Stream ed!

In my case, I only want to display the first block of matches.

「 Though Mahoney’s interview suggests that the original symbol for pipes was “>,” in the 1994 book, “A Quarter Century of Unix,” McIlroy remembers when Thompson decided the symbol for pipes should instead be “|.” Thompson made the change “for a talk in London, because he couldn’t bear to reveal my ugly syntax.” 」
#Unix #UnixPhilosophy #OSDev #RetroProgramming

「 the philosophy that everybody started putting forth, “This is the Unix philosophy. Write programs that do one thing and do it well. Write programs to work together. Write programs that handle text streams, because that is a universal interface.” All of those ideas, which add up to the tool approach, might have been there in some unformed way prior to pipes, but they really they came in afterwards 」
#Unix #UnixPhilosophy #OSDev #RetroProgramming

「 Though Mahoney’s interview suggests that the original symbol for pipes was “>,” in the 1994 book, “A Quarter Century of Unix,” McIlroy remembers when Thompson decided the symbol for pipes should instead be “|.” Thompson made the change “for a talk in London, because he couldn’t bear to reveal my ugly syntax.” 」
#Unix #UnixPhilosophy #OSDev #RetroProgramming

「 Michael S. Mahoney, a science historian at Princeton University who created an oral history of Unix in 1989, argued that the day pipes were actually created marked a significant turning point for the Unix philosophy 」
— The New Stack
#Unix #UnixPhilosophy #Pipes #OSDev
https://thenewstack.io/pipe-how-the-system-call-that-ties-unix-together-came-about

Favorite init system?
#nosystemd #unix #unixphilosophy #artixlinux #voidlinux

I wonder if it's possible to live ones life according to the #unixphilosophy

I somehow missed this when it was announced last month:

#nushell is a, um, new shell. It aims to more strictly follow the #unixPhilosophy by spiting tasks up into smaller chunks/making more use of pipelines.

To do that, it treats data as tables of 2+ dimensions rather than as flat text, drawing a bit from #powershell but with a simpler design.

Not sure the benefits are large enough to convince me to switch, but it's an interesting idea.

http://www.jonathanturner.org/2019/08/introducing-nushell.html

I somehow missed this when it was announced last month:

#nushell is a, um, new shell. It aims to more strictly follow the #unixPhilosophy by spiting tasks up into smaller chunks/making more use of pipelines.

To do that, it treats data as tables of 2+ dimensions rather than as flat text, drawing a bit from #powershell but with a simpler design.

Not sure the benefits are large enough to convince me to switch, but it's an interesting idea.

http://www.jonathanturner.org/2019/08/introducing-nushell.html

^^^ is getting at a bigger-picture question: Is it simpler to have multiple small tools that work together (the #unixPhilosophy), at the cost of grafting together tools written in different languages, operating with different abstractions, that weren't designed to work together?

Or is it simpler to have a single, coherent abstraction, at the cost of code bloat and sacrificing some on the one-job-per tool front?

(Related to debates I've had with @emsenn in one direction and @sir in the other)

I'm trying to decide between two window manager setups:

1)
#dwm, manage windows https://dwm.suckless.org/
#dmenu, launch programs https://tools.suckless.org/dmenu/
#passmenu, access passwords
#dlarm, set alarm https://github.com/codesections/dlarm
#tmux, manage panes https://github.com/tmux/tmux/wiki
#run-or-raise, run program or focus it if already running https://github.com/Soft/run-or-raise

2)
#stumpwm, all of the above + more with extensive lisp config, https://stumpwm.github.io/

Which of these is simpler? Better? #unixPhilosophy

Yay, I finally found a way to follow the people I still want to read about from $birdsite...

* www.twitrss.me converts a Twitter feed to RSS
* https://bots.tinysubversions.com/convert/ converts RSS to ActivityPub

Result! I'm testing it now... Just gotta remember that I can't *reply* to those people here :)

#EverythingIsAPipe #UnixPhilosophy

@besserwisser
<mostly_joking_self_promotion>
Well, in that case, I've written a #minimalist password generator you should try!

#passgen is a CLI app to generate secure passphrases that are easy to type (for when you can't paste). And it follows the #unixPhilosophy, and lets you pipe it's output to standard-out (or, optionally, have it in your clipboard). https://passgen.codesections.com/

</mostly_joking_self_promotion>