From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <9front-bounces@9front.inri.net> X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from 9front.inri.net (9front.inri.net [168.235.81.73]) by inbox.vuxu.org (Postfix) with ESMTP id 9E17822073 for ; Wed, 3 Apr 2024 22:43:38 +0200 (CEST) Received: from srv1.howhill.co.uk ([85.95.36.12]) by 9front; Wed Apr 3 16:42:31 -0400 2024 Received: from [192.168.1.223] (Ellychnia-corrusca.howhill.co.uk [192.168.1.223]) (Authenticated sender: willow) by srv1.howhill.co.uk (Postfix) with ESMTPSA id 37B1024C656 for <9front@9front.org>; Wed, 3 Apr 2024 21:42:29 +0100 (BST) DKIM-Filter: OpenDKIM Filter v2.11.0 srv1.howhill.co.uk 37B1024C656 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=howhill.com; s=default; t=1712176949; bh=LAIhHgSmHFiORsm0ZfRyOoGlK034Qu2P6B8XKPl7PTE=; h=Date:Subject:To:References:From:In-Reply-To:From; b=IZzfp4q/Zit92PDn90BdC7UALEhNcguoVLM85vA+kGy4CZLY5Bh5SkSkzOr2B7pZM WnD1UX+/f9sbJIysUuIyRfsrNLQ36+9NbqBNkfGWoicEA9WzO0m7/h3B23DDRXEiq/ +apD/UxCE0QyzbPIJUZrOEX7arugrAgLSQPDhuQ8o+oENvCwHyL+vuL6fx33iluORK 4x8qp5W/br74E3O2AdhLXhw9sJ/j0DOtONsnB93zM2yC7zsT54BCJ6MAgGoO3gBnvx t/bai2cWjD2yfNtqVO5iA5OHSJNil0Iajzn7LHIfZ9sq9fbBlMa40jhm783qDavrUq 3ihnq0Uq7jq/g== Message-ID: <7833cb39-ccb1-4f04-89ac-aaab6f25b80e@howhill.com> Date: Wed, 3 Apr 2024 21:42:28 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: 9front@9front.org References: <9a2ec537-c6a5-4c44-8306-d12ebee98446@howhill.com> <25847D39-F21B-463F-922E-E49E98CC6D85@gmail.com> Content-Language: en-GB From: Willow Liquorice In-Reply-To: <25847D39-F21B-463F-922E-E49E98CC6D85@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed X-Rspamd-Server: srv1.howhill.co.uk X-Spamd-Result: default: False [-3.67 / 20.00]; BAYES_HAM(-2.92)[99.65%]; GENERIC_REPUTATION(-0.66)[-0.66446775922045]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ZERO(0.00)[0]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_DN_NONE(0.00)[] X-Rspamd-Queue-Id: 37B1024C656 Content-Transfer-Encoding: quoted-printable List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: rich-client-oriented STM event-scale locator Subject: Re: [9front] Musings on web browsers and office applications Reply-To: 9front@9front.org Precedence: bulk That's intriguing. What are those edge cases? On 01/04/2024 10:17, Pavel Renev wrote: > 1 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2024 =D0=B3. 02:13:38 UTC, Willo= w Liquorice =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> Hi, >> >> I've had Plan 9 on the brain for the past few months, and I read a pdf= fs in the recent conference proceedings, and I was wondering whether the = principles in that paper could be applied to create a file server for som= ething that uses the Document Object Model. >> >> You could then use the resulting directory tree in the core of a web b= rowser (HTML) or office application (OpenDocument / Office Open XML). >> >> Just off the top of my head, maybe an example HTML document could be r= epresented like this? >> >> html/ >> !attrs/ >> lang >> "en" >> 01 head/ >> 01 title/ >> 01 text >> "Test Page" >> 02 body/ >> 01 p/ >> !attrs/ >> class >> "dumb-stuff" >> 01 text >> "according to all known laws of aviation" >> 02 comment >> "why are you doing this" >> 03 em/ >> 01 text >> "there is no way that a bee should be able to fly" >> 04 comment >> "please stop" >> >> Consider "text in quotes" to be the contents of the files they appear = under. >> >> I think the scheme above would work to identify attributes: the direct= ory name would simply be an invalid tag name. >> >> What do you think? I don't know that much about 9P, so maybe there's a= better way of expressing the order of elements in a directory tree than = literally numbering the files and folders. >> >> - Willow >=20 > I tried something similar in the past and found out that >=20 > 1. it's slow: traversing file system involves a lot of syscalls and the= y are relatively expensive. >=20 > 2. it's not very useful: there are many edge cases that are pain to dea= l with in both server and client, and in practice attributes are way more= important than actual tag hierarchy. >=20 > If I were writing a web-browser-as-a-fs today, I'd make a single file p= er "tab" with a specialized DOM query language console inside, plus simil= ar files for CSS, JS and what else.