38
A brief history of JavaScript
(deno.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 May 2025
38 points (97.5% liked)
Programming
20458 readers
84 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
This clearly shows how chaotic development of javascript really was.
It has always been like:
I suspect writing cross-platform desktop/mobile apps in HTML/CSS/JS was another big pull in this direction.
Many popular languages are bad, yet JS is the one with a widely-deployed OS interface written in it (WebOS).
If free-software/open-source devs hadn't got caught up chasing all this, there was a chance of replacing JS with other languages in the stack. HTML/CSS/your_language probably for apps initially, even making browsers support plugging in languages later. The docs say anything other than JS is not supported, so no <script type="text/your_language">. If only!
Apparently, this should be possible now (and, for apps, the result would be as "usable" as Electron) thanks to WebIDL. For example, Webkit's code to support Javascript access of browser objects is generated from a WebIDL spec. Generating support for <your_language>'s access to Webkit's browser objects is "just work".
Actually, https://tauri.app/ ...
Enough of this tangent now!