Designing Low Upkeep Software

• adama-lang

  26 104 9.9 Java

  A headless spreadsheet document container service.

Using a filesystem is underrated these days with web this or that. I'm debating relying only on the disk for my Adama platform (http://www.adama-lang.org/) where part of my thesis is that by combining mem, cpu, storage into a single node that ill get decent utilization once I figure out a durability story sorted out.

• single_file_libs

  12 8,646 0.0

  List of single-file C/C++ libraries.

> Like, why don't we just let projects be "done"? Things don't need to be maintained and updated for eternity.

This is generally why I opt for "single-file" libraries that do one simple task well. The smaller the library, the more likely it is "done". For example, do I want some insanely complex image library that handles every file format under the sun, or do I just want some basic one that allows me to output a simple JPEG?

I often find myself referring to "single_file_libs" repository: https://github.com/nothings/single_file_libs

Looking at the open issues, it doesn't appear to be actively maintained but it's still an incredibly good resource for "completed" projects.

• SurveyJS

  surveyjs.io sponsored

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

• webscripts

  1 17 5.9 Python

  Scripts for manipulating my website

I noticed on one of the files he uses lxml, that is not part of the standard library is this one of those do as I say not as I do?

https://github.com/jeffkaufman/webscripts/blob/b6a004790b464...

• collapseos

  96 4,405 0.0 C

  Discontinued Bootstrap post-collapse technology

Look into CollapseOS if you haven’t already!

https://collapseos.org/

• three.js

  449 98,873 9.9 JavaScript

  JavaScript 3D Library.

> The biggest piece is minimizing your dependencies, and limiting them to ones that value backwards compatibility

Three.js, of the most popular JS libraries, has the explicit policy of ignoring backward compatibility.

https://github.com/mrdoob/three.js/wiki/Migration-Guide

I find it not only irresponsible but arguably mean to other devs time and lives but apparently I'm in the minority. Every time I have to spend an afternoon or evening updating stuff instead of doing something new or visiting friends etc I silently curse the devs

• mu

  29 1,343 4.3 Assembly

  Soul of a tiny new machine. More thorough tests → More comprehensible and rewrite-friendly software → More resilient society. (by akkartik)

I was just telling someone[1] that I explored Forth for this exact purpose a few years ago, but ended up with a more imperative, statement-oriented approach: https://github.com/akkartik/mu

[1] https://merveilles.town/@akkartik/106978783913724906

• unmaintained.tech

  8 511 0.0 HTML

  No Maintenance Intended

Have you considered a "no maintenance intended" badge on those repos?

https://unmaintained.tech/

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• pyenv

  261 36,723 8.9 Roff

  Simple Python version management

  

> pyenv as he mentioned is a common tool.

Pyenv is not a "common tool". It's used by a very small minority of devs since:

- it's used only by dev, and half of the python coders are not devs

- it works only on unix. Most people install python on windows (https://discuss.python.org/t/python-download-stats-for-may-2..., and that doesn't take in consideration anaconda or the appstore). Unless you count the obscure fork used by even less people.

- And yet on mac, if they don't use the official installer, they use mostly brew, not pyenv. On Linux, the officials repos or things like deadnsnake or epel. And of course docker. Pyenv is a tiny fractions of that, because any alternative solution is better known and easier.

- hard to use because it compiles things, fails easily in non obvious ways and assume you manage the path correctly, so it's really, really, popular only with people that want to deal with that. In fact the setups instructions are huge: https://github.com/pyenv/pyenv#how-it-works

- that's just what we see in the field. I go to a lot of different shops every years because I'm a freelancers, and I encountered pyenv twice in 10 years.

> That it happens to compile under the hood is an implementation detail that users may not even be aware off.

Of course not. The setup docs themself tell you to "Install Python build dependencies before attempting to install a new Python version.".

So not only you have to be aware of it, but you must be capable of setting up a compilation environment, and if you fail to do so, it will not work.

pyenv is not standard python. It's not "a common tool". It's a tool for a niche of specialists with domain specific knowledge.

Suggest a related project