1. 28
  1. 9

    For those who believe that past decisions are an indicator for future decision making quality, this response to the issue …

    Chrome is not interested in this. The XML parts of our pipeline are in maintenance mode and we would love to eventually deprecate and remove them, or at least replace them with something that generates less security bugs. Increasing the capabilities of XML in the browser runs counter to that goal.

    … was written by the person of fantasy-land promises and Array.includes fame.

    1. 3

      What’s wrong with Array#includes?

      1. 2

        I found the Array.includes proposal: https://github.com/tc39/Array.prototype.includes/

        I’m curious what the fantasy-land promises referred to are!

        1. 2

          “Fantasy-land promises” must be https://github.com/fantasyland/fantasy-promises, though I don’t know why they’re notable.

          1. 3

            They are probably referring to the origin of Fantasy land. It started as a response to this response iirc https://github.com/promises-aplus/promises-spec/issues/94#issuecomment-16176966

            1. 3

              The last few replies are great for people who don’t want to read the whole thread: https://github.com/promises-aplus/promises-spec/issues/94#issuecomment-415222385

              The things done wrong here are fundamental to programming/computation itself, so there will never be a time when it is not wrong. And probably never be a time when it doesn’t adversely effect programming in Javascript/Typescript.

      2. 2

        It’s alive and well among those who are trying to extract useful information from html pages. After all, you can’t parse html with regex.

        1. 2

          I always just kind of felt like it was done. Complete. Nothing left to take away and little left to add. I used it almost daily for about eight years starting in 2009 in a proprietary product that relied very heavily on xml, xslt, and XPath. I will admit, though, that the things that were missing that I kind of wanted we ended up adding in the form of xslt extensions. So, I may be looking back through rose-colored glasses.

          1. 2

            I haven’t used XPath in several years, to the point where I tried to use it a few years ago with xmlstarlet and discovered I had forgotten all about it, but I recall from my years in the enterprise and semantic web world it being the one XML technology that basically just worked without any problems.

            1. 1

              Can you share what some of those missing things were?

              1. 2

                I had a version of this documentation open in a browser window or tab almost continuously for at least five of those years

                https://www.ibm.com/support/knowledgecenter/SS8NLW_11.0.0/com.ibm.swg.im.infosphere.dataexpl.engine.doc/c_xml-xsl-viv-extensions.html

                Things I can easily remember are some conditionals like simple if-else and switches, easy string concatenation and some other string operations, and tokenization including iteration (if we needed to do something an arbitrary number of times, we would have to create a string with N spaces and then iterate on tokens within that string).

                We had to do some calisthenics sometimes to get the job done but this stuff formed the foundation of a 100 million dollar product so it wasn’t complete garbage!