#xslt — Public Fediverse posts

RE: https://w3c.social/@koalie/116642001148113996

Le W3C entérine l'enterrement du XSLT en le justifiant obsolète mais relève, tout de même, dès fois que sait-on jamais, qu'il a été très utile.
On te fait rêver avec des super-ouvriers qui vont programmer pour toi, et dans le même temps on fait disparaître des super-outils qui t'ont permis de bâtir ce que tu voulais. Pas grave, la rétro-compatibilité du Web, c'est pas grand chose. Mais évidemment, pour ce faire, on allait quand même pas s'attaquer d'emblée à PHP ou CSS.

#xml #xslt #podcast #rss

RE: https://w3c.social/@koalie/116642001148113996

Le W3C entérine l'enterrement du XSLT en le justifiant obsolète mais relève, tout de même, dès fois que sait-on jamais, qu'il a été très utile.
On te fait rêver avec des super-ouvriers qui vont programmer pour toi, et dans le même temps on fait disparaître des super-outils qui t'ont permis de bâtir ce que tu voulais. Pas grave, la rétro-compatibilité du Web, c'est pas grand chose. Mais évidemment, pour ce faire, on allait quand même pas s'attaquer d'emblée à PHP ou CSS.

#xml #xslt #podcast #rss

RE: https://w3c.social/@koalie/116642001148113996

Le W3C entérine l'enterrement du XSLT en le justifiant obsolète mais relève, tout de même, dès fois que sait-on jamais, qu'il a été très utile.
On te fait rêver avec des super-ouvriers qui vont programmer pour toi, et dans le même temps on fait disparaître des super-outils qui t'ont permis de bâtir ce que tu voulais. Pas grave, la rétro-compatibilité du Web, c'est pas grand chose. Mais évidemment, pour ce faire, on allait quand même pas s'attaquer d'emblée à PHP ou CSS.

#xml #xslt #podcast #rss

RE: https://w3c.social/@koalie/116642001148113996

Le W3C entérine l'enterrement du XSLT en le justifiant obsolète mais relève, tout de même, dès fois que sait-on jamais, qu'il a été très utile.
On te fait rêver avec des super-ouvriers qui vont programmer pour toi, et dans le même temps on fait disparaître des super-outils qui t'ont permis de bâtir ce que tu voulais. Pas grave, la rétro-compatibilité du Web, c'est pas grand chose. Mais évidemment, pour ce faire, on allait quand même pas s'attaquer d'emblée à PHP ou CSS.

#xml #xslt #podcast #rss

RE: https://w3c.social/@koalie/116642001148113996

Le W3C entérine l'enterrement du XSLT en le justifiant obsolète mais relève, tout de même, dès fois que sait-on jamais, qu'il a été très utile.
On te fait rêver avec des super-ouvriers qui vont programmer pour toi, et dans le même temps on fait disparaître des super-outils qui t'ont permis de bâtir ce que tu voulais. Pas grave, la rétro-compatibilité du Web, c'est pas grand chose. Mais évidemment, pour ce faire, on allait quand même pas s'attaquer d'emblée à PHP ou CSS.

#xml #xslt #podcast #rss

Although we moved on from using #xslt a few years ago, this will mark the end of how we used to generate a lot of the #w3c website.

https://status.w3.org/incidents/n0g4kghms0mn

Although we moved on from using #xslt a few years ago, this will mark the end of how we used to generate a lot of the #w3c website.

https://status.w3.org/incidents/n0g4kghms0mn

Although we moved on from using #xslt a few years ago, this will mark the end of how we used to generate a lot of the #w3c website.

https://status.w3.org/incidents/n0g4kghms0mn

Although we moved on from using #xslt a few years ago, this will mark the end of how we used to generate a lot of the #w3c website.

https://status.w3.org/incidents/n0g4kghms0mn

Although we moved on from using #xslt a few years ago, this will mark the end of how we used to generate a lot of the #w3c website.

https://status.w3.org/incidents/n0g4kghms0mn

Whoops, looks like #Mozilla #Firefox users will loss the accurately formatted (by #XSLT) #RSS feed page, after pressing to "RSS" link in my blog :drgn_blush_giggle:

Sincelery, I don't know what to advise… Looks like the various "old Firefox with XUL" forks (like Pale Moon) aren't just for nostalgia, but for everyday use in the nearby future.

Whoops, looks like #Mozilla #Firefox users will loss the accurately formatted (by #XSLT) #RSS feed page, after pressing to "RSS" link in my blog :drgn_blush_giggle:

Sincelery, I don't know what to advise… Looks like the various "old Firefox with XUL" forks (like Pale Moon) aren't just for nostalgia, but for everyday use in the nearby future.

Whoops, looks like #Mozilla #Firefox users will loss the accurately formatted (by #XSLT) #RSS feed page, after pressing to "RSS" link in my blog :drgn_blush_giggle:

Sincelery, I don't know what to advise… Looks like the various "old Firefox with XUL" forks (like Pale Moon) aren't just for nostalgia, but for everyday use in the nearby future.

Whoops, looks like #Mozilla #Firefox users will loss the accurately formatted (by #XSLT) #RSS feed page, after pressing to "RSS" link in my blog :drgn_blush_giggle:

Sincelery, I don't know what to advise… Looks like the various "old Firefox with XUL" forks (like Pale Moon) aren't just for nostalgia, but for everyday use in the nearby future.

Whoops, looks like #Mozilla #Firefox users will loss the accurately formatted (by #XSLT) #RSS feed page, after pressing to "RSS" link in my blog :drgn_blush_giggle:

Sincelery, I don't know what to advise… Looks like the various "old Firefox with XUL" forks (like Pale Moon) aren't just for nostalgia, but for everyday use in the nearby future.

ROTFL

#Rust core team listens to Rust developers like the #GAFAM-controlled #WHATWG listens to web developers

#LLM #XSLT #genAI

ROTFL

#Rust core team listens to Rust developers like the #GAFAM-controlled #WHATWG listens to web developers

#LLM #XSLT #genAI

ROTFL

#Rust core team listens to Rust developers like the #GAFAM-controlled #WHATWG listens to web developers

#LLM #XSLT #genAI

ROTFL

#Rust core team listens to Rust developers like the #GAFAM-controlled #WHATWG listens to web developers

#LLM #XSLT #genAI

ROTFL

#Rust core team listens to Rust developers like the #GAFAM-controlled #WHATWG listens to web developers

#LLM #XSLT #genAI

I've opened a whole new can of worms: #XSLT. Specifically XSLT 2.0. It seems all #FOSS XSLT transformers are either proprietary or written in #Java :( Any tips for a Python or JS-based approach?

I've opened a whole new can of worms: #XSLT. Specifically XSLT 2.0. It seems all #FOSS XSLT transformers are either proprietary or written in #Java :( Any tips for a Python or JS-based approach?

I've opened a whole new can of worms: #XSLT. Specifically XSLT 2.0. It seems all #FOSS XSLT transformers are either proprietary or written in #Java :( Any tips for a Python or JS-based approach?

I've opened a whole new can of worms: #XSLT. Specifically XSLT 2.0. It seems all #FOSS XSLT transformers are either proprietary or written in #Java :( Any tips for a Python or JS-based approach?

I've opened a whole new can of worms: #XSLT. Specifically XSLT 2.0. It seems all #FOSS XSLT transformers are either proprietary or written in #Java :( Any tips for a Python or JS-based approach?

Martin 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

Martin 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

Martin 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

Martin 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

Martin 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

Giving up on having nice RSS rendering via XSLT since not only Chrome but also Firefox are removing support for XSL soon. Sad. #xslt #firefox

Giving up on having nice RSS rendering via XSLT since not only Chrome but also Firefox are removing support for XSL soon. Sad. #xslt #firefox

Giving up on having nice RSS rendering via XSLT since not only Chrome but also Firefox are removing support for XSL soon. Sad. #xslt #firefox

Giving up on having nice RSS rendering via XSLT since not only Chrome but also Firefox are removing support for XSL soon. Sad. #xslt #firefox

Giving up on having nice RSS rendering via XSLT since not only Chrome but also Firefox are removing support for XSL soon. Sad. #xslt #firefox

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.