Oblomov
Moritz
Sasha FirsovIf you have even weirdest wishes within structural data life cycle, please share.
Multi- content type parser design is almost there. Polishing some ambiguities before finalizing. Will cover whole XML stack, JSON, web stack and rust. Streaming all the way, multithreading, resource control, binary data, compression, data broadcast in addition to TCP...
30 pages of feature items so far. βοΈ as usual.
https://github.com/EPA-WG/cem/blob/develop/docs/cem-ml-stack-design.md
Emmanuel Chateau-DutierMartin Honnen sur Twitter "The XSLT 3 development branch of Apache Xalan has made great progress, I can now run lots of examples written for Saxon unchanged with Xalan, therefore I have created an entry page for my CheerpJ powered, Xalan XSLT 3.0 fiddle that shows some samples" #xslt https://martin-honnen.github.io/cheerpj3-xalan-xslt3/index-examples.html
Jorge SanzGiving up on having nice RSS rendering via XSLT since not only Chrome but also Firefox are removing support for XSL soon. Sad. #xslt #firefox
Marcus Rohrmoser π»Dear @timbl,
I kindly ask you to consider talking to the people at #Mozilla to keep #xml documents with human-friendly rendering via #xslt visible in #Firefox.
Not only needs the web decentralisation, but also raw, machine-readable data in human-friendly appearance. #Feeds, #RDF, etc. Dropping #w3c standards and backwards-compatibiity in this regard makes the web an unreliable medium for long-term publishing and archiving of such documents, even more so for small entities with limited resources. Big players have no problem continuously overhauling their archives to meet the viewers' habits du-jour and adapt to fast-moving, volatile practices.
Please say no to this #enshittification.
Yours,
@mro
P.S.: I pledge a monthly Euro to such a browser.
Hi @drscriptt @jon,
#Firefox #XSLT being on death row. Look into it's console e.g. browsing https://seppo.mro.name/aseppototry/. I mentioned that, didn't I? #Curfew May 1st AFAIK.
#Safari isn't an option here on #FreeBSD / #Linux and prbly will do likewise anyway.
#Firefox #XSLT being on death row. Look into it's console e.g. browsing https://seppo.mro.name/aseppototry/. I mentioned that, didn't I? #Curfew May 1st AFAIK.
#Safari isn't an option here on #FreeBSD / #Linux and prbly will do likewise anyway.
Hi @jon,
#JS being more powerful is the case against it.
The other is the irresponsibility to just drop features at will. #XSLT was a #w3c standard. If that's not a thing to rely on and publish documents for long-term availability, then there isn't such a thing. Fits with TLS and short lived certs.
That's all toward card houses. And I hate any of it.
It's not about XSLT, it's about #reliability.
thinkbergI donβt know who knows this apart from the experts, but #XSLT is a beautiful #functional language. I like it because it is purely so.
β’Allein #SVG und #MathML sind relevante Browser-basierte #XML-Technologien. #RSS / #Atom existieren ebenfalls.
#XSLT lebt auf dem Server weiter und hat in Version 3.0 (bald 4.0) primΓ€r fΓΌr lokal angesiedelte Prozesse der Dokumentverarbeitung (#DITA, #DocBook, #TEI) eine ungebrochene Bedeutung. Zudem steht mit #SaxonJS eine Browser-Alternative zur VerfΓΌgung.
Pensionierte XMLer werden bestimmt ebenso gefragt sein wie im Fall von #COBOL.
