if we don’t strip it off (or ignore) its declarative nature and hypermedia capabilities 2/2
-
-
I think the hypermedia nature is by far more important than declarative 1/
1 reply 0 retweets 0 likes -
in particular, the property that lets you get Resource A, display it in a browser, get 2/
1 reply 0 retweets 0 likes -
a link from it, open it in the same browser, and display Resource B... 3/
1 reply 0 retweets 1 like -
having to have a local mapping from URL->Resource (like twitter:// in iOS) doesn't qualify 4/
1 reply 0 retweets 0 likes -
and is much worse than any perceived limitations of non-declarativeness 5/
1 reply 0 retweets 0 likes -
further, over-rotating on declarativeness causes us to lose the plot on making apps 6/
1 reply 0 retweets 0 likes -
compliant with the universal hyperlinking property I described above, which is high-value 7/7
2 replies 0 retweets 0 likes -
is consumed by browsers to be too simplistic. There’s much more to the web outside of browsers. 2/2
1 reply 0 retweets 0 likes -
Replying to @TheAmazingRando @stilkov and
there's much more to the more general concept of hypermedia. Why conflate the two?
1 reply 0 retweets 0 likes
it really sounds like some kind of high-stakes terminology debate I'm not in on.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.