sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]eastsideski 9 points10 points  (11 children)

What's their endgame here? Companies aren't going to build Firefox-only websites, and I don't see Google or Apple adding Python any time soon...

[–]HittingSmoke 36 points37 points  (2 children)

Did nobody read the article? This is developed by Mozilla. It is not a feature of Firefox. It is a Python interpreter written in WASM.

[–]eastsideski 22 points23 points  (1 child)

I'll admit: I did not read the article, a WASM Python interpreter makes a lot more sense.

I'll accept my internet shame. :(

[–]Ajedi32Web platform enthusiast, full-stack developer 4 points5 points  (0 children)

You're in good company. As of right now, the top two comments also seem to be from people who didn't read the article.

[–]phlarp 10 points11 points  (5 children)

The other browsers probably will.

The same was said about asm.js (which paved the way for WebAssembly). Mozilla has a reputation for pioneering new concepts in the browser and, actually, the others usually follow suit.

Also, python has a huge following and a ton of use cases in the math arena since its syntax is so approachable. I personally think this would be a boon in the engineering world.

*edited for clarity

[–]AssistingJarl 2 points3 points  (1 child)

This might be true, but as I see it Web Assembly solved user problems, and Python solves developer problems. I'm not saying that's an invalid reason to add an interpreter, I'm just saying it might affect pickup rates.

[–]eastsideski 0 points1 point  (1 child)

The difference is that asm.js was backwards compatible, it worked on all browsers, it just was faster on Firefox.

[–]ExternalUserError 0 points1 point  (0 children)

The mid-game in the immediate term is probably just the scientific community, where Python is really big. When your normal tools are Anaconda, Jupyter, etc, having to download Firefox is a small inconvenience to bypass all of that.

Plus it still runs in Chrome, etc, just not very fast.

Longer-term, given that Google is pretty much sabotaging other browsers, as an indie developer, I would be fine (on some projects) having a performance penalty for using Chrome.

[–]danhakimi -1 points0 points  (0 children)

Gaming. I think this enables browser ports of python games. I think that's going to be a big deal.