There seems to be a lack of coverage in geek news, despite a healthy academic community/journal etc and I was wondering why.
I've got my own reasons for not being enthused about the current field, but I am curious what other people think.
Here are some searches that you could try:
http://www.google.com/search?q=site%3Anews.ycombinator.com+p...
http://www.google.com/search?q=site%3Anews.ycombinator.com+c...
http://www.google.com/search?q=site%3Anews.ycombinator.com+c...
http://www.google.com/search?q=site%3Anews.ycombinator.com+f...
Modern day locusts is what they are.
There is a lot of activity in this area which has been dubbed "physical computing". See e.g. O'Reilly's Make quarterly and Sparkfun, which apparently does > $10 million in sales annually from selling electronics components and kits to hobbyists. I'm eagerly awaiting my first Arduino starter kit from them! ;)
http://www.oldcitypublishing.com/IJUC/IJUC.html
Basically it is too unconventional (chemical), faddy and not focussed on producing something usable by the average geek.
That sort of stuff is still interesting (for computing in odd situations) but is not what I am looking for. I suppose I wondering why there isn't the computer equivalent of a space elevator. That is something most people know about that can't be done with current tech but is physically plausible (but might still might be too hard to do). Something that might spark the equivalent of the spaceward foundation, but for computers.
The fleet architecture represents a different face of unconventional computing. One that geeks can get behind. However it concentrates on speed of processing. Looking at the costs of computing, increasing computational power per watt or flops is useful but does not address the dominant cost of owning and running a computer. The dominant costs, I think, are the costs of learning the system, administering them and programming them. This is not addressed by either of the above threads of research.
I have my own odd-ball ideas. Which I'm excited about. I just wanted to gauge opinion of HN type people.
But I do see a fair bit of discussion of researchy and novel UIs here, don't you? On the front page right now I see Heroku (reducing the cost of administering systems), Hummingbird (real-time web site analytics visualization), Android vs. iPhone (which is largely about ubiquity and UI), Chatroulette, the death of files in the iPhone/iPad UI (which sounds like goes right to the core of the "dominant costs" you're talking about), Nielsen's report on iPad usability, and UI design in Basecamp. And that's just above the fold!
1) Make the things humans have to do easier. UI/UX
2) Reduce the number of things humans have to do. While all modern hardware can calculate the same things (are universal) they have different security models which can affect how much maintenance the user has to do. Take capability based security, an old idea implemented in hardware in the IBM AS 400. Languages (E, Joe-E) based on it are currently being touted as a way to reduce the risk of malware infection, even if malware does get on the system it can't do much because the language VMs operate under a principle of least privilege.
If we are changing the Arch for performance (e.g. fleet) and can't make use of the performance with standard software we may want to change it in this way as well, to take advantage of the system.
To give a concrete example of how computer architectures can be changed for the better. If windows had capability based security at the low level it could pass bits of memory to the user land process by sharing a capability that gave it write access. Then the user land process could populate it, once it had finished and the kernel wanted to read it, they could revoke the the writeable permission. This would prevent this sort of attack
http://news.ycombinator.org/item?id=1331025
See this for an intro to the philosophy
http://www.erights.org/talks/virus-safe/index.html
3) Make the computer do the work for the human. Yes this is mainly an AI problem, but it also an architecture problem. If you want the system to manage things like your graphics card drivers for you, you have to make some decisions about the hardware. Which programs are allowed to try and manage the graphics card drivers, how can the user communicate what she wants in terms of graphics card drivers in a way that the computer will find unambiguous.
So yep, UI and UX, is important but it is only one possibly angle of attack, and not the one I'm interested in. Because people are doing fine work on it, while the others languish a bit.
> by sharing a capability that gave it write access.
> Then the userland process could populate it,
> once it had finished and the kernel wanted to read it,
> they could revoke the the writeable permission.
> This would prevent this sort of attack [apparently,
> confusing auditors with TOCTOU attacks on system call arguments]
Virtual memory mapping hardware is already roughly a capability system. The CPU doesn't maintain a list of ownerships and permissions for every page of physical memory; it puts capabilities to those pages into page tables. That's how KeyKOS was able to run efficiently on stock hardware.
Capability systems are indeed better for security in several ways, but this isn't one of them. The problem here is that the memory page is shareable between different user threads. You can solve this problem in a variety of ways, including the one you suggest. However, unmapping the page that a system-call argument lives in before invoking an auditor does not constitute implementing a capability system.
To a great extent, it seems like the move toward web apps is exactly a move toward a different security model in order to reduce the maintenance the user has to do, a model in which most apps are fairly limited in their authority. The same-origin policy still falls far short of full POLA, but it's a step. The project in this area I'm most excited about is Caja, which is what MarkM's working on these days.
Heh, I didn't know there were fellow people interested in keykos type stuff here. I'm fairly new to that and more interested in the 3rd thing you can do to reduce cost of ownership, having an adaptive computer background.
If you submit a link to caja here let me know and I'll upvote it. The cap-like stuff that the Marks were working on for delegating authority to web apps was also interesting. It does reduce the amount of maintenance the user has to do, they still have to pay for the web apps though, so depending upon the income of the user and cost of the service it might not reduce the total cost by much.