HN user

SixSigma

2,825 karma
Posts2
Comments2,652
View on HN

- Everything that's "designed to..." is "specifically designed to..."

I think there is a distinction between primary design criteria and secondary e.g. the difference between must and should.

Primary : must be capable of transporting fluid.

Secondary: should be red

Coming to the US I'm shocked at how easy a Debit Card transaction is. In Chipotle (fast food) the card is just swiped. No PIN, no Signature, nothing: give the card to the operative, they swipe it and hand it back, a practice obviously not restricted to Chipotle - but I guess that's similar to contactless paying which I use in the UK - though my friend has deliberately drilled through his card to disconnect the wireless bit.

For buying gas at an automated pump, at some places all I need is my Zip code.

It feels very unreal compared to the Signature to -> Chip & Pin systems I'm used to.

I have "Ask for photo ID" written on my signature strip - though I've never needed it.

Us - yes I am part of the plan9 community - though somewhat inactive at the moment - I'm doing a degree in Supply Chain Management so my focus is on that.

That's all well porting a plan9 to JS but it's the kernel services that make plan9 different.

"Everything is a file" is the core concept. The rest is just things built on top of that.

We have a boot CD, it boots in Qemu, we have an emulated environment that runs on on Linux/BSD in 9vx, we have mounting 9p in the Linux kernel, we have plan9ports in Linux/BSD.

If you want plan9 it's not hard to get!

Like I said, between the 100 of us we only scratched the surface of the power of that idea.

It is heartbreaking to know it sits there, unloved outside of our small community.

In Plan9 the file system is per process so I can choose to bind kremvax' network over mine in this shell window, then pentvax' network over min in another.

I think I'm right in sayig that if one has /net and /net.alt then /net is asked first and then /net.alt

I'm a bit rusty on the details

To make a connection a process open's its /net/tcp/ctrl file, writes a connection string, gets back a response. If that response is a number then it opens /net/tcp/1/ctrl and /net/tcp/1/data and read / writes data to the data and sees out of stream messages on ctrl. To close the connection one closes /net/tcp/1/ctrl

Everything is done via the 9p protocol. So if I can write code on my Arduino that understands 9p and a way to send/rec that data (e.g. serial but even SP1 or JTAG) to a Plan9 machine locally, then the Arduino itself could just open a tcp connection on kremvax.

Once you start layering these things on top of each other it gets a bit mind blowing and you get drunk on power. Then when you are forced back Linux or Windows you realise how dumb they are even with their fancy application software.

I'm work at a global logistics company. Manual typewriters are still somehow part of our workflow for filling in forms, not even carbon backed.

It boggles my mind why that hasn't been replaced by a PDF form. Perhaps IT being siloed in another building keeps such legacy going.