10

So......... there's this company who HATE to return data in json, yml or xml. Their "RESTFul api" returns .ini file as string and all requests are 200 ! even though it is failed , still return 200.

And the structure are inconsistent af.

The PIC literally solve every issue by store data in .ini file locally

LocalStorage? .ini
SharedPreferences? .ini
Api response type ? .ini
Caching? .ini
UI key=value handling? .ini

hotel? trivago.

Comments
  • 3
    I like ini but only for… well initialization data which is not hierarchical.

    Encoding everything in ini is insane.
  • 3
    Hmm... failed 200 returns 200? Creator of that one must've been a fan: https://commitstrip.com/en/2018/... .
  • 5
    Quietly retched a bit reading that.

    Delphi?
  • 6
    I was going to ask if they are stuck in the past... Yes, they are. Delphi. lol
  • 2
    I hate 200-always APIs. Fuck that.

    However, some encodings are just better than JSON. For example, JSON excels in tree-like structures, but is inefficient in tabular data. CSV is one of the best human-readable formats for 80% of data out there, which still fits into a flat, tabular model.
  • 1
    @AlgoRythm I agree that csv is sometimes better but 80%?
    No way. In my experience it‘s like 5%.
Add Comment