IssueRaiser

I can use text based API's (like with JSON) with nothing else but text editor and curl.

I can use text based API's (like with JSON) with nothing else but text editor and curl. No other tooling actually required. Meanwhile if binary protocol tooling in your stack sucks, then it just sucks. Had the joy of implementing calling SOAP service with client generated from wsdl in .net core 2/3 times. Tooling was shit poorly undocumented amd with crappy errors at that time. Run only with very specific versions in very specific way. And not much you can do about it, rolling your own SOAP client would be too expensive for our team. REST with JSON meanwhile is easy and we do it all the time, don't need any client, just give us request/response spec and any docs.

Posted by whatevaa on Dec 2, 2025, 12:13 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments

pricing (Other)

I can use text based API's (like with JSON) with nothing else but text editor and curl.

whatevaaDec 2, 2025, 12:13 PM

I can use text based API's (like with JSON) with nothing else but text editor and curl. No other tooling actually required. Meanwhile if binary protocol tooling in your stack sucks, then it just sucks. Had the joy of implementing calling SOAP service with client generated from wsdl in .net core 2/3 times. Tooling was shit poorly undocumented amd with crappy errors at that time. Run only with very specific versions in very specific way. And not much you can do about it, rolling your own SOAP client would be too expensive for our team. REST with JSON meanwhile is easy and we do it all the time, don't need any client, just give us request/response spec and any docs.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue