Salta al contenuto
0
  • Categorie
  • Recenti
  • Tag
  • Popolare
  • Mondo
  • Utenti
  • Gruppi
  • Categorie
  • Recenti
  • Tag
  • Popolare
  • Mondo
  • Utenti
  • Gruppi
Collassa

Forum Federato

Di Piero Bosio
  1. Home
  2. Categorie
  3. Senza categoria
  4. I created a repo @Codeberg for my really simple #XSL-weblog:

I created a repo @Codeberg for my really simple #XSL-weblog:

Pianificato Fissato Bloccato Spostato Senza categoria
xslxsltrss
7 Post 3 Autori 2 Visualizzazioni
  • Da Vecchi a Nuovi
  • Da Nuovi a Vecchi
  • Più Voti
Rispondi
  • Topic risposta
Effettua l'accesso per rispondere
Questa discussione è stata eliminata. Solo gli utenti con diritti di gestione possono vederla.
  • Stephenundefined Questo utente è esterno a questo forum
    Stephenundefined Questo utente è esterno a questo forum
    Stephen
    scritto su ultima modifica di
    #1

    I created a repo @Codeberg for my really simple #XSL-weblog:
    https://codeberg.org/harlows/xsl-weblog

    It's part of my tiny attempt to preserve #XSLT and very much a work-in-progress. Thus far it's really just a repackaging of Evan Widloski's example:
    https://github.com/Evidlo/xsl-website

    You can see it evolve here:
    https://blog.harlow.net.nz/
    or follow the #RSS feed:
    https://blog.harlow.net.nz/feed.xml
    Transformed by the magic of #XSLT!

    Worikundefined 1 Risposta Ultima Risposta
    1
    • Stephenundefined Stephen

      I created a repo @Codeberg for my really simple #XSL-weblog:
      https://codeberg.org/harlows/xsl-weblog

      It's part of my tiny attempt to preserve #XSLT and very much a work-in-progress. Thus far it's really just a repackaging of Evan Widloski's example:
      https://github.com/Evidlo/xsl-website

      You can see it evolve here:
      https://blog.harlow.net.nz/
      or follow the #RSS feed:
      https://blog.harlow.net.nz/feed.xml
      Transformed by the magic of #XSLT!

      Worikundefined Questo utente è esterno a questo forum
      Worikundefined Questo utente è esterno a questo forum
      Worik
      scritto su ultima modifica di
      #2

      @stephenharlow @Codeberg I am interested in this debate

      I worked quite extensively with XML in the day. I am not a fan, now, after loving it when I first learnt about it then using it

      A good idea to a Computist, but in practice really hard to work with. Much harder than you'd expect, hearing about it

      Is there anything worth saving in XML technologies? Can we do better?

      Stephenundefined Oblomovundefined 2 Risposte Ultima Risposta
      • Worikundefined Worik

        @stephenharlow @Codeberg I am interested in this debate

        I worked quite extensively with XML in the day. I am not a fan, now, after loving it when I first learnt about it then using it

        A good idea to a Computist, but in practice really hard to work with. Much harder than you'd expect, hearing about it

        Is there anything worth saving in XML technologies? Can we do better?

        Stephenundefined Questo utente è esterno a questo forum
        Stephenundefined Questo utente è esterno a questo forum
        Stephen
        scritto su ultima modifica di
        #3

        @worik I think #RSS is worth saving. My motivation is keeping the web open (and learning something new in the process). What @oblomov said: https://wok.oblomov.eu/tecnologia/google-killing-open-web/

        1 Risposta Ultima Risposta
        1
        • Oblomovundefined Oblomov ha condiviso questa discussione
        • Worikundefined Worik

          @stephenharlow @Codeberg I am interested in this debate

          I worked quite extensively with XML in the day. I am not a fan, now, after loving it when I first learnt about it then using it

          A good idea to a Computist, but in practice really hard to work with. Much harder than you'd expect, hearing about it

          Is there anything worth saving in XML technologies? Can we do better?

          Oblomovundefined Questo utente è esterno a questo forum
          Oblomovundefined Questo utente è esterno a questo forum
          Oblomov
          scritto su ultima modifica di
          #4

          @worik @stephenharlow @Codeberg

          my reaction has long been the opposite. I used to hate XML and how it was being forcefully thrown everywhere regardless of whether it made sense or not. These days, I realize what a powerful, unifying language it was, and what a pity it has been that an overreaction lead to it being disregarded even when it made sense. And even if I see why in environments like e.g. the web one would want to be more tolerant of faults, the underlying principles remain valid.

          Oblomovundefined 1 Risposta Ultima Risposta
          • Oblomovundefined Oblomov

            @worik @stephenharlow @Codeberg

            my reaction has long been the opposite. I used to hate XML and how it was being forcefully thrown everywhere regardless of whether it made sense or not. These days, I realize what a powerful, unifying language it was, and what a pity it has been that an overreaction lead to it being disregarded even when it made sense. And even if I see why in environments like e.g. the web one would want to be more tolerant of faults, the underlying principles remain valid.

            Oblomovundefined Questo utente è esterno a questo forum
            Oblomovundefined Questo utente è esterno a questo forum
            Oblomov
            scritto su ultima modifica di
            #5

            @worik @stephenharlow @Codeberg

            the main reason why it remains a language difficult to work with is that the tooling around it has remained substantially underdeveloped (e.g. there's very few good XML editors, and parsers and processors have maintained a largely passive approach to error reporting —compare e.g. how much more C++ error reporting has evolved), despite the language itself allowing much more featurefull editing and processing possibilities.

            Worikundefined 1 Risposta Ultima Risposta
            • Oblomovundefined Oblomov

              @worik @stephenharlow @Codeberg

              the main reason why it remains a language difficult to work with is that the tooling around it has remained substantially underdeveloped (e.g. there's very few good XML editors, and parsers and processors have maintained a largely passive approach to error reporting —compare e.g. how much more C++ error reporting has evolved), despite the language itself allowing much more featurefull editing and processing possibilities.

              Worikundefined Questo utente è esterno a questo forum
              Worikundefined Questo utente è esterno a questo forum
              Worik
              scritto su ultima modifica di
              #6

              @oblomov @stephenharlow @Codeberg

              The difficulty I have with it is editing a file by hand. There is too much mark up

              I am not a specialist but I have seen ppl who know more than me talk of ratios of markup to content. XML is hard by that measure

              Attributes are an utter pita.

              I was using JSON , which is easier, but I am back to trying to do line orientated CSV, but it is not always suitable

              Oblomovundefined 1 Risposta Ultima Risposta
              • Worikundefined Worik

                @oblomov @stephenharlow @Codeberg

                The difficulty I have with it is editing a file by hand. There is too much mark up

                I am not a specialist but I have seen ppl who know more than me talk of ratios of markup to content. XML is hard by that measure

                Attributes are an utter pita.

                I was using JSON , which is easier, but I am back to trying to do line orientated CSV, but it is not always suitable

                Oblomovundefined Questo utente è esterno a questo forum
                Oblomovundefined Questo utente è esterno a questo forum
                Oblomov
                scritto su ultima modifica di
                #7

                @worik @stephenharlow @Codeberg

                the file format of choice should depend on the task at hand. CSV is good if your data is plain tables, JSON works better for simple structured data, and XML for tagged structured data (that's what the attributes are for).

                And yes, XML is very verbose, so you do need a good editor to work with it comfortably.

                1 Risposta Ultima Risposta
                Rispondi
                • Topic risposta
                Effettua l'accesso per rispondere
                • Da Vecchi a Nuovi
                • Da Nuovi a Vecchi
                • Più Voti


                • Accedi

                • Accedi o registrati per effettuare la ricerca.
                • Primo post
                  Ultimo post