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.
>>107597302What alternative to Chromium-based browsers is actually good?
>client side renderingSo... normal rendering? Webshitters I swear.
>>107597302>this technology is 26 years old>the library to process it wasn't updated for the last 6 months>therefore we're removing it :)Literal mental illness. God forbid not having commits every day in a library that should have been finished decades ago and has absolutely no reason to get updates because, unlike everything else, it actually works, what's that, a feature-complete program??? time to delete it!!!
>>107599533XSLT was used in a lot of legacy enterprise apps. If your goal is to replace bespoke enterprise tools with half-baked Google trannyware, then advocating for this makes sense.
>>107600403not familiar with XSLT myself probably ran into it long time ago but havent seen it recently enough to remember, what is most likely certain though as with lot of these "legacy" software that it probably rendered very quickly and had a snappy interface compared to this javascript framework-on-framework-on-framework bloat retardation where we have multi-GHZ pcs with dozen cores yet they still need to ramp up to turbo to render a webpage because the javascript bloat is so resource intensive
>>107597411Tell people how to use an RSS feed right on the RSS feed URLThat’s like 95% of it
>>107600583Well then, Google wants to kill RSS feeds too because they can't monetize them so every little thing they can do to make them worse probably sounds like a great idea to them.
>>107599455t. autist who can't interpret words
>>107597302I remember this, it's basically stylesheets for XML files. Not really useful except maybe for styling your rss feeds, but rss is getting phased out heavily because it can be accessed without logging in to your account on a site. So there's not really any use of it whatsoever, and the only reason I know of it was because they taught it in a web class I once went to 20 years ago.