commit 51f543f9cb588efddaf78f1a04ae2c9c53195cc4 parent a5d8a69190b091675822b921d94bed95fda5b533 Author: viznut_web <viznut_web@web> Date: Mon, 20 Jun 2022 14:47:09 +0200 empty web commit Diffstat:
| M | retro.mdwn | | | 2 | +- |
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/retro.mdwn b/retro.mdwn @@ -7,7 +7,7 @@ The concept is problematic from the permacomputing point of view because: * It affirms the industrial definition of "platform death" and that there can be no genuinely new uses for a platform when it is "dead". * It separates the current time period from the "old times", thus creating an artificial mental boundary. - * While historical re-enactment and time capsules have their definite places and hardware [[lifespan maximization]] is an essential element of permacomputing, labelling all uses of old hardware or time-proven techniques as "retro" may actually discourage people from using them for new purposes. We need sustainable continuity rather than a culture where hardware eventually becomes "time-locked". + * While historical re-enactment and time capsules have their definite places and hardware [[lifespan maximization]] is an essential element of permacomputing, labelling all uses of old hardware or time-proven techniques as "retro" may actually discourage people from using them for new purposes. We need sustainable continuity rather than a culture where hardware eventually becomes "time-locked" (i.e., [[obsolete|obsolescence]]). The concept of **Zombie media** has a similar problem with affirming the industry-defined concept of media "death".