From the comments on
the slashdot posting
... tieTYT tells an anecdote about what AOL did to Netscape:
[...]one of the things they did was realize that pop-up blocking was one of the new cool things for browsers to have. But the marketing team stepped in and said, "Hold on just a second. We can't have the browser blocking OUR pop-ups." So they added rule to block all pop-ups except those that came from the netscape web page.
The netscape homepage happened to have a pop-up on it and of course, this is the default home page of the browser. When you initially ran netscape, first thing you saw was a pop-up and the page behind it claiming, "New Feature: pop-up blocker".
You can't escape bad karma. What AOL does to Netscape, Time Warner tends to do to AOL. We'll see.
David Greenspan, JD Zamfirescu, and Aaron Iba have
Unlike OpenMocha, they went the extra miles of making the framework very approachable by well integrating AppJet online hosting of your custom apps, by designing the framework in a way that I think developers used to PHP like environments will appreciate and by gearing it towards very simple, small apps at the beginning.
is already visible online
I particularly like the way they encourage appjet apps to be an open collection, in a sense becoming an appjet code library. That's an aspect that already was very successful in the
old days of WebCrossing
and that I think is an essential part of a web-soft-coding environment.
Indeed, facilitating easy code reuse and sharing is a focal point that would benefit the Helma community at large as well. I need to setup something like a code bin, where we can easily upload, categorize, search and find code snippets for reuse in other Helma apps.
has ported the
js lib for working with couchdb
from AJAX and crockford's json to helma.http and helma's json support. Definitely a candidate for inclusion as part of the modules in the next Helma release, I'd say. Now, if we use the onInit and onPersist hooks and suppress the embedded db, we could directly leverage all the fancyness of HopObjects for
, including the caching :-)
On the other side, I hope we can still get more features into ES4 that increase its dynamic nature. Maybe some of what Doug Crockford has up his sleeve with ES3.1 can still go into ES4 *in addition* to what the majority of
So, churn TG1, churn. Bring us new ECMAScript revisions quickly. Don't hesitate to split things up into multiple specs, like you've done in the past with
. For example, a more flexible, less secure mode allowing embeddings to opt-out of the non-mutability for built-in types, offering macros and allowing even built-in keywords to be overridden can all make sense in some environments. So would a much more limited, more secured ECMAScript subset, defined as a separate opt-in standard, that could provide a jailed eval to embeddings that need it.
The use case in browsers is only a small part of the entire ECMAScript universe. Outside the world of browsers, maximizing flexibility can also mean to allow embeddings to run in different modes or to not require them to implement all ECMAScript subsets. So, not everything that is standardized under the name "ECMAScript" actually has to end up in web browsers!
Your email address:
The "Decentralize" Newsletter
Exchanging ideas for building a
decentralized fabric of society.
Making true democracy work on a larger
scale while decentralizing "everything",
benefiting from local diversity and
global synergies at the same time.