Should we experiment some more with #runtimes and #protocols?
This is deliberately a very general question.
Drop your thoughts in replies, I'd love to exchange!
Should we experiment some more with #runtimes and #protocols?
This is deliberately a very general question.
Drop your thoughts in replies, I'd love to exchange!
Building a JavaScript Runtime in One Month, by @themackabu.dev:
Tonbo – an embedded database for serverless and edge runtimes
https://github.com/tonbo-io/tonbo
#HackerNews #Tonbo #embedded #database #serverless #edge #runtimes #technology
Comparing AWS Lambda ARM64 vs. x86_64 Performance Across Runtimes in Late 2025
#HackerNews #AWSLambda #ARM64 #x86_64 #Performance #Runtimes #2025
Eliminating JavaScript Cold Starts on AWS Lambda, by @goose.icu:
The Many, Many, Many JavaScript Runtimes of the Last Decade, by @shirakaba:
eBPF: Connecting with Container Runtimes
https://h0x0er.github.io/blog/2025/06/29/ebpf-connecting-with-container-runtimes/
#HackerNews #eBPF #Container #Runtimes #DevOps #Programming #Security
A Brief History of JavaScript, by @deno_land:
https://deno.com/blog/history-of-javascript
#history #javascript #ecmascript #typescript #json #javascriptengines #runtimes #browsers
JS does not need a browser. Here is my shallow understanding so far:
There are three important runtimes:
• #NodeJS is reliable, the most established, least secure, slowest.
• #Deno was created by the original developer of Node.js to address security and speed.
• #Bun is the fastest and the least mature of the 3.
I like this comparison: https://betterstack.com/community/guides/scaling-nodejs/nodejs-vs-deno-vs-bun/
Did you try Deno or Bun? (If not, please boost for diversity.)
#appDev #webDev #siteGenerator #siteGenerators #JS #runtimes #TypeScript