Most of you probably hate it but is there any sharepoint devs around here?

Stuck at an unordinary customer request.

I know enough about SharePoint to fill up a jelly jar.

Unlike the d-bags on SO, there are usually decent folks on ...

https://sharepoint.stackexchange.com/...

If you need to know how to create your own custom SharePoint event receiver web parts (SharePoint Solutions) or inject javascript into a page, or <barf> create a custom view using XSL stylesheets, that's my hell right now ....run away and never turn back.

@PaperTrail have been working with it for 4 years, mostly script editor webparts for onprem and lately a lot of spfx for online.
I need to integrate a external webapp with sp rest or csom/jsom and i’m not really sure which route to choose. There is a few nodejs libraries (which is the backend used for the webapp), are they worth to try? Or is it better to build a .net api endpoint using csom to get the result? Or can i somehow consume the api straight from the clientside in the external app?

Sp2013 is the plattform in use.

@elwd Depends on which you are most comfortable with. Despite my hatred, SharePoint works really well. I've found the client-side javascript more forgiving with some of the sharepoint quirks, but having Visual Studio/C# intelli-sense is nice. Previous admins set up all the plumbing, so I don't know exactly how the magic works. Majority of code is added via the master page and events/methods are executed within the underlying .aspx pages.

ex. <input ... onclick="javascript:SaveClick()" />

javascript..

function SaveClick() { js magic}

That's my jelly jar worth of knowledge.

Sharepoint is shit, it’s the worst thing I worked on

@devTea I purposely keep myself ignorant. We've lost 3 decedent devs because they drew the short straw and decided to go 'all in' on SP admin/dev. They soon became the 'sharepoint guy' and never got out of the hole. Constant complaints of performance, why the search isn't as good as google, why does Chrome work and Edge doesn't, etc. They called MS tech support, days and weeks troubleshooting, etc for issues the users really don't care about.

Me? If Chrome works..use it.

Slow? Yea, its SharePoint.

Search for 'Vacation Policy' and its on the 3rd page of the search results (and we really only have one vacation policy doc)? Yea, SharePoint search isn't the best.

I've piss off several who feel I don't take my SharePoint duties serious. Not that don't care (I do care), but my usual response is "I can waste an entire month like John used to on these kind of issues, which if you remember, were never fixed, or I can continue working on the company's XYZ project. Which is it?"

If it's SP Online, the API should be externally accessible anyway for your app to consume