Slashdot Mirror
E2 and LJ, Comparing Content Management Systems
Anonymous Noder/LJ'er writes "Linux.com is running a story written by Slashdot's Krow, one of the authors of Slash comparing the LiveJournal site engine to the Everything2 engine. He went over the installs of the two engines and talks a bit about customizing both. I really like both sites so it is interesting to see someone talk about what makes them tick."
(p.s. do I get mod'd up for posting the first real comment?)
"I say we take off, nuke the site from orbit. It's the only way to be sure."
Comments about administration policy asside, I think that comparing the two isn't strictly fair. At least, not on absolute terms.
As a developer on both codebases, teh differences as I see them are basic: Ecore is about grouping and linking as sets, while lj is more about mass indexing of list-type data.
One of ecores main weekness is scalability, or lack thereof -- this is not a slam on teh code, but just an introspection on design. Because lj os more about this loose-linked list paradigm, it can easily scale and cluster on mutliple machine while ecore, with it's extreme data interlinking, is heaving right now with redesigns to allow that.
Of course, Ecore (or at least E2) has a much better XML interface, which is probably it's second strongest point. It's first strongest and most important is the concpet that everything is a node.
Hilary Rosen's speech was about her love of money and her desire to roll around naked in a pile of money.
Is a real run-down comparison between the everything engine, j2ee, zope, and webobjects.
Yeah, so if you're just doing some random weblog, it makes sense to look at things at the unabstract, content-management-system level. But some of us find more interesting the idea of a system that allows for you to create a website by attaching abstract prebuilt website components together, defining the kinds of pages that you will have on your site as types, and then allowing the website to be created on a backend by less tech-saavy users who are shielded by the system from the raw code. This is what the above four systems basically are.. and it is much more powerful than just a simple CMS, though you can certainly incorporate CMS features into something you make with it.
I have been looking for a web-based system to manage personal data. I don't mean calendar, contact list, etc, but more general things.
Basically I need a replacement for a filing cabinent that will let me upload documents (and maybe grab copies of web pages), store them in some sort of semantic web/catagory hierarchy, annotate them, replace them with updated versions etc. Ideally, the system would work with a wide variety of data types: pictures, pdfs, text files, html/xml, word documents etc.
Is there a system avaialable that does this sort of thing?
Why is it that the only posts worth reading are at -1? Hmm . . .