Re:Arrakis
by stephengillie on Wednesday May 21, 2014 @09:13PM
(#7781627)
At one time, all an Operating System did was load other programs into memory so the processor would run them instead. All of the sandboxing, garbage collection, security, and other features were added to make it more usable.
Correct. The usability gain was not having to (e.g.) write your own printer drivers if you wanted your program to use a printer. But if nowadays (e.g.) printer controllers are smart enough to take on most of the tasks that the OS abstracts from processes running in under it, then maybe we can turn that abstraction into a much thinner layer between the processes and the hardware.
> one day the browser might have daemons
It already does. Just write an extension and schedule a function. The one thing I don't think you can do yet is listen on a socket. At least not without doing a websocket connection to a separate service. Or bringing a native component with you.
Re:Arrakis
by icebraining on Thursday May 22, 2014 @04:29AM
(#7782731)
Firefox extensions can, and have always could. ChatZilla, for example, does direct access to IRC servers from Mozilla browsers since 2000, but even server sockets are possible[1]. Native components are also possible - they're called XPCOM components. Or you can use js-ctypes[2].
[1] https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/...
[2] https://developer.mozilla.org/en-US/docs/Mozilla/js-ctypes
I'd guess at the same time all these pieces will continue to become more distributed. Hypervisors and apps will present distributed environments (storage, processing, failover), even more than they do today.