3 ms·
This is a great article & accurate in so many ways. We are lucky to have such great writing & distillation of the times as this; a fine treasure. This pairs ver
by rektide 3y ago
This is a great article & accurate in so many ways. We are lucky to have such great writing & distillation of the times as this; a fine treasure. This pairs very well & adds a lot of context to "What I want from the Internet"[1], which was submitted yesterday & which I am also very aglow over.
Both the rise of platforms & the smartphone are tightly interwoven around a new connected axis of computing emerging & being useful. McThrow somewhat generously includes the web in his "personal computing" vision but alas, even as a huge web fan, it's pretty clear that the brief "intertwingularizing" moment (which was extremely pro user) was giving way to Service as a Software Substitute (SaaSS), to a de-personalized experience. The relevance of desktop faded, and relevance faded because users were well served by new connected services. Software effervescing, sublimating up into the cloud made it easier to share, made it easier to access to demand, freed us from worrying about backups.
I think this is one of the critical junctures that Linux and the rest of the Desktops has failed to internalize, as a new need: the need to be connected. The need to be more than just isolated personal, the need to be available, the need to be connectable. I don't know quite what this future looks like or what it implies, but the "Linux on the desktop" spoke of competition with an outmoded, fading mode of computing. What was really needed was a further push onward, was a backbone for inter-app systems & development.
One of the few efforts here is one people love to hate on (even though I think most have a superficial at best grasp of the technics): One Laptop Per Child, OLPC/XOPC. My word what a wonderful & interesting system, powered by a grand already-well-adopted-on-FreeDesktop/Linux desktop bus (DBus) that underpins a wide variety of the software matter about. And then the team went further & built DBus Telepathy[2], to connect DBus instances to one a other, across the local 802.11s mesh the laptop had, to create a very compelling shared multi-player object stage that apps could use to create shared experiences. Stunning smart extension of existing highly personal intra-desktop tech into a connected form, a connected media; simply brilliant.
There's a couple reasons for hope in my view. First, the connected age is new & we are iterating & learning what broader connectivities work, and in there I think is the real base of power, the higher path that will be compelling for folks to get into. Nostr in particular has a very grand set of Nostr Implementation Possibilities[3] that shows how flexible the simple protocol is. But works like Dat, Hyper, ActivityPub, AtProto/BlueSky, Solid show a hunger & willingness to find out, to explore, at the base of a big tree of possibilities that more personal yet connected futures might emerge upon.
I'm also happy to see computing operations getting mature. It was a free for all, learn everything do everything, everything is different & unique, there are no standard all-encompassing routes until the last half decade. Love it or hate it but there is nothing as integrative & consistent for operating computing resources as Kubernetes. It's an incredibly simple pattern at heart, applicable to almost all computing, and its aspirations of being autonomic, self-maintaining, are such a compelling human-liberating spirit that server-hugging desperately needed. Even if it's not Kubernetes in the end, the spirit of an integrating platform for computing that can reasonably self-manage is a must, if we want personal computing to win. Personal computing has to become more than a machine, it just has to, the demands are too high, and we are not going back, and thankfully, we now have good mature sensible ways to weave together the thousands of different threads of running these online endpoints ourselves. We'll keep getting better with smarter packaged implementations, and better tooling; the momentum is for real on & it's so good.
The hardest to hope for win is the Web, but it's to most essential. The web has a lot of good-hearted people who care about personal computing. But the forces stacked up are huge; the industrialization of the field has been epic. (And getting ghastly worse, with WebGPU canvases threatening to turn the screen into just a bunch of pixels, see Hixie's Towards a modern Web Stack[4] and Flutter CanvasKit implementation). Alas in my view many of the good, spirited radicals differentiate themselves negatively, regressively, with back to the land ethos rather than having willingness or interest in forward advancement, when what we need is ambition & striving & exploration forward, particularly by rejecting industrialized best practices & asking ourselves again & again what best serves the user, what is the most open & empowering routes we can find? What course forward would we lead?
I think there are some HyperCard-ish futures about in easy-ish reach, some explainable observable quick & interactive modes of computing, if we go hunting, and that the web is already almost the perfect material/medium. WebComponents are a key abstraction, and I'm not ashamed to say how thankful I am that the biggest most powerful tech companies are quickly adopting it en-mass & seeing great success (YouTube, GitHub, Google, Salesforce[5]), and that although underpublicized, it creates learnable moments & good offshoot tech (Stencil.js, Github's Catalyst, Google's Lit). Embedding app state into the DOM makes it malleable, makes it learnable in a way code isn't. My hope is we can start to create more visual editor like systems, where the page itself exposes it's own tools to better show the user the objects on the screen, and let's them play and explore more. Make the medium more live & interactable.
Yet this is still not enough. A more user-friendly web page medium still, and better ability to host endpoints, still leaves a whole question of what's in the middle & how does it work. It returns to the protocols like Nostr I mentioned above. Figuring out how to personalize the protocols, how to Augment Intellect (the highest mission, the Engelbartian vision) in computing needs so many levels of the stack to be illuminated & graspable.
And above all that stack, what is the experience? The world of applications, what most users use, is a lot of isolated systems. This hearkens back to the point of this submission, that personal computing had fallen, and in many ways it's because the at hand value to capture was upmarket, was higher level concerns: apps. Personal Computing fell away because each app is it's own fief, it's own walled garden, and we didn't emerge a broader system of computing that meaningfully intersected with and connected with thr apps. Isolated industrial experiences has been the name of the game for decades now, that brief Intertwingularity/Cluetrain Manifesto zeitgeist the late aughts aside. I've talked a lot about stack & technics, but ultimately a more integrative holistic stack has to be here to be useful, to serve the needs we have. Making HyperCard-y experiences that can interlink & coexist together on the canvas feels like a maybe possible vision here, something works like OpenSocial[6] were trying for during the greatest headiest API-based moments of computing history. It was a greater effort, but that attempt to stitch together widgets & data has some notable overlap with above mentioned Solid.
Overall, I'd emphasize that for computing to be personal, it has to be personalizable. It has to be the users, in some degree. On these simple grounds, I can think of no more direct & overarching a cause than the Malleable Systems Collective[7], which is a wonderful home-base for exploring what computing do, how it might get out of the imprisonment of the data keep, oops i mean data center, & back into the hands of users.
[1] https://www.chrbutler.com/what-i-want-from-the-internet https://www.chrbutler.com/what-i-want-from-the-internet https://news.ycombinator.com/item?id=35852516 https://news.ycombinator.com/item?id=35852516
[2] https://aosabook.org/en/v1/telepathy.html https://aosabook.org/en/v1/telepathy.html
[3] https://github.com/nostr-protocol/nips https://github.com/nostr-protocol/nips
[4] https://docs.google.com/document/d/1peUSMsvFGvqD5yKh3GprskLC3KVdAlLGOsK6gFoEOD0/edit?resourcekey=0-bPajpoo9IBZpG__-uCBE6w https://docs.google.com/document/d/1peUSMsvFGvqD5yKh3GprskLC... https://news.ycombinator.com/item?id=34612696 https://news.ycombinator.com/item?id=34612696
[5] https://levelup.gitconnected.com/web-components-at-big-tech-companies-youtube-84266bb507fd https://levelup.gitconnected.com/web-components-at-big-tech-...
[6] https://en.m.wikipedia.org/wiki/OpenSocial https://en.m.wikipedia.org/wiki/OpenSocial
[7] https://malleable.systems/ https://malleable.systems/
- jdougan 3y agoI think he misunderstands the state of STEPS. STEPS was impressive, however it was far from feature complete compared to a modern desktop. They didn't (and possibly can't) solve for the essential complexity in modern specifications. eg. If they had to implement HTML5 with quirks the size would have ballooned, no matter how beautiful and clean the implementation was. And then there are drivers, like the pile of closed source poop that are the broadcom wi-fi drivers. To really do it right, you have to open up all of the stack starting down in the hardware, and then socially engineer people to less complex and bloated standards. Without losing valued functionality. A very tall order.