Apparently Google is removing XSLT support from Chrome. Fuck Jewgle and fuck the retards behind their shit browser for killing the only native client side rendering "framework".https://chromestatus.com/feature/4709671889534976
Chrome is the browser for people who used Internet Explorer until Chrome came out. You get the browser you deserve.
>>107597302Literally never heard of this. Sounds like bloat that only affects cuntpanies still living in 2000-5 desu fampai
>>107597302use case for XSLT?
>>107597411Client side rendering without Javascript. I learnt it it about 18 years ago.https://www.w3schools.com/xml/xsl_intro.asp
>>107597459>without javascriptbecause it's about ten times worse than javascript. which is a low bar in the first place.
>>107597302Don't really care for this particular technology but still smell the neovagina rotting on the other side of screen when terms "complex, aging C codebase" and "memory safety" was being brought upIf it was Written In Rust™ the trannies would be pushing XSLT as the best technology to ever exist with no faults whatsoever
>>107597527No. We're in the age of "security scanner" software that chugs through codebases and flags zillions of potential security issues. (he overwhelming majority of them tend to be "well, this code is complex and is hard to maintain). Mangers love this shit.You can bet that whatever they're using has been bitching up a storm about this lib and they've just decided to pitch it.
