"I have a mind like a steel... uh... thingy." Patrick Logan's weblog.

Search This Blog

Loading...

Wednesday, January 26, 2005

Why...

...is Sharepoint the suckiest thing on this planet?

15 comments:

Florian said...

Simple, it is slow as hell, provides the illusion of a repository, yet lacking features like synchronize, or checking in multiple files at once. On top of that it's acive-x fragfest which makes it only run on IExploder.

Anonymous said...

Slow? Try running it on real hardware. It's not slow for us.

We also have several employees using Firefox with SharePoint with very few problems. There are almost no activex components used. It's almost entirely html + jscript.

I recommend you talk about things you know -- SharePoint is obviously not one of them.

Patrick Logan said...

Speed is not the issue.

Anonymous said...

What is, then? ... those of us who don't have opportunity to use it but had guessed that it might suck want to know.

Anonymous said...

The average slashdot post has less trollness than this blog post.

Anonymous said...

Yeah, I have to second the other anonymous guy. It's your post, why not say why Sharepoint is the suckiest thing on the planet?

Greg said...

Hi Patrick,

Initial response: If speed is not the issue, then what is? I'd be interested know what you're referring to. Or are you just trolling for comment reaction to an inflammatory post?

Reasoned, thoughtful response: SharePoint does not suck. It's also not a cure-all for every single niche collaboration need on the planet. It's a good example of where Microsoft has developed a platform that is both deep and wide in it's scope, but where the custom functionality that might be needed by specific classes of users are left up to Microsoft's partner channel. That's pretty much the way Microsoft operates these days, by the way: Provide the platforms and enable the vertical channel partners to best meet the specific needs of the different customers.

Platform: SharePoint out of the box provides a basic set of fairly complex functionality, and allows the people who implement it to build upon it for their own purposes. For example, adding workflow or customizing the application, look/feel, webparts, etc. is a standard thing for people to do. It has (very) basic document management - if you want more, add it. It has some basic task mastering and issue tracking - if you want more, add project server or any one of several other products. Right out of the box you get integration with a variety of other Office System applications, like Outlook and Excel and Word and PowerPoint, OneNote, Live Communication Server, etc. It's a great starting point from which to build.

And that's really the point - you can use it just as it comes out of the box, but hopefully people will take the initial experience and build from there. SharePoint is as powerful as you make it. I can tell you that in my experience, where end users have adopted it and spent just a small amount of time setting up their lists and sites, the return has been huge, and teams are now doing things together collaboratively in one centralized place than they ever did before SharePoint.

What exactly were you hoping for from SharePoint? To say something sucks is a pretty pointed statement, and unless you can back it up, I'll have to take it with a grain of salt and write it off to trolling for a reaction...

With all due respect, of course. :)

Patrick Logan said...

As evidenced by my lack of evidence, I blogged this in a fit of frustration. I need to use Sharepoint primarily to schedule or to follow schedules, and as a file system.

The bottom line for me right now with just a beginner's experience of SP is that the developers could learn a thing or two from systems like Gmail. With all the widgets and whatnots for web interfaces these days, why is the interface to Sharepoint so damned non-functional?

Microsoft owns the file explorer and the Sharepoint "explorer" I guess it should be called. Why is one the Sharepoint explorer not even remotely as functional as the file explorer?

Anonymous said...

Probably because SharePoint explorer is a web based interface and Explorer is a desktop application (that can also host web pages)?

Did you know that SharePoint supports WebDAV so you can access document libraries with a network path like this
\\MySharePointServer\MySite\MyDocumentLibrary?

You can also map network drives.

Anonymous said...

Also, how would the developers have learned something from a product that wasn't released until long after theirs?

Patrick Logan said...

Please no more unimaginative defenses of Sharepoint on this blog.

Thanks. I'm done here.

Patrick Logan said...

But thanks for the WebDAV tip. I'll look into that.

Anonymous said...

Unimaginitive defenses for an incredibly uninformed attack?

Patrick Logan said...

Agreed. This was a spur of the moment rant, not an argument.

Web Hosting reviews said...

Great, Keep posting more blogs. Keep it up.
I have a best web hosting providers site. It pretty much covers best web hosting providers related stuff.
Thanks. Smile.

Blog Archive

About Me

Portland, Oregon, United States
I'm usually writing from my favorite location on the planet, the pacific northwest of the u.s. I write for myself only and unless otherwise specified my posts here should not be taken as representing an official position of my employer. Contact me at my gee mail account, username patrickdlogan.