Replies: 1 comment
-
Given that is a near future, we might be able to run Python in the browser (https://www.zdnet.com/article/programming-languages-want-to-run-python-code-in-a-browser-soon-you-might-be-able-to/) this does not really have all that much prio at the moment. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The way Hedy currently works is that we transpile Hedy to Python serverside, and then execute the generated Python on the front-end using Skulpt. This was a fine idea when Hedy was a prototype because it was easiest to achieve, but now has some downsides now that we are bigger, for example it harms performance, and also Skulpt has some edge cases where it does not exactly works like Python.
It would be a lot better when we would just generate JavaScript serverside and sent that back, most likely shaving of some execution time!
This would make for a nice side project for someone, especially I guess for a (group of) student(s)!
The nice thing about this project is that it can be approached gradually! Even doing this for 1 level already adds a bit of benefit while leaving the rest as they are. It would of course impact a lot, most notable also many test cases that currently are validated against the generated Python code, not against the output.
Beta Was this translation helpful? Give feedback.
All reactions