Hacker News
points by ergonaught 3 days ago | 0 comments
We used XSLT for literally every UI, for generating C++ for certain types of classes, and for generating SQL for very large reporting systems, etc. It was used in damned near everything.

Bummer, I guess.

[–] genxy 3 days ago
I am sure someone is working on a polyfill using wasm. This won't unbreak the rest of the web, but it will still allow for a clean separation of concerns.

I know "chrome is their browser" but Google has no business unilaterally decided what the fucking web runs now. They are just a big fucking adriddled bully.

[–] youngtaff 3 days ago
It’s not just Google… Apple and Mozilla want to kill it off in browsers too

Fundamental issue is the library is maintained by one person (from memory) and no-one at the big corps wants to step up

[–] xp84 3 days ago
Did any of that stuff happen in the browser, though?

I never learned the first thing about it, other than its name, so I'll admit ignorance.

[–] ergonaught 3 days ago
For the UI, yes. It gave us (and our customers) a great deal of flexibility.

I can only assume we would go in a different direction, today, even if XSLT weren't "dying", but it really did fit our use case really well.