<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ritish_Singha on Medium]]></title>
        <description><![CDATA[Stories by Ritish_Singha on Medium]]></description>
        <link>https://medium.com/@ritishsingh900?source=rss-56204e901a25------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*S5JAkFEcOWSjOgD8LjrBRA.jpeg</url>
            <title>Stories by Ritish_Singha on Medium</title>
            <link>https://medium.com/@ritishsingh900?source=rss-56204e901a25------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:26:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ritishsingh900/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Web Engine Performance: Why V8 + Blink Lead the Pack]]></title>
            <link>https://medium.com/@ritishsingh900/web-engine-performance-why-v8-blink-lead-the-pack-052b3e48f054?source=rss-56204e901a25------2</link>
            <guid isPermaLink="false">https://medium.com/p/052b3e48f054</guid>
            <dc:creator><![CDATA[Ritish_Singha]]></dc:creator>
            <pubDate>Tue, 28 Jul 2026 14:15:52 GMT</pubDate>
            <atom:updated>2026-07-28T14:36:01.083Z</atom:updated>
            <content:encoded><![CDATA[<p>The web engine performance is really important. The latest numbers show that V8 and Blink are the best. They are used by 65 percent of people around the world.</p><p>Here are some key points to think about:</p><p>Execution Speed: V8 is 15 to 20 percent faster than SpiderMonkey when it comes to doing a lot of JavaScript work.</p><p>Feature Fidelity: Blink is really good at handling CSS. Gets it right about 98.4 percent of the time.</p><p>Rendering Efficiency: Blink is also good at rendering things on the screen. Can do it at 60 frames per second.</p><p>WebAssembly Growth: More and more people are using WebAssembly. It is growing really fast. About 45 percent per year.</p><p>The future of the web looks really exciting with things, like Edge rendering and WebGPU. These things will make it possible to do AI work faster and safer.</p><p>This means that developers can build fast and secure applications using WebAssembly and WebGPU. For people who build things on the web this means that having performance is no longer something special. It is what people expect.</p><p>So what do you think. Will WebAssembly and WebGPU change the way we make web apps in the ten years or will native apps still be the best?</p><p>#WebPerformance #V8 #Blink #WebAssembly #WebGPU #EngineeringInnovation</p><p>Explore: <a href="https://drive.google.com/file/d/1g5WfrWtTr-llIkfj3vAv_EgKx7B67C0y/view?usp=sharing">https://drive.google.com/file/d/1g5WfrWtTr-llIkfj3vAv_EgKx7B67C0y/view?usp=sharing</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ebv3b1EdWc7X7GHXEeta0g.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=052b3e48f054" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MiMo Code — Xiaomi’s Free Open‑Source AI Assistant]]></title>
            <link>https://medium.com/@ritishsingh900/mimo-code-xiaomis-free-open-source-ai-assistant-25673c58cab6?source=rss-56204e901a25------2</link>
            <guid isPermaLink="false">https://medium.com/p/25673c58cab6</guid>
            <category><![CDATA[mimo-code]]></category>
            <dc:creator><![CDATA[Ritish_Singha]]></dc:creator>
            <pubDate>Tue, 21 Jul 2026 18:00:23 GMT</pubDate>
            <atom:updated>2026-07-21T18:00:23.329Z</atom:updated>
            <content:encoded><![CDATA[<p>I was looking at Xiaomi’s coding assistant called MiMo Code, and I think it is really interesting for people who work with AI, coding, computer vision, and creative development. MiMo Code is a helper that can read and write code, run commands, manage Git, and remember what you were working on over time. What I like about it is that it uses the MiMo 2.5 model, which helps it understand images and makes it easier to create things and try out ideas quickly.</p><p>These days, generating code is not enough. We need tools that can examine an existing codebase, interpret pictures or designs, and help turn those into websites, demos, or animations. MiMo Code seems to do all that by combining project memory, image understanding, and interactive workflows to accelerate experimentation. That makes it a great tool for trying out ideas and creating new things.</p><p>There are several ways to try MiMo Code. For example, you can use it to generate product catalogs from images, convert a picture into a responsive website, build demos from visual inputs, or create animations and prototypes that combine computer vision with natural language. Because it is open source, developers can inspect the implementation, add new features, and integrate it into their own projects.</p><p>To get started with MiMo Code, install it and then use simple commands like /models to choose MiMo Auto and /variants to adjust how it reasons or generates. I plan to try it out and explore its image-driven workflows and rapid prototyping capabilities. If you work with AI, web automation, or computer vision, you should definitely check it out.</p><p>GitHub: <a href="https://github.com/XiaomiMiMo/MiMo-Code">https://github.com/XiaomiMiMo/MiMo-Code</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iPLdTNPSP66_zZKhXt9imw.png" /></figure><p>#AI #MachineLearning #ComputerVision #GenerativeAI #OpenSource #WebDevelopment #MiMoCode</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25673c58cab6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Couldn’t Dual-Boot. So I Caged a Lion. Now Linux Thinks It Owns My Machine — Windows Just Smiles.]]></title>
            <link>https://medium.com/@ritishsingh900/i-couldnt-dual-boot-so-i-caged-a-lion-now-linux-thinks-it-owns-my-machine-windows-just-smiles-b163d6e4e606?source=rss-56204e901a25------2</link>
            <guid isPermaLink="false">https://medium.com/p/b163d6e4e606</guid>
            <category><![CDATA[a-caged-lion]]></category>
            <dc:creator><![CDATA[Ritish_Singha]]></dc:creator>
            <pubDate>Sat, 18 Jul 2026 13:50:17 GMT</pubDate>
            <atom:updated>2026-07-18T16:30:35.243Z</atom:updated>
            <content:encoded><![CDATA[<p>🦁 I tried to set up a DevOps lab. Windows said no. Here’s exactly how I outsmarted it — and discovered the most elegant OS analogy I’ve ever seen.</p><p>My NVMe C-drive had 10 GB of free space left. Dual-booting was out — modifying a bootloader with near-zero disk space bricks machines. I needed Windows and Linux running simultaneously, with Linux living on my 301 GB H-drive.</p><p>That’s when I found WSL 2. And the analogy that changed how I see operating systems forever.</p><p>━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━</p><p>🦁 The Wolf Never Fought the Lion. It Just Built a Smarter Cage.</p><p>━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━</p><p>Linux is natively a Lion.</p><p>It’s a dominant, bare-metal system — designed from the ground up to rule over every CPU thread, every byte of RAM on an entire machine. It doesn’t ask permission. It takes command.</p><p>Windows is the Wolf.</p><p>And the Wolf built a cage.</p><p>WSL 2 (Windows Subsystem for Linux) is that cage — an entire Linux kernel, isolated inside a dynamic virtual hard disk (ext4.vhdx) on my H-drive. The Lion thinks it rules its own kingdom. It does — but that kingdom is a container. When the Lion needs to roar (Docker, CI/CD pipelines, automation scripts), Windows dynamically slides CPU threads and RAM through the bars. The moment the task completes, it reclaims that power instantly.</p><p>The Lion gets to be a Lion. Windows stays in control. I get a full DevOps lab — zero reboots required.</p><p>Getting there? That took some fighting.</p><p>━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━</p><p>🛠️ HOW I GOT STUCK — AND HOW I BROKE THROUGH</p><p>━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━</p><p>🔴 BLOCKER 1 — The Hypervisor Wasn’t Installed</p><p>First command:</p><p>wsl — install -d Ubuntu</p><p>First error:</p><p>Wsl/InstallDistro/Service/RegisterDistro/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED</p><p>My BIOS had virtualization enabled — but that’s only the hardware capability. Windows still needs to activate the Virtual Machine Platform (the software bridge) before WSL 2 can create its container. Two completely different layers.</p><p>✅ FIX (Admin CMD):</p><p>dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart</p><p>bcdedit /set hypervisorlaunchtype Auto</p><p>Clean system reboot. Hypervisor initialized. The cage was ready to be built.</p><p>— -</p><p>🔴 BLOCKER 2 — The Path Trap (ERROR_FILE_NOT_FOUND)</p><p>Running the WSL installer from inside a nested H-drive folder gave me ERROR_FILE_NOT_FOUND. Here’s why: WSL doesn’t just install an app — it registers Ubuntu as a system component inside Windows. When you run the installer from a deeply nested custom path, Windows loses track of its own internal references.</p><p>✅ FIX — Treat it like a system update, running from C:&gt;</p><p>wsl — install — distribution Ubuntu</p><p>First login. Created my UNIX user account: ritish. The Lion had a name.</p><p>— -</p><p>🔴 BLOCKER 3 — The Lion Was in the Wrong Kingdom</p><p>Ubuntu was running. But it was sitting on my dying C-drive. I needed to migrate the entire system to my 301 GB H-drive without losing a single file. Here’s the exact migration:</p><p>Step A — Shut down all WSL processes:</p><p>wsl — shutdown</p><p>Step B — Export the entire Linux system into a portable archive (the “moving box”):</p><p>wsl — export Ubuntu “H:\Linux\ubuntu-backup.tar”</p><p>Step C — Unregister Ubuntu from C-drive and recover the disk space:</p><p>wsl — unregister Ubuntu</p><p>Step D — Import and unpack Ubuntu into its permanent home:</p><p>wsl — import Ubuntu “H:\Linux\WSL” “H:\Linux\ubuntu-backup.tar”</p><p>Step E — Restore my default user login (prevents root login by default):</p><p>wsl — manage Ubuntu — set-default-user ritish</p><p>Step F — Delete the temporary archive, recover 1.2 GB:</p><p>del “H:\Linux\ubuntu-backup.tar”</p><p>Running whoami inside the terminal: ritish ✅(Example)</p><p>Current footprint: 2 GB. Maximum potential: 301 GB. Dynamic growth — it only takes what it needs.</p><p>━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━</p><p>🧠 5 REASONS EVERY DEVOPS ENGINEER SHOULD KNOW WSL 2</p><p>━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━</p><p>Why #1 — True Simultaneous Workflows</p><p>Write code in VS Code on Windows. Test it on a live Linux kernel running next to it in real time. No rebooting. No context switching. No “save everything and switch OS.” Just: build, test, iterate.</p><p>Why #2 — The Cloud Doesn’t Give You Hardware</p><p>This is the big one. AWS, Azure, GCP don’t give you bare metal. They give you a Linux system inside a virtualized container. Learning to work inside WSL is conceptually identical to managing a cloud VM. You’re training for production from day one.</p><p>Why #3 — Zero Boot Penalty</p><p>WSL starts in under 2 seconds. Dual-boot Linux takes 30–60 seconds to reboot. In a DevOps workflow where you’re constantly switching contexts, that overhead compounds into hours of wasted time every month.</p><p>Why #4 — Seamless File System Access</p><p>Windows can browse the Linux file system natively in File Explorer. Linux auto-mounts your Windows drives — my H-drive is accessible at /mnt/h/ from inside the terminal. No file transfers. No network shares. Just native access, both directions.</p><p>Why #5 — Docker on a Real Linux Kernel</p><p>Docker was built for Linux containers. Running Docker inside WSL 2 means you’re running containers on a real Linux kernel — not an emulation layer, not a compatibility shim. It’s the closest thing to a production cloud environment you can run on a Windows laptop.</p><p>━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━</p><p>The Lion is caged, fed, and ready to roar. 🦁</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fmHNdmcVcU6Jm9AgaMn0_Q.png" /></figure><p>#DevOps #Linux #Ubuntu #WSL2 #CloudComputing #Docker #SystemsEngineering #Infrastructure #TechJourney #ContinuousLearning #Windows11 #Windows</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b163d6e4e606" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>