Article URL: http://www.constitutionaldaily.com/index.php?id=737%3Athe-fierce-idiocy-of-new&format=html&option=com_content

Comments URL: https://news.ycombinator.com/item?id=8675824

Points: 5

# Comments: 0

BeOS and Plan 9 have such different concepts of OO that they're hard to compare. In BeOS, there's a C++ interface your applications have to conform to, and it's somewhat machine-centric. Your objects are live processes in memory.

Plan 9 guys tend not to like the design of HTTP ( http://http02.cat-v.org/ ) so don't tell anyone I used this illustration, but Plan 9 is OO similar to the way REST is.

In Plan 9 (and Inferno) your objects can be files on disk, structs in memory, devices, etc. Anything that can conform to the interface. The interface in this case is files. Your objects expose a filesystem, and you interact with them by means of the usual tools for file manipulation. The Acme editor exposes a filesystem, the clipboard ("snarf buffer") is a file, and the network is, instead of a group of special syscalls, a filesystem. So you could write a shell script that reads a URL from the snarf buffer, downloads the page it points to, and puts the content into a new window in Acme, in three or four lines, without using anything more complex than cat and echo.

The OS doesn't power down the antenna while there are open network connections. Did your tests wait long enough to turn off the antenna, was the test environment clean (i.e., nothing else using the network on the device, including your tests)?

AGPLv3

• [DH] doc/LICENSE

This is a terrible readme.

• [DH] .gitignore
• [DH] README

Start with a copied skeleton and the base64 implementation.

• [DH] cmd/base64.c
• [DH] cmd/mkfile
• [DH] mkfile

Load prefs.

• [DH] interp.go

And a couple more interjections.

I think whenever someone tries to argue with the copypasta, I'll just put them into the
interjection list.

   _______  ________________
  /  _/ _ \/  _/ __/_  __/ /
 _/ // // // // _/  / / / /__
/___/____/___/_/   /_/ /____/

• [DH] interj.go

ChangeLog

• [DH] doc/ChangeLog

ChangeLog embedded.

• [DH] embed.go

And also it has to get in the mkfile, obviously.

• [DH] mkfile