Plan 9's not dead edition, presenting 9git

Plan 9's not dead edition, presenting 9git
The most obvious difference is that Git's index is a bit boneheaded, so I'm
ignoring it. The index doesn't affect the wire protocol, so this
isn't an interoperability issue, unless you share the same physical
repository on both Plan 9 and Unix. If you do, expect them to disagree
about the files that have been modified in the working copy.

In fact, the entire concept of the staging area has been dropped, as
it's both confusing and clunky. There are now only three states that
files can be in: 'untracked', 'dirty', and 'committed'. Tracking is
done with empty files under .git/index9/{removed,tracked}/path/to/file.

It's implemented in Plan 9 flavor C, and provides tools for writing
repository contents, and a file system for read-only access, which
will mirror the current state of the repository.

bitbucket.org/oridb/git9

What's your excuse now?

Attached: 9front-logo.png (1024x1024, 66K)

Other urls found in this thread:

sel4.systems/pipermail/devel/2017-September/001634.html
twitter.com/SFWRedditVideos

it's still terribly designed

Insightful comment

>9git
awesome, something I've wanted for a long time

>What's your excuse now?
no elixir port

9bump

every evening i go to sleep i hope that one day i will wake up, open my thinkpad, cpu(1) into my server i rent per cpu time and continue working on project i left over unfinished yesterday

Attached: callingdicktracy.png (500x647, 354K)

thank you 9ye, very cool!

computer technology is the only area where I'm a fan of diversity. it's nice to have the big 3 operating systems but we need more people doing cool stuff with all the other OSes.

Can you imagine how cool and futuristic computig will be if Plan 9 were widely adopted?

Is this my thread?

Attached: cirno.jpg (225x225, 12K)

>OS design is based on file servers and synthetic files
>VFS is implemented in kernel
literally why the fuck

No. You're drunk

kernel itself is generic, you can throw it out and replace it with, for example, seL4 and implement lacking plan9 syscalls as a readonly shared page mapped into every process (thread)

:(

Now, apply that to Windows/Linux

>kernel itself is generic, you can throw it out and replace it with, for example, Linux and implement lacking Windows syscalls as a readonly shared page mapped into every process using WINE

i'm not sure that would work with linux exactly the same way, although, wine-binfmt could provide you some comparable experience. also, i recall there was some effort to provide some support for windows PE/COFF binaries from the kernel, assuming wine

also, necessary mention: windows has about 1k winapi functions (syscalls) going into kernel, linux has about 500 syscalls and plan9 has 27 (14 of them is vfs)

as for plan9/seL4, see sel4.systems/pipermail/devel/2017-September/001634.html

Attached: cirno.jpg (500x375, 40K)

That's clever.

What's the downside?

slow

is the 9P driver on linux any good? is it a viable alternative to NFS?

Plan 9 C is what C should be. K&R and Plan 9 C, everything else is for cucks and was designed by committee.