Slashdot Mirror
Lotus vs. SharePoint
daria42 writes "An article at ZDNet pits the software collaboration kings against each other. IBM's Lotus Notes/Domino 7 goes head to head against Microsoft's SharePoint Portal Server 2003. 'If you don't have the resources dedicated to developing collaborative applications, don't have complex application or integration requirements or if you are focused on the Microsoft solution stack, SharePoint Portal Server 2003 is going to be hard to beat,' the review concludes."
I've used both apps, as a user, not a developer. I can say this with certitude: if I want something fast with reasonable workflow capabilities, I can get it out of Sharepoint. Aside from my corporation's resource constraints, development on Lotus is way over my head and thus useless to me. /Begin flamewar
Given that I spent the last four weeks designing and implementing a Plone intranet site because SharePoint turned out to be an unworkable solution for a 80 developer team that is distributed over 4 locations in the US, Japan and Europe, this "review" cracked me up.
Why not try infinity
I was just at a Microsoft SharePoint conference last wek in Seattle and I have to say I came away very impressed with the new features they will be releasing soon. The integration with the office suite is very impressive. I think this next release will put SharePoint over the top. The 2003 version is good, but this next version looks much, much better.
As a developer at a large bank which requires us not only to use Lotus Notes, but to have it open at all times so we can be sametimed and be alerted of new emails ... I have to say it blows. If it wasn't for me being a developer and getting a P4 2.5ghz 1.2gb ram pc ... I would shoot myself now. I view my co-workers (non-developers) pc's occasionally and they're chugging along on their P3 256mb ram pc ... ouch.
Really, the URL's are no different that UNC paths depending on how your SharePoint is setup. Instead of your path listed above, it might be http://sharepoint/IT/Documents/Folder/Coolstuff.xl s. The only convoluted part is that spaces are encoded into %20 which can be annoying.
All-in-all, I am very impressed with SharePoint 2003 and we keep finding more and more uses for it.
ÕÕ
I've been using basecamp http://www.basecamphq.com/ as a lightweight solution, and I really like it so far. I'm not sure about scaling it up to a large corporate level, but it has been great so far for my small team. The downside is all of your data is on their servers.
It uses a Software as a service model, pay as you go. So not GPL, but it does expose a HTTP/XML API that could easily be hacked with perl, python, etc.
The company http://www.37signals.com/ also offers a few other solutions. You may have heard of them through all of the RoR hype lately.
While I can say that I have found a bug or two, crashes are very rare. Missing dic files means that something is screwed up at the os level. You can get missing files with any application if you start deleting stuff at the os level. Random unread docs is usually only a problem if the user is sometimes reading from the web interface, and sometimes reading from the client interface. Of course sometimes it is because the document HAS been updated, and the database is set to flag updates to unread.
I can tell you this about Replication Errors. They work flawlessly. If you are getting replication conflicts, it is because you have different data on different Replicas, and the data was changed on each replica since the last replication. Save/Replication conflicts are not a failure of Notes/Domino. They are the proper handling of conflicting data. Most other platforms just pick one copy and indiscriminatly over write the other. This is general done by date, and is a very poor way to handle things. Of course if you want your data handled poorly, you can set Notes/Domino to just overwrite the older data.
The biggest curse of Notes/Domino is that for years, the Designer was the same application as the Developer. Given how easy it is to produce robust applications on this platform, many companies assigned the first user to be the developer. Now, I'm not saying that a secratary cannot be a good developer, but being a secratery certainly doesn't mean that you ARE a good developer.
I tested and pushed hard for theis one at a place I worked at:
http://www.cybozu.com/
then they hired an IT genius for a director or it who thought that the only true software is microsoft....
putting the 'B' in LGBTQ+
We use Sharepoint and Twiki nearly interchangeably at work. I don't have a problem with either of them. The people complaining about Sharepoint needing a lot of ActiveX controls must be using far more advanced features than are available on our installation. I access Sharepoint using Konqueror, Firefox, and Opera (on Linux) regularly and have never had any problems. I'll admit that I resisted when "they" started pushing Sharepoint on me since past experience with MS designed web applications has shown me their zeal to lock out everything but IE on Windows (*cough*MS Project Central*cough*)... but since using it, I have no complaints at all.
Typically, we use Sharepoint for any Microsoft formatted docs (xls, doc, ppt, etc) since Office 2003 has pretty decent support for Sharepoint built-in. Click on a spreadsheet and Excel will check it out, show you who is working on the file, and check it back in when you save. Pretty slick. Gnumeric comes pretty close in that it appears to check it out, but Sharepoint doesn't seem to recognize the checked out state so checking it back in is problematic.
We then use Twiki for docs that are more static (PDFs, typically) and for pages that are heavily customized. I'm sure that Sharepoint allows for very customized pages as well but we use what we know and we know Twiki.
I use our internal portal from Firefox. No troubles.
But don't let total ignorance of the product stop you from bashing it. This is, after all, Slashdot.