writing.exchange is one of the many independent Mastodon servers you can use to participate in the fediverse.
A small, intentional community for poets, authors, and every kind of writer.

Administered by:

Server stats:

339
active users

#unixphilosophy

1 post1 participant0 posts today
The #LispyGopherClimate #weekly #tech #podcast for 2025-04-02

Listen at: https://archives.anonradio.net/202504020000_screwtape.mp3

This week we will talk about the Unix Philosophy and how it compares and contrasts with whatever one might call the “Emacs Philosophy.”

The impetus for the discussion is a series of blog posts by @ramin_hal9001 called “Emacs fulfills the UNIX Philosophy”:

…as well as a fascinating discussion that took place over this past week on ActivityPub on the topic of the Unix philosophy and history of Lisp on Unix in which some very knowledgeable people have contributed anecdotes and facts.

#technology #programming #SoftwareEngineering #RetroComputing #lisp #r7rs #SchemeLang #UnixPhilosophy

This weeks #ClimateCrisis #haiku by @kentpitman
within each of us
our loved ones, in tiny form,
caring's innate yield
    company at a distance
    legacy in case of loss

Recently I switched from the default keyboard on my Android phone to Simple Keyboard from the F-Droid app. It doesn't have autocorrect, word suggestions, swiping/gesture support, or spyware.

I originally switched for privacy reasons, but I've noticed that my frustration with phone typing has gone down drastically. I was always struggling against autocorrect to not replace the wrong thing, and the auto capitalization and such never allowed me to develop any skill in typing precisely.

I'm much slower in typing now, but I feel so much more in control of the experience.

#android #fdroid #foss #unixphilosophy #typing

The Unix Philosophy died when every major Linux distribution decided SystemD was a good idea, and embedded it deeply into everything.

Nowadays, it's hard to enumerate and nearly impossible to replicate what software expects from a SystemD distribution when it's not running on SystemD, so of course I'm running SystemD.

#unixphilosophy #linux #systemd

Replied in thread

#ed is the standard editor. I'm gnu.org/fun/jokes/ed-msg.en.ht 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.

www.gnu.orgEd, man! !man ed- GNU Project - Free Software Foundation (FSF)
Continued thread
Conceptually all stages of a pipeline are run concurrently, but in reality it's more effective, especially on a constrained system, to run the first stage of pipeline until the pipe blocks, then run the next one, etc.

With many small programs, this means only one program needs to fit in RAM. You might be able to do things with a pipeline of five programs that would have run out of RAM if the code and data for the whole pipeline would have needed to be in RAM all at the same time!

So yet another useful abstract feature that might have been partly motivated by concrete constraints at the time!

TIL.

#PipesAndFilters #EarlyUnix #UnixPipelines #UnixPhilosophy
libranet.deLIBRANET.de | Search

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.

jonathanturner.org/2019/08/int

www.jonathanturner.orgIntroducing nushell
Replied in thread

@jalcine i'm not sure that there's anything wrong with #IRC as a protocol. as for your suggestions

playvicious.social/@jalcine/10

clients: if using a terminal, weechat is one of the most versatile well-doc'd pieces of #floss out there.

back-end re 'trend' implementation: this could be a great new project! yet i see how things like #matrix might impact hypothetical development of a let's-say-ircd++.

there's no reason quality IRC experience should be easily-accessible only to #unixPhilosophy hackers.

playvicious.socialJacky Alciné (@jalcine@playvicious.social)By Jacky Alciné
Continued thread

^^^ 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 dwm.suckless.org/
#dmenu, launch programs tools.suckless.org/dmenu/
#passmenu, access passwords
#dlarm, set alarm github.com/codesections/dlarm
#tmux, manage panes github.com/tmux/tmux/wiki
#run-or-raise, run program or focus it if already running github.com/Soft/run-or-raise

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

Which of these is simpler? Better? #unixPhilosophy

dwm.suckless.orgdwm - dynamic window manager | suckless.org software that sucks less