Hi,
I want to start this 2010 year thanking all the people that
have contributed to make Dillo what it is. It's been 10 years and
a long way lays behind. Lots of people have shared their
time/work/advice/help/money/. After all, what we have now is the
addition of all those efforts. Thanks to you all!!!
On Mon, Jan 04, 2010 at 11:38:03PM +0000, corvid wrote:
> Do we currently have anything that needs to be
> fixed/implemented before a release would be sensible?
Not that I remember. The only problem I recall was the error
message you reported with cookies and later seemed to be working
somehow.
Besides, AFAIS the repo is stable enough to start rolling the
release process.
BTW, the cookie story is frustrating. Generally speaking:
vested interests strive to kill commodity technologies to
introduce their own and henceforward profit monopoly-like. This
happens everywhere in the area we deal with e.g. HTTP, HTML,
SGML, XML, scripting, flash, java, video streams, audio, cookies,
AJAX, etc.
Remember that not even the big players were able (nor willing)
to implement the SPECS they co-designed.
Dillo's game so far had been to support a subset with emphasis
on efficiency and privacy. The game is never solved, the point is
to decide well where to prune (see bottom line).
Speaking of technology: Ten years ago it was images and tables,
the FTP, then CGI, then cookies (the stateless HTTP, now with
state), then frames (which faded 5 years later), then SGML (which
was replaced by XML), then XML (which never succeeded over HTML
tag soup). Then CSS (which is necessary these days. Despite IE
never gave much for it). Somewhere in the middle there was java
(and java beans), but it died. Then Flash, then AJAX, then
silverlight, the cloud...
IMHO, beyond the hyped technologies "du jour", Dillo is
relevant as long as it's able to serve as an efficient
information gathering tool, with emphasis on privacy.
--
Cheers
Jorge.-
