Post #3734033
2026-07-11 06:19 UTC
Replies (1)
-
@TommyTorty10@infosec.exchange 2026-07-11 06:42
@ethan256@mas.to Greetings from California! I think my first more serious use of JS was in my university senior project. We had a robot autonomously mapping and navigating through a room and using a camera to recognize objects as it went. The idea was that it was a proof-of-concept for an accessibilty aid to help blind people locate and retrieve dropped objects. I used JS to do final filtering to select good object identifications before listing out every object the robot saw in the UI. In the end, the JS was short and simple, but the learning curve of getting it to play nice with the robotics software was steep. At that point in my education, I was near the end of university, so learning another language on top of the many I had already dabbled in wasn't bad, but was certainly more stressful on a deadline. Nowadays I only use it when occasionally updating or making browser extensions. JS is hard for reasons that can be subtle and difficult to descibe. Many aspects of it are unforgiving. If you have the luxury of time to learn an object oriented language after JS, I would recommend giving it a go. It gets easier to pick up new languages as you grow more familiar with popular design patterns. Imo, many other OOP languages are better at communicating with the dev than JS and make troubleshooting easier.