Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
@metamourge in my whatever long carreer never once i have seen yaml being used unironically
-
devTea240945y@Alice I’ve read once that people still uses XML because of some pros cons compared to JSON, but I forgot
-
C0D4681975y@devTea WSDL validation is handy, at least the api can't lie ๐
But yea I'll take json anyday. -
C0D4681975y@devTea I sill use soap ๐งผ... but only because I work with dinosaur companies that I realllllly don't trust with a REST api. They hardly keep their systems working as it is.
-
devTea240945y@C0D4 I’ve seen XML format on JSON string and then parse it back, can you beat that?
-
C0D4681975y@devTea... jsonp inside xml would have to be near the top of my list, With some of the key data being XML node attributes.
Something like this:
<credentials user="x" pass="y">
<callback>callback("{'key':1,'key':2}")</callback>
</credentials>
I sometimes regret my life choices. -
pesar1095yI wish I could edit my rant and instead of:
XML
put:
Blah Blah config file format. This could prevent the Config File War above! -
inaba46315yWhere the factory that gets the function dependency injected and then calls it through a method that takes the exact same parameters??
-
haze2715yI'll have to use SOAP as well soon. :') Disgusting stuff.
But there are Python libraries that can easily handle them.
I'll just need to write *simple* scripts to integrate two completely different tools client uses... Fck. -
Trithon10305yI'm just RESTing my hand on my forehead (forcefully)
I showed this to my friend JSON and he did the same thing -
You want to call a function? STOP!!!
Nowadays it is so amateur and old fashioned! Instead you must:
- Make a soap request
- Write a router to handle soup requests
- Write an XML to define which controller responds to this request
- Write an XML parser on top of another XML parser
- Write a controller to trigger an event in response to the request
- Write an XML which defines the event
- Write an XML that defines the event observer
- Write a plugin which calls event observers
- Write a router which delegates the task of calling event observers to that plugin
- Write an event observer which calls another plugin
- Write a plugin that "Calls a function".
It's better because... it's more Object Oriented!
rant