I created a repo @Codeberg for my really simple #XSL-weblog:
-
I created a repo @Codeberg for my really simple #XSL-weblog:
https://codeberg.org/harlows/xsl-weblogIt'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-websiteYou 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! -
I created a repo @Codeberg for my really simple #XSL-weblog:
https://codeberg.org/harlows/xsl-weblogIt'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-websiteYou 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!@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?
-
@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?
@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/
-
undefined Oblomov ha condiviso questa discussione
-
@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?
@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.
-
@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.
@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.
-
@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.
@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
-
@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
@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.