this post was submitted on 17 Dec 2024
35 points (100.0% liked)
Hacker News
323 readers
251 users here now
RSS Feed of HackerNews
founded 3 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
SOAP services are a thing of the past, but I still remember how easy it was to put the WSDL URL is Visual Studio and poof you'd have a full SDK complete with a service facade and data models. So nice and easy. (Which appears to be similar to what this guy was trying to build and sell)
When REST started getting popular, I was like: "WTF, we have to code all this now by hand again!?"
Don't know about .NET, but in Java my experience with SOAP has been abysmal. I'd much rather write a client by hand using a nice REST lib than go through this bullshit again.
EDIT: it's worth mentioning Java has been my primary language for most of my career and I don't hate it.
I could go all day, but in brief, I (jokingly) blame you guys (non-Microsoft developers) for enshitifying Microsoft's toolset.
Microsoft's approach for years was to build designers and GUIs into Visual Studio to make coding super easy. Everything was integrated. The developer experience was glorious.
Then, all the developers like you suffering with shit like NetBeans, Eclipse, Apache, and TortoiseSVN decided they'd had enough and started romanticizing one-off command line tools, goofy data structures like yaml, and git. That made everything too hard, so you built code generators, transpilers, and job runners to automate things. That led to so much complexity, you needed virtual containers to run it in so setup wouldn't be a nightmare. Then, the containers got out of control so you needed something to manage THAT.
Microsoft could have laughed and let us live in our developer utopia, but noooooo. They felt compelled to play along. And now anything new coming from MS is built to support all that crap we never needed in the first place.
We had it so good. Sigh.