#dev 2024-10-07
2024-10-07 UTC
barnaby, Dryusdan, [morganm], Guest6, baracurda, ttybitnik, jacky_ and [schmarty] joined the channel
AramZS and baracurda_ joined the channel
#
[0x3b0b] I think I've only ever used XSLT for two things. One of them I don't remember, and the other was for a subset of conversion of WDDX to JSON because I was dealing with a server on which I didn't have sufficient influence to get someone to install whatever it was PHP needed in order to deliver JSON pretty-printed.
claudinec and [Joe_Crawford] joined the channel
#
[Joe_Crawford] XSLT is never going to be "awesome" but if you are obliged to speak XML it's pretty great. MP3 dot com had what was essentially a static site generator that used XML files for storage in its early days.
#
[Joe_Crawford] Structured storage for hundreds of thousands of songs, artists, albums, etc and used XSLT in Perl (I want to say Perl::mason) rather than having to buy licenses the only performant database anyone wouldn't sniff at - Oracle.
#
[Joe_Crawford] And when forced to interact with XML based APIs it can be a nice way to tease out whatcha want.
#
[Joe_Crawford] But in 2024 would I *choose* to do things in XSLT? No.
AramZS and bret joined the channel
#
[tantek] alright, I'm thinking today I start drafting a bunch of updates to rel-author, in case folks have thoughts, outstanding issues etc. obviously this touches on many aspects like /authorship, and in particular I want to specify precise enough functionality to bridge HTML post permalinks (regardless of platform/software) and both HTML author pages and JSON AS2 profiles (that presumably have AP inboxes).
#
[tantek] for reference, spec: https://microformats.org/wiki/rel-author
#
[tantek] and examples, how to use: https://indieweb.org/rel-author
lanodan, [shadow] and troojg joined the channel
