BeOS certainly was targeted at non regular users Windows could get email and browse the web just as well as Be perhaps even better in later years. BeOS was about advanced and innovative features and making using a computer better and easier not just getting the job done... Windows and Linux can get the job done its just what you have to go through to get there.
What would be wrong with making Haiku an unmatched OS for the Scientific and Power user community BeOS was supposed to have been unmatched for power users... multimedia multitasking etc... distributed compilation (icecream & distcc etc...)
another point is that you could offload mundane chores to a second perhaps older headless PC so you primary desktop is fast. I see no reason to tie this idea to any release schedule It's either a good idea or it is not... personally
I think its a good idea and should be considered for including in the API planning of R2 as in R1 it would probably be a cludge in R2 it could be made elegant.
From what I understand clustering consists of head node and sub nodes where either a binary is sent to the nodes to run or a packet is sent to be processed (ie SunGrid engine java based) or something along those lines.
Perhaps wherever an application wants something to be processed either of two things could happen
*a packet containing all the data and a c/c++ file for llvm to compile at runtime is sent out and once processed that packet communicates back its results
*or a c/c++ code file is sent out and a network filesystem is used to access needed data.
Being a general desktop OS is boring and once Haiku has 3D drivers, WebPositive and Encrypted WiFi it will be pretty complete on that front (assuming you don't mind koffice) .... I would think the devs would like to try something adventurous once in awhile.
If using llvm I think you could think of it as threaded interpreter/jit compiler running on multiple computers I wonder if clang could be modified to do this...
http://llvm.org/cmds/lli.html that is what I was looking for the head node would compile the code into llvm bytecode and the sub nodes would execute it with lli (llvm interpreter?) it should run on any platform or as a jit compiler on supported platforms. I think it would probably be best for the code to execute with as little privileges as possible and only able to write into a certain place once execution completes the data in the specified placed could be sent back to the head node (could be ram, disk, network share etc...).
@ColinG We had openMosix and all the other clustering libs on a rpm based PII/PIII cluster (centos 5) but the application we really wanted to get going was a massive hackfest for us as the installer was written in csh (there were jokes in that seemed to indicate it was surprising to the developer we had made it that far) I think we ccould have don't some cool things with povray (I learned a bit of povray enough to generate a few animations) but we ran out of time in the semester an I moved to a 4 year uni (though I still drop by there alot on the way home). I think openMosix or any other 3rd party lib would be the wrong way to go unless it was BSD licensed and could be forked into haiku.
Edit again!: I may be overthinking this a bit... so Would it be possible to extend the Be api to pass messages between apps not only the local machine but also any machine on the network that happens to be listening? I think that could also be used as a basis since then code that is running on the separate machine can communicate actively with the head node or any node it wants or do I misunderstand the concept of BeMessages? It would also need to be as low latency as possible.
Apparently this has been done on BeOS before to some extent (it isn't really secure at all for one thing) https://public.msli.com/lcs/jaf/SockHop/ perhaps the developer could be persuaded to donate the code to Haiku?