💾 Archived View for jojolepro.com › blog › 2022-12-12_forever_computer › index.gmi captured on 2023-06-16 at 16:11:13. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2023-01-29)

-=-=-=-=-=-=-

Jojolepro

Blog

Projects

Music

Quotes

GitHub

Archives

re: Forever Computer

Ploum started an interesting conversation on what a computer that would last

a very long amount of time would look like.

gemini://ploum.be/2022-12-03-reinventing-how-we-use-computers.gmi

I have had some thoughts related to this too in the past and did some

experimenting with kiss linux to see how far we can push minimalism before

it becomes too limiting.

I have also noticed a trend which might be applicable to humanity in general,

which is that we almost always try to move forward: do more, faster, easier.

People focusing on security and stability, those who take less risks, will be

left behind.

The question is: are you fine being left behind for some things?

Are you fine doing plain old C programming when people are using rust and code

generation tools? Are you fine being constrained to an environment that will

feel slower and slower *compared to the alternatives*?

For this blog post, I propose the following method:

computer or if an alternative is needed.

Forever Computer Properties

the design is simple enough to be understood by most people

to be usable everywhere

Goals and use cases

Now for the complex part. Let's list all my use cases. *insert blob sweat emoji*

will give me good results)

passwords...)

Wew, that was a lot.

It's quite clear that we can't have a forever computer that does all this

currently: it would be huge and expensive!

Let's assume that all use cases are important and cannot be deleted, and see

how different things can/can't deal with them.

Y = it can

N = it cannot

The Paper Sheet

website will give me good results)

passwords...)

12 Y

35 N

So paper can cover 25% of our use cases. Not too bad!

Terminal Only Kiss Linux

I have some experience using a terminal-only environment in 2022.

Let's see how our many use cases that works for.

passwords...)

be missing a jack terminal frontend to do it)

34 Y

15 N

69% (nice) of use cases. Considering this is only using a terminal interface,

it's impressive!

If we add the ability to have a 2d interface, window manager and pointing

device but no graphics card, 7 N becomes Y for a total of 83% use cases.

What to do?

We often say: "use the right tool for the job."

Which we could also rewrite as "use the simplest tool that does the job just

as well as other tools".

But there's an issue with that: we lose convenience.

Ever did construction and you need to go back and forth multiple times to grab

different tools you forgot?

Using the simplest tool for the job would mean walking around with a pen,

notebook, simple computer and having a complex computer at home.

How inconvenient! There's a reason phones have an integrated camera, it's

to not walk around with 2 devices!

My understanding of the forever computer is that we want to make most of our

use cases portable: move them from our big laptops/big desktops into

a single portable and convenient device. And we want that to have a long

battery life and be future proof.

This isn't going towards simplicity, it is the same idea as what we saw in the

introduction: we are going forward, towards doing more and having more

convenience.

If you are ready to sacrifice use cases (as I did when I went full time on

kiss linux for a while), what will happen when you get bored?

The appeal of the new technologies is strong, because that's where all the

new shiny toys are at. That's where most of the fun (and frustration) is at.

And don't forget that we can't have it both ways. If we have both a forever

computer and a complex computer for the remaining use cases, it will be

extremely tempting to do everything on the complex computer. Why?

Because it is convenient to do everything on the same device.

Instead of starting to talk about hardware, I'll instead end this post on

more personal questions.

Are you ready to sacrifice use cases in the name of stability, security and

simplicity?

Are you ready to sacrifice convenience by using the simplest tool for the job?

Are you fine with being left behind? Or do you prefer the attraction of the

shiny new things?

How much effort are you willing to put into a system where you will gain

control and understanding, but lose on value (use cases solved by it)?

Let us know your thoughts in the mailing list

~lioploum/forevercomputer@list.sr.ht

or by making a post on your own blog

or by sending an email to jojolepro [at] jojolepro [dot] com

Thanks you for your time, I hope this was an interesting read!

(CC0) Joël Lupien 2020-2022

View page source