We cut @nodejs memory in half with a one-line Docker image swap.
No code changes. No new APIs. Just smaller heaps.
Here's what happened when we tested pointer compression on real workloads 🧵
I almost approved a security hole last year.
A simple image server. Clean code. Worked perfectly.
It also let anyone read any file on our filesystem.
Here's what happened 🧵
Just started diving into the preview copy of "Node.js Design Patterns" by @loige and @mariocasciaro!
Loving the clarity & depth so far. If you are into Node.js or backend architecture, this is shaping up to be a must-read. Kudos to the authors for crafting such a thoughtful book
For years, I’ve been asked whether I’ll ever write a book about @Nodejs.
I’m excited to announce the time has come.
Presenting “The Definitive Guide for Node.js in Enterprise”, a labour of love by myself, @Lucamaraschi, and every single member of the @Platformatic team.
The wait is over! 🎉 Fastify Mini Course is NOW LIVE for everyone! 🚀 Build high-performance APIs faster than ever. Get started here: https://t.co/F4BFCDtSlc #Fastify#NodeJS
Yesterday, we introduced multiple workers into @platformatic’s Watt application server 🚀
Why?
• To reduce resource wastage
• To improve app performance
Let's clear up a couple questions we've received! 👇
@_vangelis_66@athudeosthale@that_anokha_boy In that case you POST the user entered password to the server to hash it and check equality. You do not return the hashed stored value from the database so that someone can run a numerous techniques of cracking it.
🚀 Excited to announce that @ArrowoodTech will speak at #NodeConfEU 2024! Join us for "Node.js Streams vs Web Streams" as we dive into Next.js's evolution and key API differences. Don’t miss it!
Secure tickets: https://t.co/i22h8W2aQD
#NodeJS#NodeConfEU2024#November#Ireland
@drakakisgeo PiHole και την IP των συσκευών της μικρής. Θα το κάνει block 24/7 λόγω του rule για το domain. Μπορείς να βάλεις ένα group από domains επειδή έχει διαφορετικά domains όπως https://t.co/pPiMrrLGj7, https://t.co/qFlUBB782W κ.τ.λ.
Good news: the @nodejs downloads reached an all-time high in August, when Node.js v20 finally surpassed Node.js v18!
Bad news: Node.js v16 still has major usage; go update, it has been out of LTS for a year!
Really bad news: who the heck is still using Node.js v14 and v12?
@liran_tal I do not have anything against dotenv itself. Actually it’s a tremendously helpful package.
Where I disagree, is the way most tutorials teach it and how developers use it to start up / configure their projects.
It’s a configuration step, that might not be used in every provider
New Node.js feature is environment variables support
You can keep using dotenv, or you can remove it and spin up Node.js with --env-file=./.env and it will automatically populate your `process.env`