Recently joined and started a community for people who want to move away from Lemmy and want to see Lemmy loosen its stranglehold on the threadiverse, if that seems like something interesting to you consider checking out !cancel_lemmy@piefed.social
Recently joined and started a community for people who want to move away from Lemmy and want to see Lemmy loosen its stranglehold on the threadiverse, if that seems like something interesting to you consider checking out !cancel_lemmy@piefed.social
Yes I don’t think that demolishing whole ecosystems is a good thing. I think that it’s a shitty mentality of wanting shiny and new shit and fixing what isn’t broken. I am a believer in legacy support and I find it weird and concerning to see and hear people complain about it. You do realize that if Python had been the Web’s scripting engine instead of JS, a lot of Websites would’ve been, and still would be trashed and unusable due to said breaking changes with zero regard for legacy support. Thankfully that wasn’t the case, but it does go to show that legacy support and backwards compatibility is important.
But python isn’t the webs scripting engine. If it was, browsers would have support for python3 and 2.
I mean, maybe? I don’t know, I don’t live in that mirror universe where python supplanted JS. Though considering how hard the push was to abandon and burn down python2, I have a feeling even if it was a web scripting language the same push would’ve happened and it would’ve just broken a lot more stuff since you know “sECuRiTY”.
I mean, looking at what python3 broke, they are some changes that were well needed. https://docs.python.org/release/3.0.1/whatsnew/3.0.html
I think it would be like xhtml, which broke compatibility with old versions of html, but was (and still is) supported by browsers.