shy_mia@lemmy.blahaj.zone
on 24 Dec 2025 21:14
nextcollapse
Impressive, but we should stop trying to fit a square peg into a round hole. If there’s one thing the world doesn’t need is JavaScript in more places.
Flamekebab@piefed.social
on 24 Dec 2025 21:58
nextcollapse
Every time I consider learning more JS because it’s widely used I find myself between a rock and a hard place. It’s popular but it probably shouldn’t be and I don’t want to contribute to it being used even more for whatever mad shit is being attempted now.
kibiz0r@midwest.social
on 24 Dec 2025 22:16
collapse
Why?
The language itself is… fine. It has some bad decisions baked into it, but what language doesn’t? And it has a pretty mature security model, which is a big help for embedded devices.
And given that so many embedded devices these days are talking to cloud services — that are probably running JS, but are at least communicating via JSON — being able to share some cross-platform code or tooling can help things go quicker and/or safer.
Edit: This is probably not a route for teams that are chronically tight on memory and choose to solve that by spending hundreds of dev-hours on optimizing code rather than adding BOM cost. But for teams that could stand to increase BOM cost as long as the savings on dev-hours make up for it… it could be an option.
shy_mia@lemmy.blahaj.zone
on 25 Dec 2025 04:17
collapse
JavaScript doesn’t have a few bad decisions baked into it, it’s an absolute minefield. It was made for one thing and one thing only: making simple scripts for web pages. Anything beyond that and it becomes increasingly difficult to maintain. I honesty have no idea why devs are so hellbent on using it everywhere. Putting such an unreliable dynamic language, with absolutely no safety guards when it comes to type checking and serialization, on bare metal hardware is not something I’d ever consider in good conscience. Maybe it could be used for some IoT devices, but that’s it, definitely not for something that interfaces with machinery or anything more than something like a display.
TinyGo sounds like an infinitely better pick if someone wants to use a garbage collected language on an embedded device.
PushButton@lemmy.world
on 24 Dec 2025 21:25
nextcollapse
JavaScript for embedded, I’ve seen everything…
fokker_de_beste@feddit.nl
on 24 Dec 2025 22:36
nextcollapse
This seems similar to Espruino, wonder how it compares
JadedBlueEyes@programming.dev
on 25 Dec 2025 00:20
nextcollapse
I feel like people didn’t make this much fuss about micro python lol
thedeadwalking4242@lemmy.world
on 25 Dec 2025 16:35
collapse
I’ll take python over JavaScript any day
galaxy_nova@lemmy.world
on 25 Dec 2025 16:10
collapse
threaded - newest
Impressive, but we should stop trying to fit a square peg into a round hole. If there’s one thing the world doesn’t need is JavaScript in more places.
Every time I consider learning more JS because it’s widely used I find myself between a rock and a hard place. It’s popular but it probably shouldn’t be and I don’t want to contribute to it being used even more for whatever mad shit is being attempted now.
Why?
The language itself is… fine. It has some bad decisions baked into it, but what language doesn’t? And it has a pretty mature security model, which is a big help for embedded devices.
And given that so many embedded devices these days are talking to cloud services — that are probably running JS, but are at least communicating via JSON — being able to share some cross-platform code or tooling can help things go quicker and/or safer.
Edit: This is probably not a route for teams that are chronically tight on memory and choose to solve that by spending hundreds of dev-hours on optimizing code rather than adding BOM cost. But for teams that could stand to increase BOM cost as long as the savings on dev-hours make up for it… it could be an option.
JavaScript doesn’t have a few bad decisions baked into it, it’s an absolute minefield. It was made for one thing and one thing only: making simple scripts for web pages. Anything beyond that and it becomes increasingly difficult to maintain. I honesty have no idea why devs are so hellbent on using it everywhere. Putting such an unreliable dynamic language, with absolutely no safety guards when it comes to type checking and serialization, on bare metal hardware is not something I’d ever consider in good conscience. Maybe it could be used for some IoT devices, but that’s it, definitely not for something that interfaces with machinery or anything more than something like a display. TinyGo sounds like an infinitely better pick if someone wants to use a garbage collected language on an embedded device.
JavaScript for embedded, I’ve seen everything…
This seems similar to Espruino, wonder how it compares
I feel like people didn’t make this much fuss about micro python lol
I’ll take python over JavaScript any day
Hoping for the day JS dies