Notices by sirjofri@mastodon.sdf.org

@lanodan @volpeon @sun oof. Not nice at all!

It's not only about "saving" the web, it's about _how_ you do it!

@sun @volpeon @lanodan what did they do?

@lanodan meanwhile plan9:
fd = create("myfile", OREAD, 0666);

@driusan @a one of the biggest lacks in my opinion is this: you can read a full year about everything around plan 9, all documentation, all man pages, even a basic installation. But once you set up a plan 9 system you're done and you need help. You need help using the system, you need help configuring it, and there's often just no documentation for you.

@chakuari portability-wise: everything is cross-compilable. Our kernel is portability-oriented, our libraries are, our programs usually are just portable as is (just compile them with the compiler for the target). The build system is built around that. Our dynamic namespaces help to execute the right binaries for our platform (no need for complex $path variable hacking)

@chakuari I guess you already read a lot about it? Then my guess is, just try it. There's plenty of ways to try it and to learn more about it. But keep in mind that plan 9 is not a unix and many design choices are based on a fully networked environment (a single plan 9 system may consist of many machines)

@chakuari speed-wise it's like unix should be: many small programs that do their task and do it well. We have a shell that's comparatively slow, but we never hit any bottlenecks with it, although half of our boot process is managed by it.

@chakuari quite easy, I use it for everything personal computing, nowadays. Though that's also rare at the moment because I don't do much personal stuff...

It is a small system that's simple to understand, so it helps me to maintain my sanity. It's a system that "just works" at some point and you don't have to live in a state of "configuring before you can start your work" (1/x)

@chakuari it's very consistent. While unix/linux had to patch fixes on issues that wouldn't exist if it were more consistent, plan 9 maintains a level of consistency so fixes like that aren't needed (though it also has its issues of course).

It has the best C dialect for developing applications, and you can usually compile the whole system within a few minutes. It's also source-based, you rarely get binaries. Just compile from source

@chakuari I guess security-wise we're also in a good position, but not because our system is extremely security-based, just we tunnel everything via one protocol and it's easy to maintain services (files in a directory is easier than managing iptables and hundreds of daemons via some obscure program).

@bagder good thing I don't need symlinks anymore... #plan9 #9front

I really hate the trend that #documentation is no longer written but the details are in video #tutorials, especially in #gamedev. I want to READ documentation, with graphics and explanation. On long pages with varying degrees of details. Not some obscure 50min video where I can find the missing piece of information in a single frame at minute 34. #unreal #ue5

@aeva @khm also, since I'm working on the abstraction level, it doesn't matter what the implementation does under the hood: pure cpu based, network grid based, native gpu, networked gpu, birds juggling electrons, ...

@aeva @khm that's interesting to know. I'm working on getting some level of vulkan support on plan 9, currently working on that for drawterm. Drawterm is like vnc for plan 9, but much more integrated and native, and it runs on any other major OS. With that gpu filesystem I'm developing you can use the gpu of the host OS on your plan 9 machine.

@brion
unix: "everything is a file"
plan 9: "liar"
9front: "😏"