31–40 of 100 posts
Given the huge maintenance cost of immature computer architectures such as mips, 386, arm, arm64 and amd64, we decided to put our focus on the more mature and stable achitectures:
power64 and itanuim.
Therefore, all architectures other than power64 and itanium are thereby frozen, conserved and promoted to end of life.
Please consider RISC OS next!
Golang on RISC OS would be a truly ludicrous porting effort.
Webinar in progress (Google Meet) https://ftp.plan9.ts.net/webinar
Happy to answer any questions! A bunch of us are currently in https://meet.google.com/qre-gydb-mkv chatting about this. (Edit: the hour is over; we all left) The earlier Apr 1st blog post was https://tailscale.com/blog/tailscale-enterprise-plan-9-suppo...
Happy to answer any questions! A bunch of us are currently in https://meet.google.com/qre-gydb-mkv chatting about this. (Edit: the hour is over; we all left) The earlier Apr 1st blog post was https://tailscale.com/blog/tailscale-enterprise-plan-9-suppo...
[flagged]
Russ Cox is an absolute legend for committing to this joke.
Russ Cox is an absolute legend for committing to this joke.
Someone needs to convince Russ that it would be hilarious to have a full featured web browser in Plan 9.
Earlier quoted context omitted.
Someone needs to convince Russ that it would be hilarious to have a full featured web browser in Plan 9.
Doesn’t plan9 support frame buffers over 9p or something like that? You could probably write a wrapper that just forwards a Linux browser to a plan9 window
Earlier quoted context omitted.
I would worry less about other people being able to run rc scripts and more about them being able to read/edit them.
they're routinely very short, and the only non-obvious syntax for someone familiar with a C-like language is the ~ command and redirecting to stderr. They're pretty much always easier to read (and write) than bash scripts in general because of how little weird/surprising syntax there is. Not being a derivative of ALGOL has its perks. Most scripts are write-once:read-never, especially if you actually implement -h/--he…
I guess the answer is always “it depends”, but that generally has never been my experience with most things. Are you over-engineering the shit out of every script to the degree the script itself is a Turing complete machine and with enough —-help flags anything is possible? Most 40+ year old Unix tools with a thousand flags have their limits and you have to script around them to achieve things you want.
In my experience, eventually a business need will arise that require you to change a script. Are your coworkers comfortable changing these scripts or are you in the mind set of “that’s a simple enough change, I’ll do it”