Google "sgi trackball" for some interesting code to point the way.
660 karma · joined November 10, 2009
Google "sgi trackball" for some interesting code to point the way.
I've seen a few different fabrics in production (including proprietary non-public ones) and while I'm not sure IB is the answer Ethernet certainly has quite a few performance limitations.
Most of the systems C programmers I know, who admittedly work on large distributed systems, like Go.
Don't leave us comp geom geeks hanging.. Which one are you referring to? :-)
Input for computer graphics is very very hard. I've seen some great design work up close (Tinkercad) and this is one of the most interesting concepts in a while.
I do think you are on to something with the idea of pods, most farmhouses where I come from are arranged in a number of small separate buildings.
ABI compatibility just postulates that the bytes entering and leaving the interface will be marshalled the same way. However, the semantics of the function must by definition always change when you change the implementation.
You are arguing that these semantic changes are sometimes inconsequential, like for security updates. Based on my personal experience I think a more conservative view is appropriate and any changes to the dependencies of a program should be tested before large scale deployment.
Noe Valley is pretty nice and it's hard to say if it's more expensive than say Mountain View in the south.
The longer answer is that selling part of your business while continuing in a business that is in any way related is usually very challenging from a legal standpoint. The lawyers call it the "spaghetti effect", basically the IP tends to be really tangled. We had serendipitous developments a few weeks back in how Airstone is built which let us create a hermetic barrier between the Airstone and Tinkercad IP's. Before that happened we had no way of selling the IP without taking an unacceptable risk.
Airstone development will continue as before.
Edit: The site was down for 3 min and 32 s.