We are DevopsCentral!
Empowering the future of software delivery.
Join our vibrant community of DevOps practitioners & enthusiasts for Technical discussions
Sir, Issue is not resolved from the person failed to answer my queries Since 17th March 2026, till today 13th April 2026 i have deposited around ₹5000.
I am having only ₹318 balance left where is the rest money gone
@AU_JhansiNews@pradeepjain52@UPPCLLKO@dvvnlhq
Cloudflare is again facing an outage today, second time in a month!!
All major trading platforms like Groww, Zerodha are not working
#Cloudflare#Groww#cloudflaredown
🚀 Google just dropped Gemini 3 – their most intelligent AI model yet!This isn't just an update. It's a game-changer for reasoning, multimodal understanding, and autonomous AI agents.
Here's what you need to know 🧵
#AI#GoogleGemini#AGI#Gemini
🔹 Cache
After execution, Node caches the module in require.cache.
So next time you require("./math"), it’s not reloaded — it’s fetched instantly from memory.
This makes modules behave like singletons.
Best Practices
While you can add properties to the global object, it's generally discouraged because:
It can lead to naming conflicts
Makes code harder to test and debug
Goes against Node.js module philosophy
⭐️Node.js Global Object ⭐️
In Node.js, the global object is the top-level object that serves as the global namespace, similar to how window works in browsers. It's accessible from anywhere in your Nodejs application without needing to import or require it
1/n
#nodejs#TechTwitter
Important Differences from Browser
Unlike browsers where window === this in the global scope, Node.js has some nuances:
1️⃣ The global object is called global, not window
2️⃣Variables declared with var at the top level of a module are not added to the global object (they're scoped to the module)
3️⃣Each module has its own scope, so global pollution is less of an issue