diff options
author | lxf <sng@luxagraf.net> | 2024-09-17 13:56:23 +0000 |
---|---|---|
committer | lxf <sng@luxagraf.net> | 2024-09-17 13:56:23 +0000 |
commit | 8cdc95f1a2f2cdebe5e386af9454ba9690d30a6a (patch) | |
tree | 9af996fcbb8a3db6551945a61b9a5556f821336a /wired.txt | |
parent | cc88d21f6fc34dc50e612f0c7c48a763e9bb2665 (diff) |
did some work on darktable
Diffstat (limited to 'wired.txt')
-rw-r--r-- | wired.txt | 14 |
1 files changed, 12 insertions, 2 deletions
@@ -51,9 +51,19 @@ nomad grill # Darktable -One of the great myths of free software (free as in freedom, not necessarily free as in beer) is that if it doesn't work the way you like, you can take the code, modify it to suit your needs, and go on your merry way. This is the cornerstone of the Free Software Foundations argument for why free software is better than proprietary software. While this is technically true -- the provisions for copying, modifying, and redistributing are governed by the licence -- it ignores the social reality that there is more to software than code. +Every great piece of software starts with a problem. Good software solves the problem. Great software makes you forget there ever was a problem. -The code is perhaps the least important part of a software project, particularly a large software project. The other two elements, the human elements, the developers and the users are the important part of software. These are the two elements that determine the fate of the code. 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. +One of the great myths of free software (free as in freedom, not necessarily free as in beer) is that if it doesn't work the way you like, you can take the code, modify it to suit your needs, and go on your merry way. This is the cornerstone of the Free Software Foundations argument for why free software is better than proprietary software. + +While this is technically true -- the provisions for copying, modifying, and redistributing are governed by the licence -- it ignores the social reality of programming. There is more to software than code. + +The code is perhaps the least important part of a software project, particularly a large software project. All software starts with a problem. Good software solves the problem. Great software moves beyond the problem entirely. Which is to say that code must be there, but at some point in the life of a software project the code takes a back seat to the other two elements at play, the human elements, the developers and the users. + +These are the two elements that determine the fate of the code (again, taking for granted that the code does in fact solve the problem). + +Perhaps the oddest part of programming is that these two factors, the producers and the users often end up producing a tension that can make or break projects. In the best cases this tension drives the project forward. From what I've witnessed over the years in the free software community successful projects have great leadership, whether that's a very talented individual or a governing body of individuals. What makes a great leader is difficult to say, it seems to vary by project even. + +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. |