Live data from Hacker News

Letters about Soap (1997)

people.cs.ksu.edu

41–50 of 74 posts

Re: Letters about Soap (1997)

#42
post #9

Part of me thinks this was faked/exaggerated at the time, except... Once on Amazon, I ordered an open tent. Basically, it is just an aluminum frame, 12 feet×12, 8 feet high, with canvas, to keep the sun off when presenting things at outdoor events. The one I received took 5 weeks to arrive, and was supposed to be new. But it was used, with scruff marks on the posts. I sent pics, and said "Hey, this is supposed to be…

When the Sorcerer's Apprentice works on Customer Support.

Re: Letters about Soap (1997)

#43
post #4
post #3

Why do I feel the urge to find this guy's address and arrange for an industrial crate of tiny soap bars delivered to him?

But they have to be in stacks no more than 4 high due to their tendency to tip over, so it might be more than one crate required.

If you create enough stacks around each other, that stops being a problem.

Re: Letters about Soap (1997)

#44
post #41

Ha, I expected it to be about SOAP the protocol https://en.wikipedia.org/wiki/SOAP but this seems to be more interesting. I suppose if you have a Galactic Empire sized business, maybe something like SOAP (or EDI) to really nail things down makes some sense. Otherwise I'm not so sure.

Not a year goes by where I’m not convinced that things would be easier if as a community we used a modern version of the soap protocol, maybe with JSON instead of XML. RPC is such a clean design compared to REST, and it we had auto-generated client code 15 years ago, something the likes of swagger are still catching up with.

Re: Letters about Soap (1997)

#45
post #10

reminds me of a lot of "support" these days: figure out which script contains words which sound like the problem being described, then follow it, without actually taking the time to understand the problem

Did anyone else click on the link expecting a rant about the soap protocol?

The S stands for Simple: http://harmful.cat-v.org/software/xml/soap/simple

Re: Letters about Soap (1997)

#46
post #10

Earlier quoted context omitted.

Did anyone else click on the link expecting a rant about the soap protocol?

I clicked on it expecting effusive praise of SOAP. Disappointed to find it's still only me, there must be tens of us who like it.

I have heard praise of SOAP once. It came from a Sun spokesperson, before the protocol had support on anything on the real world.

I have never heard praise of it again.

To tell you the truth, the autodiscovery part would be really awesome... if it worked. But instead, the thousands of pages long set of standards that create SOAP are not specific enough, so it doesn't work.

Re: Letters about Soap (1997)

#47
post #5
post #4

Earlier quoted context omitted.

But they have to be in stacks no more than 4 high due to their tendency to tip over, so it might be more than one crate required.

"Welcome to the Soap-of-the-Week Club! Every week we'll send you some tiny bars of soap in a little stack. You may not revoke your membership."

3.. 2.. 1..

Someone starts a subscription service for small bars of hotel style soap, perhaps themes of hotel, room type, region, season regional or other soap minutiae, shipped once a month.

Like Candy Japan, but for tiny bars of hotel soap.

Re: Letters about Soap (1997)

#48

This is an excellent addition to HN and I hope that devs and product managers alike see what happens when everyone tries to do as little as possible without taking the time to understand the bigger picture or even the underlying problem. This could have been solved so simply at any step of the journey.

Hiliariously, my PM brain that can never be at-rest was thinking about how this whole interaction could be improved. Hampered, of course, that this was dated in 1997–now hotels have magical things like in-room tablets.

Which means that this can now play out with tablets instead of bars of soap.

Re: Letters about Soap (1997)

#49
post #44
post #41

Ha, I expected it to be about SOAP the protocol https://en.wikipedia.org/wiki/SOAP but this seems to be more interesting. I suppose if you have a Galactic Empire sized business, maybe something like SOAP (or EDI) to really nail things down makes some sense. Otherwise I'm not so sure.

Not a year goes by where I’m not convinced that things would be easier if as a community we used a modern version of the soap protocol, maybe with JSON instead of XML. RPC is such a clean design compared to REST, and it we had auto-generated client code 15 years ago, something the likes of swagger are still catching up with.

Auto generated client code is nice in theory. In practice I find it only really useful as a starting point. There are enough choices to be made in writing even a simple HTTP api that its unlikely that a generic tool will generate useful code for a given application. This could include library usage (http client, serialization, logging, DI integration), async vs sync, logging requirements, tooling support for generated code. If you are in a language which has established std libraries and patterns this is less of a problem, but in something like Java that has evolved in all these areas over the years it can be a real problem.
Post reply on HN