cozy in a mac rom scarf. specifically this is a slice of the ROM from a Macintosh IIsi. here's how it was made. i used @th 's script github.com/osresearch/prom/blo… and the mac roms on archive dot org archive.org/details/mac_rom_ar…
if you have ImageMagick already installed:
$ perl hex2png.pl -y 1280 -w 32 mac_rom_archive_-_as_of_8-19-2011/36B7FB6C\ -\ Mac\ IIsi.ROM \ | convert - maciisi.png
Then a slice four columns wide was taken of the resulting image and knit into a scarf. The scarf is 1280 pixels/knit stitches long and therefore wraps natively in the columns of the scarf. if you want to make your own, you'll need a hacked consumer knitting machine or an industrial knitting machine or someone with a setup to machine knit it for you.
Macintosh ROM Archive : Free Download, Borrow, and Streaming : Internet Archive
A collection of dumped ROM chips relevant to earlier Macintosh-branded computers, for use in research, emulation and recovery for older...Internet Archive
Federico Mena Quintero
in reply to probono • • •“Finding and reminding” revisited: appropriate metaphors for file organization at the desktop
B. Nardi (SGCH)NiceMicro
in reply to Federico Mena Quintero • • •@federicomena Based on how many times I've seen Windows computers with the desktop polluted with documents and other files, and the occasional folder when some of the files are related to the same thing...
I guess I have to agree with you. Most people don't care.
Garrett LeSage
in reply to probono • • •Wrong assumption. It's confusing for everyone but the most technical people.
I've been involved in FOSS since 1996 and even ran user studies testing the filesystem and Linux generally (around 2006, IIRC, part of the "BetterDesktop" effort we ran at Novell/SUSE). People generally don't understand filesystem hierarchy. They get lost navigating it and so do their files.
The reason why apps manage documents instead of people using a file manager is not nefarious. It's meant to be helpful.
matzipan
in reply to Garrett LeSage • • •Garrett LeSage
in reply to matzipan • • •probono
in reply to Garrett LeSage • • •probono
in reply to probono • • •Garrett LeSage
in reply to probono • • •@matzipan @talex5 The problem isn't putting a file "somewhere". The problem is finding that file later.
This has already been discussed forever ago. @federicomena gave several talks on this around a decade and a half ago.
Here's an interview he gave in 2011 that talks all about this subject:
derstandard.at/story/131846132…
Federico Mena-Quintero talks about the Document-Centric Desktop
DER STANDARDAbandoned
in reply to Garrett LeSage • • •Garrett LeSage
in reply to Abandoned • • •@doctormo @matzipan @talex5 @federicomena As of right now, in 2022, these are all true:
The filesystem hasn't gone away.
Plugging in a phone (both iOS & Android) shows a filesystem with documents as files.
GNOME's file manager shows home directories and files by default. And you can navigate outside of $HOME if you really want to. Same for KDE's file manager.
The GTK and KDE file dialogs still show files and folders.
People in general still have problems navigating a filesystem.
Abandoned
in reply to Garrett LeSage • • •matzipan
in reply to Abandoned • • •Garrett LeSage
in reply to matzipan • • •@matzipan @doctormo @talex5 @federicomena Yeah, it's used in Flatpak.
What more needs to be done with xdg-datadirs? 🤔
Abandoned
in reply to Garrett LeSage • • •Federico Mena Quintero
in reply to Abandoned • • •@doctormo @garrett XDG specs need maintenance; they've been in "work well enough, a lot of work to change apps if the specs change" mode for a long time now.
Photos / templates / etc. are 2000s things, I think, partly from trying to be familiar with Windows/MacOS and Nautilus trying to be clever with templates (they are great for forms for expense reports!).
I like that both flatpaks and containerized services are converging on object capabilities even if done with ugly historical APIs.
Federico Mena Quintero
in reply to Federico Mena Quintero • • •@doctormo @garrett For example, .local and .config and friends were a way to avoid the proliferation of app-specific dotfiles or dot-dirs, and now flatpak really formalizes what goes in them. It's only of interest to sysadmins and really responsible app authors.
We wanted apps to control the data they create on behalf of users, without polluting already-messy home directories even more. So, stuff things in dot-dirs. Once you have containers, they become really useful.
Abandoned
in reply to Federico Mena Quintero • • •probono
in reply to Garrett LeSage • • •Project "XDG ng" · helloSystem/hello Wiki
GitHubFederico Mena Quintero
in reply to probono • • •Organise Framework - Semantic File Management
organise-fw.sourceforge.net