 |
Blogs Schmogs
[reply]
|
04/23/04 09:04 AM EST
posted by JER email web |
|
I ran a search on Google for "Sharepoint sucks" to see if I'm the only one who just doesn't get it, and I found an interesting blog post about how Blogs as conversations suck.
Kearns & I had discussed this topic a little while ago, because we noticed that after the initial few posts to a blog topic, the conversation dissolves. I think trackback is meant to counter this in some way (?), but I haven't seen a compelling use of it that makes me want to add it to Shiny Donkey.
Has anyone else used Sharepoint Services yet? Whether you hate it or think it's the best thing since Jay Mohr, I'd like as much feedback as possible. |
|
|
|
| Next week I'm going to a Microsoft seminar that I hope will enlighten me to the genius of SharePoint. |
|
|
|
| And his largest complaint seems to be the missing back-and-forth. For just this reason I have the ability to email my responses to their comments and bring them back into the conversation... |
|
|
|
| I've never used sharepoint, but I hear it sucks, mostly from Jerry. On a related note, Jay Mohr is horrible, and I know he really does suck. |
|
|
|
| Sweet. Next week I expect a full report that either explains the glories of Sharepoint or verifies that Sharepoint is just a confusing web of document storage & messaging components. |
|
|
|
| My interest actually started with our Business Development guy stating that you could store calendar/event information in SharePoint, which was intriguing enough to me, but hopefully over the next 3 days I'll be able to tell you if it sucks or not, and why it sucks or not... |
|
[reply]
|
11/09/04 09:26 AM EST
posted by Joe |
|
I tend to agree that Sharepoint sucks. Using it is like closing your eyes, holding your breath and spinning around for thirty seconds. When your done you dont know where you are, you are very dizzy, and feel like you might throw up.
I might create something in one place, but cant delete it or rename it there. After 15 minutes of searching, I cant find the same tool I used yesterday to do one thing or another. Its like that house in 13 Ghosts, everything SEEMS to move around on you.
What really bothers me is this is not version one. It is a great idea gone horribly implemented. |
|
[reply]
|
01/04/05 01:23 AM EST
posted by billy email |
|
| read: Random Lingering in Isla Vista by J. Mike Knox cause it has a donkey on the cover |
|
|
|
Ok, I may need to revise my "Sharepoint sucks" statement. Sharepoint sucks if it's not configured and is simply in the default mode. With a few hours of planning, though, I was able to replace our intranet task mgt system with Sharepoint "issues," greatly modified to include "Hours Logged", "Estimated Hours", "Due Date", etc. Then custom views allowed me to create "My Tasks," "Tasks I've Assigned" and on down the gamut.
I'm not prepared to say that Sharepoint is great, but my opinion is moving to that side of the fence. |
|
[reply]
|
03/23/05 04:31 AM EST
posted by sqrv |
|
I've developing under sharepoint for the better part of this moth and I
have to say Sharepoint sucks big time. Sure, as long as you need only
the basic features, you're fine. But when you decide you need something
extra, even if it's so simple a web developer would implement in an
hour (say voting for documents), then you're in for a ride. Developing
for sharepoint is nothing but a nightmare. The system is overly
complex, unintuitive and just plain bizarre. I swear, we've spent
almost a week trying to implement some of the features, when we could
have written a fully functional php/postgresql site in that time.
Guess Microsoft development just isn't my cup of tea. hated developing with exchange and outlook, hate sharepoint.
To answer your question: no, sharepoint doesn't suck if you're a
marketing guy or secretary, who "just needs to do this or that as easy
as possible", but if you're a developer, then good luck.
|
|
|
|
So far I'm seeing a similar trend, sqrv.
Out of the box WSS/SPS seems super-d-duper and we're getting lots of good collaboration opportunities out of it.
I'm trying to migrate some discussions into it, however, and there are no tools to help with this. I'm forced to develop something in .NET (or theoretically anything that can do web services) if I wish to complete that migration. And the WSS object model isn't very straight-forward (though that's a bit typical for Microsoft, very dynamic OM for SPS). |
|
[reply]
|
07/20/05 08:27 AM EST
posted by ari |
|
| Share point sucks ****. It is confusing, the documentation is little or absent. However, all the higher ups at my corperation have accepted it with open arms because the consultants told them too. The consultants are now getting paid 60 dollars an hour to teach it. I hate share point. |
|
|
|
| Are the consultants two guys named "Bob"? Do you call them the Bobs? Do you work for Initech? |
|
[reply]
|
07/20/05 07:31 PM EST
posted by Jonny |
|
As one who has worked for more than one consulting firm, I have a
different perspective. Any consulting firm that wants to be on good
terms with Microsoft will push strongly for Sharepoint. Sharepoint and
Biztalk. I've even heard them refered to as the next level of
programming languages. We'll see what happens to this SOA trend, if it
catches on (look at Indigo) then I think we'll see more of Biztalk and
to some extent Sharepoint. Anyway, I just know I'm being strongly
encouraged to get certified in the two.
My cents
|
|
[reply]
|
02/07/07 05:00 PM EST
posted by mark |
|
I've been DEVELOPING with Sharepoint for a YEAR now. IT SUCKS, IT SUCKS, IT SUCKS....Try developing a web part and installing it in a Server Farm. Try moving configured lists from DEV to Production by creating Templates. Try customizing List Views for Paging. I have been a Microsoft Developer for about 8 years. I LOVE ASP.NET, C# and SQL Server. If you are a small mom and pop shop and just need UNSTRUCTURED data, like Contacts or an Issue Tracker, Sharepoint is fine. If you have a complex application with RELATIONAL DATA and COMPLEX OBJECTS, DO NOTNOTNOTNOTNOT put the DATA in Sharepoint. If you want to build Web Parts to hit a SQL Server, that is fine. If you want to build Web Parts that hit custom pages on a web application somewhere else, okay. They're may be security issues, but you can work around it(web services). But PLEASE don't try to build a COMPLETE Application that needs ANY TYPE OF Data Constraints/Foreign Keys, etc into SHAREPOINT. You will cry until you cut yourself. My users keep asking for certain functionality, and I say to myself, if I was using a Datagrid in ASP.NET, I could give that to them easily, but the Consultant I am working with just says, NO, because we are working with OOB Sharepoint. YES, we are customizing some Edit or NewItem Forms to put SOME custom Business Logic in, but overall, this whole app is ONE GIANT HACK. I will put Sharepoint on my Resume so people will know that I did some work this year, but if they want to hire me to build web parts, I will get up, and walk out of the interview.
take that to the bank.
|
|
[reply]
|
11/13/07 01:34 PM EST
posted by MJ |
|
Any web based tool sucks if you can't increase the font. Try changing text size in your browser and you will see nothing happens. This is the simplest thing to consider for any web app that supposed to reach thousands of users. If they didn't think about this simple accessibility issue then you can imagine what else they forgot.
I think no government agency can deploy any tool with an accessiblity issue like this.
I can give you a list of more than 100 problems like the above but don't want to waste everybody's time.
The bottom line is that the team in charge of developing sharepoint sucks (believe me I am an ex MS employee). Microsoft only has a few good teams (that # decreases every year thanks to Google and ...) and any thing that comes from other teams sucks big time. |
|
|
|
SharePoint is only good for what it was developed for: Collaboration. I think where SharePoint begins to suck is when management is sold on the fact that EVERYTHING needs to go into SharePoint. Then developers start thinking that SharePoint sucks...because if applications are expected to be developed in SharePoint, well, it sucks.
Build a web app using IIS, VS2005 and SQL Server 2005, just like you normally would. When you are finished, simply put the application dll(s) in the bin directory of the SharePoint website (c:\inetpub\wwwroot\wss\virtualdirectories\80\bin). Now to get the .aspx pages into SharePoint. SharePoint does not store the web pages as physical files. All the web pages in a SharePoint site are stored in the SQL Server backend. Lame. I don't think there could be a benefit to this that can possibly outweigh the lameness. So how do I get the .aspx files into SharePoint? Here's the easiest way: Open up SharePoint Designer. Open the site you wish to host the application in and drag the .aspx files into the site via SharePoint Designer. This will import the pages into the SharePoint database. Open SharePoint, go to the site, and hey, it works! Here is a good article that explains it a bit better than I just did (option 4 is what you need to look at). In the end, if you want to develop an application and host it in SharePoint, do it this way!!
http://blogs.msdn.com/cjohnson/archive/2006/09/05/application-development-on-moss-2007-amp-wss-v3.aspx |
|
|
|
SharePoint is only good for what it was developed for: Collaboration. I think where SharePoint begins to suck is when management is sold on the fact that EVERYTHING needs to go into SharePoint. Then developers start thinking that SharePoint sucks...because if applications are expected to be developed in SharePoint, well, it sucks.
Build a web app using IIS, VS2005 and SQL Server 2005, just like you normally would. When you are finished, simply put the application dll(s) in the bin directory of the SharePoint website (c:\inetpub\wwwroot\wss\virtualdirectories\80\bin). Now to get the .aspx pages into SharePoint. SharePoint does not store the web pages as physical files. All the web pages in a SharePoint site are stored in the SQL Server backend. Lame. I don't think there could be a benefit to this that can possibly outweigh the lameness. So how do I get the .aspx files into SharePoint? Here's the easiest way: Open up SharePoint Designer. Open the site you wish to host the application in and drag the .aspx files into the site via SharePoint Designer. This will import the pages into the SharePoint database. Open SharePoint, go to the site, and hey, it works! Here is a good article that explains it a bit better than I just did (option 4 is what you need to look at). In the end, if you want to develop an application and host it in SharePoint, do it this way!!
http://blogs.msdn.com/cjohnson/archive/2006/09/05/application-development-on-moss-2007-amp-wss-v3.aspx |
|
[reply]
|
12/07/07 03:10 PM EST
posted by Travis email |
|
| I have been forced to use sharepoint for the past 3 years and let me tell you, it sucks.....Unfortunately, it sucks a whole lot less than your alternatives. I work for a large fortune 500 company and we have currently over 1600 sharepoints sites.....we are running a portal of SPS and also have WSS available for all our teams to dynamically create. Like i said before, it sucks but NOT NEARLY as bad as the competition. |
|
[reply]
|
12/27/07 04:45 PM EST
posted by Georgia |
|
| SHAREPOINT - I HATE IT. End users are expected to use it? Gimme a break, they can't even find the my documents folder! This will create a mountain of work for IS! |
|
[reply]
|
02/18/08 09:59 AM EST
posted by ma70_guy |
|
it is a shame ms wanted to make things more complicated.
i have been writing "ok" asp.net apps for awhile now. and i am more confident on writing complex apps.
I would love to just "tap" into sharepoint sql data without the caml bs. But alas - it is too good to be true =(
sharepoint has some good things, but they ruined it with caml. what a waste of my resource - i have to learn one of those new "xml" standard again.
|
|
[reply]
|
02/20/08 08:46 PM EST
posted by bcw |
|
| I dislike SP, a lot. An earlier post noted that SP is good for what it was designed, collaboration. I'm not an IS person, but my work team uses SP in that capacity just fine -- it works well. Where SP sucks: our company suddenly believes that SP is a good tool to base our intranet on. OK, maybe over time I will be proved wrong. But now it's like moving from fluency in one language to an entirely new language. Our web guys can barely make the thing work correctly, so how are end users supposed to make it work correctly and design sites taht are easy for others to use, navigate and find information? We are going to end up with a bunch of lists and shared folders that store Word, Excel, and PPT files with absolutely no context to the documents and thousands of different ways that teams and "site admins" will use to present information. |
|
|
|
I am a SharePoint admin guy for my department, and have attended a $1500 SharPoint course that took two days.
It is not intuitive, and follows little of Windows years of established PC convention, like click and drag.
I have spoken to many who use sharepoint regularly. All are amazed how clunky and akward it is to use. The Reason to impliment is extreamly suspect as well. Many suspect it is a way for corporations to gather personal data workers.
In two words,
SharePoint sucks...... |
|
[reply]
|
04/16/08 02:50 PM EST
posted by adminguy |
|
its april 2008 and i can tell you that sharepoint sucks donkey balls! i have noooooo idea how this is making things better. All it does is it makes you buy more MS products and makes you buy a MS SQL server - The pathetic part is that i have to sell this to my users...ugh i'd rather convert the network to a linux
|
|
[reply]
|
08/29/08 03:11 PM EST
posted by Mike |
|
| I could not agree more with the comments on this board. I commend Microsoft for their progress with development tools, C# and Visual Studio are awesome and get better with each version. I've been developing for 15 years and struggled through the DLL hell era with VB, C++ and almost killed myself. Then came C# and Visual Studio 2003. Got better w/ VS2005 and almost Nirvana w/ VS 2008 (minus some SSRS quirks). Ahh, this is how it should be. Now enter SharePoint. Holy ****, ****ryin out loud! I hate SharePoint. There is absolutely no Software Dev process or is their any guidance. Try getting data into SharePoint via the SP Object Model and you will be asking for cyanide pills. I am on the verge of quitting IT again, but realized I just have to leave the SharePoint practice at my company and go back to C#. Downloaded the VS 2008 SharePoint extensions and ran the Solution Generator. It f'ng blew up when I hit Site Definition and clicked Next. Last Straw. God Speed to you developers who choose to suffer with this any further. |
|
[reply]
|
08/29/08 03:11 PM EST
posted by Mike |
|
| I could not agree more with the comments on this board. I commend Microsoft for their progress with development tools, C# and Visual Studio are awesome and get better with each version. I've been developing for 15 years and struggled through the DLL hell era with VB, C++ and almost killed myself. Then came C# and Visual Studio 2003. Got better w/ VS2005 and almost Nirvana w/ VS 2008 (minus some SSRS quirks). Ahh, this is how it should be. Now enter SharePoint. Holy ****, ****ryin out loud! I hate SharePoint. There is absolutely no Software Dev process or is their any guidance. Try getting data into SharePoint via the SP Object Model and you will be asking for cyanide pills. I am on the verge of quitting IT again, but realized I just have to leave the SharePoint practice at my company and go back to C#. Downloaded the VS 2008 SharePoint extensions and ran the Solution Generator. It f'ng blew up when I hit Site Definition and clicked Next. Last Straw. God Speed to you developers who choose to suffer with this any further. |
|
[reply]
|
08/29/08 03:12 PM EST
posted by Mike |
|
| I could not agree more with the comments on this board. I commend Microsoft for their progress with development tools, C# and Visual Studio are awesome and get better with each version. I've been developing for 15 years and struggled through the DLL hell era with VB, C++ and almost killed myself. Then came C# and Visual Studio 2003. Got better w/ VS2005 and almost Nirvana w/ VS 2008 (minus some SSRS quirks). Ahh, this is how it should be. Now enter SharePoint. Holy ****, ****ryin out loud! I hate SharePoint. There is absolutely no Software Dev process or is their any guidance. Try getting data into SharePoint via the SP Object Model and you will be asking for cyanide pills. I am on the verge of quitting IT again, but realized I just have to leave the SharePoint practice at my company and go back to C#. Downloaded the VS 2008 SharePoint extensions and ran the Solution Generator. It f'ng blew up when I hit Site Definition and clicked Next. Last Straw. God Speed to you developers who choose to suffer with this any further. |
|
[reply]
|
08/29/08 03:13 PM EST
posted by Mike |
|
| I could not agree more with the comments on this board. I commend Microsoft for their progress with development tools, C# and Visual Studio are awesome and get better with each version. I've been developing for 15 years and struggled through the DLL hell era with VB, C++ and almost killed myself. Then came C# and Visual Studio 2003. Got better w/ VS2005 and almost Nirvana w/ VS 2008 (minus some SSRS quirks). Ahh, this is how it should be. Now enter SharePoint. Holy ****, ****ryin out loud! I hate SharePoint. There is absolutely no Software Dev process or is their any guidance. Try getting data into SharePoint via the SP Object Model and you will be asking for cyanide pills. I am on the verge of quitting IT again, but realized I just have to leave the SharePoint practice at my company and go back to C#. Downloaded the VS 2008 SharePoint extensions and ran the Solution Generator. It f'ng blew up when I hit Site Definition and clicked Next. Last Straw. God Speed to you developers who choose to suffer with this any further. |
|
[reply]
|
08/29/08 03:13 PM EST
posted by Mike |
|
| I could not agree more with the comments on this board. I commend Microsoft for their progress with development tools, C# and Visual Studio are awesome and get better with each version. I've been developing for 15 years and struggled through the DLL hell era with VB, C++ and almost killed myself. Then came C# and Visual Studio 2003. Got better w/ VS2005 and almost Nirvana w/ VS 2008 (minus some SSRS quirks). Ahh, this is how it should be. Now enter SharePoint. Holy ****, ****ryin out loud! I hate SharePoint. There is absolutely no Software Dev process or is their any guidance. Try getting data into SharePoint via the SP Object Model and you will be asking for cyanide pills. I am on the verge of quitting IT again, but realized I just have to leave the SharePoint practice at my company and go back to C#. Downloaded the VS 2008 SharePoint extensions and ran the Solution Generator. It f'ng blew up when I hit Site Definition and clicked Next. Last Straw. God Speed to you developers who choose to suffer with this any further. |
|