logo

kamal's Blog

🤟 Welcome to my tech blog. 💻

About Me

Hey there, I’m Kamal! 🤘 A tech enthusiast with a knack for sharing my mostly silly (and occasionally brilliant 🤯) discoveries in the coding world. This blog is my playground, where I spill the beans on what I’m learning—whether it’s the basics, the latest tech, or random tidbits that might make you go, “Wait, that’s a thing?” 😅

Here, you’ll find a mix of flexing, cheeky jokes, and even the occasional “mokka” humor to keep things real. Coding is fun, and I write these posts with that same energy! So if you’re having a rough day, stop by—you’ll either walk away grinning or at least wondering, “What was that?!” 😜

Stick around, laugh a little, learn a lot, and remember: coding is fun, and so is reading about it here! 🎉

Deno: The New Kid in Town 🌟

Deno: The New Kid in Town 🌟

Why Deno Might Just Take Over the Backend World 🚀

So, I recently got introduced to Deno, and let me tell you—it's like discovering a hidden gem in the world of backend development. But wait, before we dive deep into the wonders of Deno, have you ever wondered why it’s called Deno in the first place? Well, here’s the scoop:

The name Deno actually comes from Node.js but with a twist. If you sort the letters in "Node" alphabetically, you get Deno. Yeah, that's right! It’s like the name is literally telling us that Deno is Node but sorted out—a modernized, cleaner version of Node.js that aims to address all the problems Ryan Dahl, the creator of both, found in the original Node runtime.


Why Deno Will Take Over the Backend World 🌍

Now, let’s talk about why Deno is gonna take over the backend world. It’s not just because of the name (though that’s pretty clever too). Here’s why Deno is the next big thing:

  1. Security First 🔐
    In Deno, security is at the forefront. Unlike Node, where running a script can access the entire filesystem, Deno only allows access to the system if explicitly granted by the user. This makes it far more secure by default.

  2. Built-In TypeScript Support 💻
    Forget about manually configuring TypeScript in your project. Deno comes with built-in support for TypeScript right out of the box. No extra setup. No headaches.

  3. Standard Library 📚
    Deno comes with a powerful standard library, meaning you don’t need to rely on npm packages for everything. It includes modules for things like file operations, HTTP servers, and more—all maintained by the Deno team.

  4. Single Executable
    Deno is a single executable with no dependencies like Node's npm. Just install Deno, and you're ready to roll.


What You Gain by Knowing Deno 🤓

  • Cleaner Code
    Deno promotes cleaner, more efficient code. The runtime itself is designed to be more intuitive than Node, so you don’t spend your time debugging your environment setup.

  • Next-Gen Backend Development
    As JavaScript and TypeScript continue to dominate the backend world, knowing Deno is like having a superpower that makes you ready for the future.


Conclusion: Is Deno the Future? 🔮

With its security-first approach, built-in TypeScript support, and a modern take on backend development, Deno is definitely a force to be reckoned with. If you're into backend development, this is one tool you definitely want in your toolkit.

So, if you haven’t checked out Deno yet, now is the time. Get ahead of the curve, and who knows—you might just find yourself saying, "Node who?" 😎