5 ms·
When I read the title, I was imagining something more theoretical, e.g. a URL encoding of lambda calculus terms.
by majewsky 10y ago
When I read the title, I was imagining something more theoretical, e.g. a URL encoding of lambda calculus terms.
- gavinpc 10y agoSame here. As others have indicated, that would be more consistent with the title (and more interesting). The more general idea is a content-addressable function repository, where, as you point out, code would have to be in some kind of normal form. Joe Armstrong toys with this idea in his talk "The mess we're in," one of my favorites. [0] [0] https://www.youtube.com/watch?v=lKXe3HUG2l4&t=33m10s https://www.youtube.com/watch?v=lKXe3HUG2l4&t=33m10s
- genericpseudo 10y agoMy semantic-web-loving cold dead heart disagrees with you on the "more interesting". The one really good idea in the whole Semantic Web train-wreck (and at this distance, I think it's fair to call it that) was that everything should have a negotiable, dereferencable URL. REST includes that core principle. A lot of single-page web apps make me sad because they've been designed without reference to that. If what you're building is genuinely an application, then I get it; but most of the time what you're building is a catalogue, and everything in that can have an address, so it should.
- gavinpc 10y agoI agree 100% about catalogues and addressability. I'm also a diehard in that respect, and I've come to distinguish "apps" in a similar manner, as sites where either there's no "business case" for an ontology, or the content is too transient for it to matter. Naming is hard... I think that's what makes the "semantic web" a kind of chimera even for those who endorse it. Can a URL really capture the worldwide identity of a thing? Over all time? And who's going to maintain all those names? Suppose that naming everything is intractable as a human effort, but we still want addressability. Alan Kay takes this to the extreme, saying, why not give every object on the internet an IP address? [0] Not every resource, every object, in every program. It sounds facetious, but it's consistent with his general objects-as-computers-all-the-way-down view. His system designs (including those from VPRI) express the belief that hard barriers between the layers of a system (usage and application, application and framework, framework and OS) account for much of today's uncontrollable code bloat and the limits on how much scale systems can tolerate. The "everything gets an IP address" idea is just a recognition that network boundaries will eventually be seen the same way. From this perspective, it might be fruitful to think about how we'd identify things on the internet if they were homogenous with the objects in our applications. [0] It's in one of his talks but I don't remember which.
- jplur 10y agoStrongly agree! One of the reasons I'm excited about IPFS is for content addressable code linking. For example, running single js functions through google's closure compiler to normalize the symbols and using a package manager that would recursively replace IPFS links with the code.
- th0ma5 10y agoSort of reminds me of the Redfoot project for Python. It was sort of a URI based code repository...
- igravious 10y agoSame here! And then I went, "Uh oh, … CORBA strikes back!"
- bluejekyll 10y agoAm I the only one in the world that liked CORBA? I used ACE and TAO back in the day, and built multicast discovery mechanism to decentralize the ORB. Then the SOAP shitshow came to town, and now REST which is the rockstar, but people want better defined endpoints (RAML), um IDL was there in CORBA. REST is definitely easier to use than CORBA was, but it's much more limited, and it always feels like we're just reinventing the wheel. And yes, REST is better for web APIs, but it's always felt lacking after using CORBA.
- 1ris 10y agoCheck out Binary Lambda Calculus.
- lelf 10y agoSame. Was expecting something like http://www.haskellforall.com/2015/05/the-internet-of-code.html http://www.haskellforall.com/2015/05/the-internet-of-code.ht... https://github.com/Gabriel439/Haskell-Annah-Library https://github.com/Gabriel439/Haskell-Annah-Library
- mreid 10y agoIt's been a while since I looked at it, but I think Computational REST (CREST) tried to do something like that: http://www.erenkrantz.com/CREST/ http://www.erenkrantz.com/CREST/