The JS API is total crap. One has to use it to develop anything that gets a bit more complex, but MS chose to ignore things that exists in the ES standard (like normal iterators, wtf) for quite some time to preserve backwards-compatibility with IE.
This make neither debugging nor any further exposure to the API any fun.
SP, like any standard platform (think i.e. SAP) invites the systems integrators to customize the crap out of it, which tends to impact the bad performance even more.
I see. We have some internal facing stuff that our IT has done using sharepoint. Its not pretty/modern by any stretch, but it works just fine. Was curious what the world looks like from the other side.
Isn't the search issue more of a indexing engine problem though? Can you plug in other engines?
The JS API is total crap. One has to use it to develop anything that gets a bit more complex, but MS chose to ignore things that exists in the ES standard (like normal iterators, wtf) for quite some time to preserve backwards-compatibility with IE. This make neither debugging nor any further exposure to the API any fun.
SP, like any standard platform (think i.e. SAP) invites the systems integrators to customize the crap out of it, which tends to impact the bad performance even more.
I see. Thanks for sharing your experience!
In my experience, Sharepoint is stupidly slow, and it feels like it's trying to be everything.
Like...I don't need it to notify me that I have new e-mail. I already have either Outlook or an Outlook tab running.
Sharepoint is a shining example of feature creep run wild.
I've never seen search work properly (where "properly" = 90+% of searches return desired document in first 2 results)
I see. We have some internal facing stuff that our IT has done using sharepoint. Its not pretty/modern by any stretch, but it works just fine. Was curious what the world looks like from the other side.
Isn't the search issue more of a indexing engine problem though? Can you plug in other engines?