concept: get on my lawn software.
a software design philosophy that believes good software ages like a fine wine. it shuns trends and salesmen disguised as programmers, shuns the fancy new framework. instead, gomls curates quality old software like a carefully tended forest. software that has stood the test of time, and, though it seems antiquated, it’s as robust as cast iron anvil.
2. RSYNC came out in June 1996, it is 23 years old. it is the only program that I trust for copying large files and large amounts of files between any two points. it natively supports ssh and, in some configurations, uses an extremely clever rolling checksum algorithm that makes me seriously question the sanity of games consoles and operating systems vendors who do not use RSYNC for system and software updates.
so that this list isn’t unixy stuff only
3. Excel, initial release, 1987, 32 years ago.
love it or hate it, excel gets shit done, it still gets shit done, and it’s been getting shit done for a very long time.
its fomula language and macros system fulfills the promise of users sooving their own problems in a way every other system has utterly failed, possibly because it’s cloaked from the ruinous grasp of “professional programmers” attempting to turn it into a “real” application platform.
> i basically used that quote because it was shorter than Explaining #tiddlywiki
for those that haven't heard of it, tw has: programmable macros, widgets, templating systems...
- build whole small apps inside
- on nodejs, call external programs in macros
- as i did, build a game data editor that reads arbitrary hjson files, makes data tiddlers, & exports to arbitrary formats
- program a way to display (or even edit) spreadsheets or such
though it starts as a system of cards
Yeah, I get that a big trait of hypercard isn't just its "self-editing function"/"f(g(x)) style templating" nature but that it was simple & before basically Every (!) modern thing with similar features
My thought while trying to list what #tiddlywiki does:
"...it may have scriptable components + customisable Everything templates but the non-js macro coding syntax is /hell/.
as verbose as hypertalk is, something more flexible in the way of it or lisp would have been Better"
@Valenoern i really had no idea tiddly wiki could do those things you listed and it has me intrigued. what I mean by hypercard’s simplicity can be summed up as “easy things are easy, hard things are possible”. concretely, flash authoring tool started out as an obvious hypercard clone. as the versions progressed though, you want from “select button, pick goto, pick frame” to “create mybutton.as file and write a class that extends as.core.widgets.button. override the click method with…”
@Valenoern in the pursuit of OOP, i think, a lot of people got obsessed with the mechanics, and missed that the point of OOP was originally to enable these codeless methods of building interactive apps.
For people who care about, support, or build Free, Libre, and Open Source Software (FLOSS).