News for hackers. Stuff that matters.
Re:WebAssembly becomes a W3C Recommendation by LessDmesg on Monday December 16, 2019 @12:41PM (#21805034)
For one thing, not being broken. Python doesn't have ("1"+1) and similar design flaws, Python doesn't need a new ECMAscript standard every year, Python has figured out modules and classes much earlier, and frankly, Python is what Javascript is only becoming after years of improvement. Really, I don't understand why we and the browser maintainers have to put up with a broken, insane language when there is a similar but much more mature and "done right" one. And as far as ecosystem, Python can kick Javascript's ass if not in quantity (though it's close) then in quality of its userbase for sure. And Python has been used onе the backend much more than JS, so it makes much more sense to unify the language and just use Python for the front-end.
Re:WebAssembly becomes a W3C Recommendation by strbean on Monday December 16, 2019 @11:59PM (#21810765)
I feel like almost every one of those points is highly debatable.

- New ECMA standard every year VS. new PEPs every year

- Modules and classes: cyclic dependency hell, obscure multi-import issues, __init__.py ugliness, imperative class declaration. Python only figured these things out much earlier to the extent that it has actually figured these things out.

...

Re:WebAssembly becomes a W3C Recommendation by wahern on Monday December 16, 2019 @09:08PM (#21809796)
> Python has figured out modules... much earlier,

You expect that to carry over to WASM environments?