About Me

My photo
Currently working as a Pen Tester, I'm interested in Android and web apps.

Friday, 30 July 2010

The Wrong Platform

So I've made my decision, I think it's the wrong platform. Developing on SharePoint seems like a nightmare and for this project I would have to bend the platform to suit the needs of the system. There's plenty of resources out there where people talk about joining SharePoint Lists and manipulating Lists using Views and Web Parts but it's all unnecessary coding to get something simple to work! I can't guarantee the performance of the application or if it could be further developed due to the restrictions with storing data in SharePoint. Storing unrelated data with a 2000 item cap is bad. The project could not go from prototype to commercial release using SharePoint. To me SharePoint is aimed at people who can't code and just want a simple team website.

Sure it'll save me time as I don't have to code a user database or any lower level code but at the price I can't develop what I want, I'm restricted. It'll save time with testing too but I can see it getting messy.

I'm left scratching my head why SharePoint clumps information into a List and you can't use SQL. It's pointless having a system like that because there is so much power with SQL, I just don't know? I've read so many blogs and articles about developers constantly coming up with workaround for their SharePoint site and I don't want to be one of them. Also so many people frustrated trying to import a database into SharePoint.

I've come to dislike SharePoint without even getting stuck into it. Why use SharePoint when I can use PHP and MySQL. There are probably situations where SharePoint is a great idea but for this project it's not.

No comments:

Post a Comment