Quoting on Kit's endorsement on JavaScript (and what brought them into p5.js), it is a very portable language in the sense that it is more than just being understandable to human language, but its portal of executions are more multifaceted compared to Java / Python: you can access it via browser which is a super powerful user interface that is accessible from different devices and to different kind of users from all levels of programming knowledge.

Why browser seems to be monopolizing the portal of programming? We do have terminal but it seems most people prefers browser. Is it the graphical interface?

I also noted down possible things I can work on p5.xr:

1. First of all, need to contact them to see if they're still active.

2. Just looked into their website contribution guideline:

• Optimizing and refining the transformation matrices used for raycasting and AR.
• Switching to an inline generation tool (JSDocs) for generating the Reference section of this page.
• Adding more unit tests.
• Styling and Design to make the Reference section more readable.
• Any other bugs in the Github repo.

For this week homework, i added a hyperlink to CONTRIBUTING.md on the "developing contributing notes" section on the ml5 documentation site.

I also tried to access p5.xr on my VR headset in order to access the VR environment but still getting failure. I could consider raising this as an issue in the p5.xr github, however, i still want to double check that it is indeed true that i cannot run it on my headset. Posting an issue on Github makes me feel so self-aware, what if the issue that i posted turns out to be just something that i made out of my own mistake or something that i missed? Would it be better to remove/delete the issue or correct myself in the issue? I suppose correcting oneself may save another person who runs into this simple self-made mistake as well...

At this point, i'm thinking of a plan B to contribute to simple bugs that are raised on the ml5.js community as I notice that there are no recent PR/fixes merged since 2023! This one particularly caught my eye since it looks like something i can work on in a relatively short time.

UPDATE: it seems this library may have been replaced by a newer version: ml5-nextgen.