News for hackers. Stuff that matters.
Re:A peek into a possible future of Python in the browser by fragmede on Tuesday February 25, 2025 @05:12PM (#43178212)
You can dismiss their objections as childish, but people are gonna write in the language they want to (or are paid to) write in. If there's a large body of existing python code they'd have to rewrite in JavaScript, or use some python in the browser route for their purposes, why should we force other people to use typescript because some of us think it's better?

of course, LLMs, with their nascent ability to translate code into different languages, makes the question of rewriting something in a different language more tractable, but it's still a hike.

Re:A peek into a possible future of Python in the browser by amonroe805-2 on Tuesday February 25, 2025 @06:01PM (#43178666)
I mean, these things aren’t static. Python may be the second most popular language (behind JS/TS) today, but what if elixir takes over 10 years from now? There is no need for browsers to implement every language-of-the-day.

Additionally, browser JS adheres to a quite strict backwards compatibility requirements. Python can and does deprecate and remove APIs, and I would imagine the community would not like to lose that flexibility.

WASM is probably the best bet here, in that it provides a well-specified low-level target, such that the door is open for other languages for anyone who is allergic to learning/using javascript.

Re:A peek into a possible future of Python in the browser by dangus on Tuesday February 25, 2025 @08:53PM (#43179777)
Or perhaps you've got it backwards: there's no reason for browsers to prevent anyone from implementing any language they want.

JS and backwards compatibility gave me a chuckle...try hanging out on the web in IE11.

Re:A peek into a possible future of Python in the browser by pjaoko on Tuesday February 25, 2025 @09:04PM (#43179827)
What is the difference between the DOM API, a JavaScript engine and the JS language specification?
Re:A peek into a possible future of Python in the browser by athanagor2 on Wednesday February 26, 2025 @01:17PM (#43186389)
> You can dismiss their objections as childish, but people are gonna write in the language they want to (or are paid to) write in. If there's a large body of existing python code they'd have to rewrite in JavaScript, or use some python in the browser route for their purposes, why should we force other people to use typescript because some of us think it's better?

An existing codebase can certainly be an obstacle in adopting a PL but I don't think that's the main motivation in practice.

> of course, LLMs, with their nascent ability to translate code into different languages, makes the question of rewriting something in a different language more tractable, but it's still a hike.

Entirely agree. In my current company there's quite a bit of reluctance to spend some bucks to have good tools and I resent it. Rewriting (quickly!) some Python into say, C++, would be absolutely great.