Dreaming the future of software; Project Editor ECMAScript 2015;
Reformed Smalltalker
JavaScript historian dl.acm.org/doi/abs/10.114…
@allenwb@mastodon.social
Liberating our stuff" from mobile app lock in.
"I want to walk before I run. By creating a better model for mobile, the plan is to create a clear user understanding of what is “mine” and how this is seen, stored, shared, and acted upon."
Everybody wants to own the platform. Nobody wants to be on someone else’s platform. Result: small, anemic platforms (what I’ve called the CompuServe of Things). @pbusch42 at #eci2021 says the answer is the Economy of Things, a decentralized IoT metasystem. windley.com/archives/2021/07…
"...more than other networked software, tools for thought want to be owned. I don't want to store my second brain on someone else's computer... Maybe this is just a niche category, or maybe it could be the basis for a new open-ended ecosystem?"
On teletypes the corresponding key was labelled “rubout” and was used for correcting paper tape mispunches. It punched all bit positions (Ascii 127) so by backing up and pushing rubout you could erase a character on the tape—assuming the reader (HW or SW) ignored ascii 127.
If you want to make a long-term contribution to tech, make your users' data accessible through open file formats.
Software comes and goes, lots of planned obsolescence, but users' files tend to stick around.
it strikes a chord because it reframes the problem of 'how to make long-lasting software' around people and culture, rather than coming up with the perfect technology platform
I agree with this. It's the environment, or "the habitat", in which the work is done that is massively lacking.
Few things in that env will be collab multi-person edit simultaneously.
Importantly, in a real room, I can _see what others are working on._ Ambient context.
Collaborative multi-person editing is actually a pretty rare use case. I wish that much of the technical energy that is directed towards it was instead directed towards creating personal multi-device integration—a Personal Digital Habitat
wirfs-brock.com/allen/posts/…
I just don’t find 17 cursors mutating different parts of the same document simultaneously to be all that more effective than one person having control at a time (or every person having their own sub document), and it’s not like it solves 2 people making actual conflicting edits.
Yes, a file isn't "my stuff" unless it can be managed and meaningfully processed by a software agent of my choosing. Platforms should support this use case as the norm. For users, open formats > open source.
This is scary...if people are growing up with mental models where "documents" are subordinate to "apps" then the app itself becomes a walled garden. No user concepts/expectations of interchange/interoperability/competitive implementations of standard doc formats?
I suspect there are some conceptions that students hold, based on current computer usage, that are impeding students from developing the file/directory mental model...
...and I am sufficiently old that I cannot even guess how this might work.
The fundamental user abstraction of "file" is "my stuff". It's the digital stuff that a user owns and controls its usage. "Apps" and data encircled by apps is not "my stuff". I have accumulated decades worth of digital stuff. Almost none of it are still functional "app".
"Too many people think “Mobile is the Future” but we are so far past that. *Mobile is the present*. We need to actually be thinking about the future that is coming and what we are going to need."
Croquet has an impressive pedigree and looks intriguing as a foundation technology for a Personal Digital Habitat experience. I need to dig deeper. wirfs-brock.com/allen/posts/…croquet.io/faq/
With the recent uploads on Vimeo, we now have a full year of presentations available on line. Thanks to all the presenters and to everyone who attended our meetings!
Check out the videos at vimeo.com/ukstug
Even shorter: Silos are an emergent property of the most common web app architecture; interoperability is an emergent property of file centric app architectures.
By "large" internet I mean the original world-wide web as opposed to the "small" internet that denies the larger web's existence. The small claims to be more secure even though it is haunted by predatory giants with whom we do not want to associate.