Places Feature Cut From Firefox 2

segphault writes "Apparently, the new bookmark and history system (called 'Places') scheduled for inclusion in Firefox 2 has been removed from the roadmap and disabled in the builds. An article at Ars Technica discusses some of the implications: 'Since Firefox 2 (and all alpha builds from here on out) will use the conventional bookmark system, those of you that have been using Firefox 2 alphas (the Gecko 1.8 branch) will have to export your bookmarks to HTML in order to preserve them. As a Firefox user and a software developer, I am personally very disappointed with the removal of this innovative feature.'" Update: 05/01 01:16 GMT by Z : Ars link updated.

Comments

Differentiation

[MrNonchalant]

I tried the Firefox 2 beta briefly and wasn't impressed. There's very little in the way of real differentiation from 1.5 and 1.5 had very little differentiation from 1.0. Prior to this improvement was obvious, now it seems like there are a few cosmetic and stability/security changes but nothing serious. If you take out Places for 2.0, what's really left? The close button'll be on the tabs, but that seems about the only user-visible improvement.

Re:So what are we missing?

[Jerf]

Let the master, jwz, rant about Mork (it's in the comments round about the second page for most people):

#
# And Now, The Ugly Truth Laid Bare:
#
# In Netscape Navigator 1.0 through 4.0, the history.db file was just a
# Berkeley DBM file. You could trivially bind to it from Perl, and
# pull out the URLs and last-access time. In Mozilla, this has been
# replaced with a "Mork" database for which no tools exist.
#
# Let me make it clear that McCusker is a complete barking lunatic.
# This is just about the stupidest file format I've ever seen.
#
# http://www.mozilla.org/mailnews/arch/mork/primer. txt
# http://jwz.livejournal.com/312657.html
# http://www.jwz.org/doc/mailsum.html
# http://bugzilla.mozilla.org/show_bug.cgi?id=24143 8
#
# In brief, let's count its sins:
#
# - Two different numerical namespaces that overlap.
#
# - It can't decide what kind of character-quoting syntax to use:
# Backslash? Hex encoding with dollar-sign?
#
# - C++ line comments are allowed sometimes, but sometimes // is just
# a pair of characters in a URL.
#
# - It goes to all this serious compression effort (two different
# string-interning hash tables) and then writes out Unicode strings
# without using UTF-8: writes out the unpacked wchar_t characters!
#
# - Worse, it hex-encodes each wchar_t with a 3-byte encoding,
# meaning the file size will be 3x or 6x (depending on whether
# whchar_t is 2 bytes or 4 bytes.)
#
# - It masquerades as a "textual" file format when in fact it's just
# another binary-blob file, except that it represents all its magic
# numbers in ASCII. It's not human-readable, it's not hand-editable,
# so the only benefit there is to the fact that it uses short lines
# and doesn't use binary characters is that it makes the file bigger.
# Oh wait, my mistake, that isn't actually a benefit at all.
#
# Pure comedy.