But python isn’t the webs scripting engine. If it was, browsers would have support for python3 and 2.
Comment on Just started a community for those who wish to move away from Lemmy
Draconic_NEO@lemmy.world 1 week agoYes 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.
irelephant@lemmy.dbzer0.com 1 week ago
Draconic_NEO@lemmy.world 2 days ago
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”.
irelephant@lemmy.dbzer0.com 2 days ago
I mean, looking at what python3 broke, they are some changes that were well needed. 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.
db0@lemmy.dbzer0.com 1 week ago
Again, python 2 still exists. nothing would be “trashed”. If you want backwards compatibility just keep using python2. We clearly don’t see things the same way, but given that python is the most popular languge in the world, I’m happy most see it my way.