summaryrefslogtreecommitdiff
path: root/wired.txt
diff options
context:
space:
mode:
authorlxf <sng@luxagraf.net>2024-09-17 17:04:26 -0500
committerlxf <sng@luxagraf.net>2024-09-17 17:04:26 -0500
commitbd9bfef3d887d611f16888db5b09d932ebab31fb (patch)
treee7970870bde4169f5ad7aa5f138843938956610b /wired.txt
parent54871178e0b9a575aa92cffb0c65c14797f6bd03 (diff)
copy to google doc
Diffstat (limited to 'wired.txt')
-rw-r--r--wired.txt8
1 files changed, 5 insertions, 3 deletions
diff --git a/wired.txt b/wired.txt
index fad833d..c9c9953 100644
--- a/wired.txt
+++ b/wired.txt
@@ -51,9 +51,11 @@ nomad grill
# Darktable
-Every great piece of software starts with a problem. Good software solves the problem. Great software so elegantly solves the problem we forget that it ever existed. Writing machine code was a problem. Enter the compiler. Try to find someone who remembers that once upon a time writing machine code was the only way to program.
+Every great piece of software starts with a problem. Good software solves the problem. Great software so elegantly solves the problem we forget that it ever existed. Writing machine code was a problem. Enter the compiler. Try finding someone who remembers days when writing machine code was the only way to program.
-Elegance is in the eye of the beholder of course, consider for instance the elegance of Vim vs the mess that is emacs. I am told there are programmers who feel the opposite. Just kidding emacs users. Although I have never like emacs, LISP the would rate high on my list of elegant solutions.
+Elegance is in the eye of the beholder of course. Everyone sees elegance in their favorite text editor, though others may not. Some see elegance in various ways of the fibonnaci sequence, or writing a Perl script in the shape of a dolphin. tk etc
+
+If I were picking the ultimate in elegance I would pick something that might seem obscure, but borders on the magical when you really think about it. It's not just one piece of software, but a chain of things that enable you to transform something you've seen in the real world into something that exists on your screen.
@@ -85,7 +87,7 @@ Perhaps the oddest part of programming is that these two factors, the producers
While there are doubtless exceptions, most major project splits I've witnessed have been related to personalities within the project more than the capabilities of the code. Think LibreOffice, which spun off of OpenOffice in major part because the developers wanted a more egalitarian project structure, or NextCloud, which was forked from OwnCloud in part because, again, there were cultural differences between developers and the parent company. There are plenty of other examples. WordPress forked from b2, MariaDB from MySQL, Tenacity from Audacity.
-In every case the project that ends up continuing is the one that draws in the most developers and consequently users.
+In every case the project that ends up continuing is the one that draws in the most developers and most users.
Software without developers quickly dies. This is obvious. What's less obvious is that software without users quickly does the same. Developers need users. The relationship between the two is what makes software more than code, more human.