Subesh Yadav @SubeshDev

Vyoma = Cloud Hypervisor + Rust daemon + CLI + Dashboard + CRI shim + Swarm + Teleport + TimeMachine. All in one binary. It’s an ecosystem, not just a runtime. Visit -vyoma-vm.netlify.app Github -github.com/VyomaVM/Vyoma #CloudNative #DevOps #DevTools #OpenSource #BuildInPublic

Containers share a kernel. That’s a feature and a vulnerability. Vyoma wraps each workload in a dedicated micro‑VM. You still get sub‑sec boot time, but with hardware‑level isolation. GitHub - github.com/VyomaVM/Vyoma Visit - vyoma-vm.netlify.app #CloudNative #DevOps #DevTools

@SaniaA54030 Thanks for your time to check this if possible I would love any review or feedback. Thanks again 😊

Containers share a kernel. That’s a policy. MicroVMs are physics. Enforced by hardware boundaries. One container escape = full host access. What if you got true VM isolation with the 250ms cold-boot speed of a container? Today, we're launching Vyoma on Product Hunt! 🚀🧵 (1/3)

producthunt.com/products/vyoma…

We are live on Product Hunt right now! As an open-source project your support is what drives us forward. If you want stronger, lighter container security, please take 10 seconds to check us out, leave some feedback and drop an upvote! Link to our launch in the replies below!👇

Vyoma — MicroVM Ecosystem: Run VMs like containers. Pervasive as the sky. producthunt.com/products/vyoma… via @producthunt

What if docker run actually launched a lightweight VM? That’s Vyoma. Same speed, actual security boundaries. I’ve been building this for months, and it’s finally working. Github - github.com/VyomaVM/Vyoma Browse - vyoma-vm.netlify.app #CloudNative #DevOps #MicroVM #DevTools

I’m building Vyoma – a MicroVM ecosystem that feels like Docker but gives every container its own kernel. No noisy neighbours. No shared kernel exploits. Just real isolation. 🐳 Github - lnkd.in/gRMpxiBD Browse - lnkd.in/gfAAdcCU #CloudNative #DevOps #MicroVM

8/8 ✅ Today’s key takeaway: Rc<T> empowers Rust with multiple ownership safely, using reference counting. Next: combining it with interior mutability (RefCell<T>) for even more flexibility. #100DaysOfRust #RustLang 🦀

7/8 But, beware ⚠️ - Rc<T> only handles ownership, not mutability. - If you need mutable shared state, you’ll combine it with RefCell<T>. (That’s coming up next 👀)

1/8 Day 30 of #100DaysOfRust 🦀 Today I explored Rc<T> (Reference Counting) — enabling multiple ownership in Rust! 📖 Blog post 👉 dev.to/subesh_yadav/d… 🧵 Let’s break it down 👇 #Rust #Rustlang #Rustaceans #LearningInPublic

(8/8) That’s a wrap for Day 29! Today was all about safe and predictable cleanup in Rust using the Drop trait. 📖 Full blog: dev.to/subesh_yadav/d…

(7/8) Key Takeaways ✅ Rust auto-calls drop at scope end ✅ Implement Drop for custom cleanup logic ✅ Use std::mem::drop for early cleanup ✅ No memory leaks, no double frees

🧵 (1/8) Day 29 of #100DaysOfRust – Mastering the Drop Trait Rust ensures memory safety without garbage collection. But how does it know when and how to clean things up? Enter the Drop trait 👇 #Rust #Rustlang #Rustaceans #LearningInPublic