- From: Ihe Onwuka <ihe.onwuka@g...>
- To: Nicholas <saunders.nicholas@g...>, xml-dev <xml-dev@l...>
- Date: Fri, 30 Jul 2021 06:32:51 -0400
Yes but that's rather the point. If you ignore the ways in which the formats are not equivalent (like the specific one mentioned in my post) that lunch is going to either make you throw up or cause you indigestion.
Talk is cheap and experience can be a very bitter teacher.
On 2021-07-19 6:29 a.m., Ihe Onwuka
wrote:
..
Somebody comes along and wants to remodel this in JSON and
the reason when you've cut through all the is that bullshit
JSON has eaten XML's lunch and if you disagree that it would
be bullshit let's just agree that it's not going to be because
you can do the subtyping in the data model you originally
designed in JSON.
So my attitude is let them make that argument and if they
win the contract let them go build the system.
..
Yes, but that's rather the point: JSON has eaten the lunch of
XML. That's a legitimate reason to remodel in JSON: usability.
-Nick
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
|
Cart
