> Also it's quite speculative how far one could get with JS which is
> essentially based on goja and domino.
Yes, JS works in more limited than netsurf, although the latter has a little
functions.
One big disadvantage is not having 'colspan'...
Kenji
Quoth Stuart Morrow :
> On 29/12/2020, sirjofri wrote:
> > ori's new filesystem
>
> What's this? and why is it needed? Hjfs already fixes the worst thing
> about cwfs already (needing to copy files from one partition to
> another on the same disk).
crash safety, corruption detection,
Thank you very much for your technical explanation, Philip.
By the way the file sizes of both are:
--rwxrwxr-x M 24 sys sys 51135788 Jan 7 15:33 /amd64/bin/netsurf
--rwxr-xr-x M 24 sys sys 15456437 Jan 7 09:32 /amd64/bin/opossum
Kenji
--
9fans: 9fans
On 29/12/2020, sirjofri wrote:
> ori's new filesystem
What's this? and why is it needed? Hjfs already fixes the worst thing
about cwfs already (needing to copy files from one partition to
another on the same disk).
Though speaking of new file servers, the Irssi /upgrade trick would be
good to
To be fair I think the rendering quality can be attributed to the html/css
processing. For instance parsing is completely done by golang.org/x/net/html
and github.com/aymerick/douceur. (Also one can get quite far with handling
display: inline/inline-block/flex and height/width attributes)
One
Quoth Joe S :
> hiro:
> The purpose of doing this was not to just access multiple parts of the
> file. I was working off the quote below. Maybe a file server thats purpose
> is to mux parts of another file sounded like fun. My thoughts are that you
> could then transer thoes chunks on a
http://git.pmikkelsen.com/ph/opossum
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T9a725c37f61954a8-Mf2d9006c5749e4decf646828
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
> Netsurf is written in C, and Opossum is in Go.
> Most basic difference is that opossum is written for Plan 9
> from the beginning which may be better for us...
>
One point in favour, from a Go fan: Go is far more maintainable than
C. I can think of some disadvantages, though.
As I can't find
> The problem is that throughput and responsiveness are enemies.
no. not throughput, but buffer sizes are the enemy of latency
> you're trying to push a large quantity of data down a TCP connection,
> and try to do anything interactive over that same connection, the
> latency will make that
