[–] [S] 2 points 9 months ago

while JSON is a generalized data structure with support for various data types supported by programming languages

Honestly, I find it surprising that you say “support for various data types supported by programming languages”. Data types are particularly weak in JSON when you go beyond JavaScript. Only number for numbers, no integer types, no date, no time, etc.

Regarding use, I see, at least to some degree, JSON outside of use for network transfer. For example, used for configuration files.

  • source
  • parent
  • context
  • [–] [S] 1 point 9 months ago

    The point is that there are degrees to readability, specificity, and obviousness, even without a common understanding. Self-describing data, much like self-describing code, is different from a dense serialization without much support in that regard.

  • source
  • parent
  • context
  • [–] [S] 5 points 9 months ago* (1 child)

    Making XML schemas work was often a hassle. You have a schema ID, and sometimes you can open or load the schema through that URL. Other times, it serves only as an identifier and your tooling/IDE must support ID to local xsd file mappings that you configure.

    Every time it didn't immediately work, you'd think: Man, why don't they publish the schema under that public URL.

  • source
  • parent
  • context
  • [–] [S] 5 points 9 months ago (5 children)

    In XML the practice to approximate arrays is to put the index as an attribute. It’s incredibly gross.

    I don't think I've seen that much if ever.

    Typically, XML repeats tag names. Repeating keys are not possible in JSON, but are possible in XML.

    <items>
      <item></item>
      <item></item>
      <item></item>
    </items>
    
  • source
  • parent
  • context
  • [–] [S] 2 points 9 months ago

    It can be used as alternatives. In MSBuild you can use attributes and sub elements interchangeably. Which, if you're writing it, gives you a choice of preference. I typically prefer attributes for conciseness (vertical density), but switch to subelements once the length/number becomes a (significant) downside.

    Of course that's more of a human writing view. Your point about ambiguity in de-/serialization still stands at least until the interface defines expectation or behavior as a general mechanism one way or the other, or with specific schema.

  • source
  • parent
  • context
  • [–] [S] 5 points 9 months ago* (1 child)

    There was a time where HTML moved towards a more formalized XML-valid definition named XHTML. Ultimately, web/browser backwards compatibility and messy and forgiving nature lead to us giving up on that and now we have the HTML living standard with rules, but browsers (not sure to what degree it's standardized or not) are very forgiving in their interpretation.

    While HTML, prior to HTML5, was defined as an application of Standard Generalized Markup Language (SGML), a flexible markup language framework, XHTML is an application of XML, a more restrictive subset of SGML. XHTML documents are well-formed and may therefore be parsed using standard XML parsers, unlike HTML, which requires a lenient, HTML-specific parser.[1]

    XHTML 1.0 became a World Wide Web Consortium (W3C) recommendation on 26 January 2000. XHTML 1.1 became a W3C recommendation on 31 May 2001. XHTML is now referred to as "the XML syntax for HTML"[2][3] and being developed as an XML adaptation of the HTML living standard.[4][5]

  • source
  • parent
  • context
  • [–] [S] 6 points 9 months ago (3 children)

    Most use cases don’t need fully sematic data storage

    If both sides have a shared data model it's a good base model without further needs. Anything else quickly becomes complicated because of the dynamic nature of JSON - at least if you want a robust or well-documented solution.

  • source
  • parent
  • context
  • [–] 4 points 9 months ago

    It’s possible for users to store those keys on a device they own, but Microsoft also recommends BitLocker users store their keys on its servers for convenience.

    Pretty obvious that if you hand over the (recovery) keys that they'd follow court orders.

    Of course, the criticism about defaults is warranted. At the same time, even outside of control concerns, it's fairly obvious why Microsoft would choose user convenience and ability to recover data over loss of data.

    It should be a well informed choice that makes the risks clear when setting it up.

  • source
  • view more: ‹ prev next ›