"This site uses features not available in older browsers." It is difficult to express the degree of my frustration with C2 being rewritten from a gunmetal HTML page that worked everywhere into an inaccessible heavyweight SPA mess with a frankly bizarre UI.
It does look like just another bloated SPA, but Federated Wiki was a geniune advance when Ward was developing it a decade ago. Still is. Shame it hasn't caught on. I agree it was a mistake to move the existing c2 content into it. Maybe a better try was to start a new wiki of some kind. But the temptation to leverage the existing site to launch Federated Wiki is understandable.
Tuple Space (2014)
21–30 of 56 posts
Re: Tuple Space (2014)
#22I remember when tuple spaces were the new hotness and going to a presentation from GigaSpaces at my local JUG. And now I can't even remember the problem they solve or any potential use cases. Weird.
Primary problem: Distribute work on heterogenous data across a cluster of heterogenous processes. Add new processes (either additional workers or additional capabilities) by attaching them to the existing shared tuple space. Add new data by wrapping it into a tuple and tossing it into the pile. Add a processor for the new data by having it search for a pattern that picks up the new tuple. Similar concept behind messa…
In David Gelernter's original work, it's not just data. In Linda, it's possible to put Objects in, which are little executable (`eval` in Linda terms) which a processor can manipulate through whatever interface the tuple type exposes.
Re: Tuple Space (2014)
#23"This site uses features not available in older browsers." It is difficult to express the degree of my frustration with C2 being rewritten from a gunmetal HTML page that worked everywhere into an inaccessible heavyweight SPA mess with a frankly bizarre UI.
Re: Tuple Space (2014)
#24Another interesting technology that was inspired by tuple spaces is DDS which tries to be a distributed tuple space for communication between embedded/field devices. https://en.wikipedia.org/wiki/Data_Distribution_Service
what makes it a "tuple space" vs a "message queue" system?
Re: Tuple Space (2014)
#25I remember when tuple spaces were the new hotness and going to a presentation from GigaSpaces at my local JUG. And now I can't even remember the problem they solve or any potential use cases. Weird.
By having the producer gradually update the responses to all possible queries to a tuple space, completely on its own schedule, there is not even temporal coupling between it and the consumer.
Re: Tuple Space (2014)
#26Re: Tuple Space (2014)
#27"that is, TupleSpace won't work on the Internet, precisely because of its underlying "distributed shared memory" idea". anyone know why?
Lose a processor or a message and it's just lost. Try to address that with copy-put-take and you now have duplicates. Try to address that and you now have byzantine failures with no resolution or supporting tooling. So it's wonderfully simple until you need to do something outside of a single process and then it's useless.
Internet-friendly stuff generally has a hard requirement on being fault tolerant.
Re: Tuple Space (2014)
#28I always thought Tuple Spaces were a super cool idea and am a bit bummed out they never took off. JavaSpaces was based on the idea but had a somewhat limited release.
Is NoSQL close enough, so MongoDB etc displaced tuple spaces?
Re: Tuple Space (2014)
#29Re: Tuple Space (2014)
#30Earlier quoted context omitted.
While I agree that the current rendition is unfortunate, it's a bit amusing hearing someone say that the literal inventor of the wiki is a twisted ego that should be completely ignored.
I stand by my statement. Terrible people can build good things.