Relatedly, what struck me while following the HTML5 spec development
is how they decided to specify existing browser behavior and add more
to the plate. Instead, they could have tried to decompose existing
elements to a smaller subset that would be more easily documented.
Maybe not down to
On 31 May 2011 16:30, Alan Kay alan.n...@yahoo.com wrote:
There are lots of egregiously wrong things in the web design. Perhaps one of
the simplest is that the browser folks have lacked the perspective to see
that the browser is not like an application, but like an OS. i.e. what it
really
On Fri, Jun 3, 2011 at 12:58 PM, C. Scott Ananian csc...@laptop.org wrote:
[...]
The web is not *only* an OS. It also provides the backing data for a
very large unstructured database. Google of course realize this, as
their company rests on a search engine. The semantic web folks have
Hi Scott,
I tend to agree with you. The uniform interface of the web (reduced
set of HTTP verbs, links...) is what make all these applications
possible. We know what to do when we have the URL to the flickr image.
But we could do so much more.
A simple multi-media document definition language
2011/6/3 Benoît Fleury benoit.fle...@gmail.com:
I tend to agree with you. The uniform interface of the web (reduced
set of HTTP verbs, links...) is what make all these applications
possible. We know what to do when we have the URL to the flickr image.
But we could do so much more.
I agree
For many, many moons, I've examined the early Smalltalk
books, small bootstrap Forth systems, Lisp based systems
(implementing a large subset of CL decades ago) and the like.
In recent years, I've taken an interest in type systems and
typed functional languages.
What is the relationship,
