DEV Community: Toni Angelchovski

Why GNU/Linux Isn't for Everyone - and That's a Good Thing

Toni Angelchovski — Sat, 15 Aug 2026 21:10:47 +0000

We have been hearing "Linux is ready for the desktop" for twenty years. Maybe the question is the wrong one.

1. The myth of mass adoption

Every year somebody announces the year of Linux on the desktop. Ubuntu was going to deliver it. Then Mint. Then the Steam Deck. Every wave ends the same way: noise, articles, enthusiasm, and six months later the market share is roughly where it was.

The reason is not the quality of the code. The reason is that Linux is not a product. It is a philosophy, and philosophies do not sell to a mass market.

The average user wants to double-click and have things work. They want Adobe Creative Suite behind one installer. They do not want to know what a dependency is, what permissions are, or why the video plays without sound.

Linux wants the opposite. It wants you to think. That is precisely why it stays "hard" for most people.

Linux is not hard. It just refuses to pretend that a computer is magic.

2. Control is responsibility

Linux gives you control over everything. That is both its strength and the price you pay for it.

On Windows, when something breaks, Microsoft is at fault. On Linux the person at fault has a name and it is yours. Installed a driver from a questionable PPA? Your problem. Edited a config without a backup? Your problem. Wiped a partition because you were in a hurry? Your problem.

sudo rm -rf /

This is one of the few places a modern distribution will actually stop you. GNU coreutils refuses to run that without an explicit --no-preserve-root. It is close to the only safety catch the system puts in your way. Everywhere else it assumes you know what you are doing.

That is a form of respect for your intelligence. And a test of it.

3. The Unix philosophy

Linux inherits three rules older than most of the people using it:

Do one thing and do it well
Everything is a file
Small tools that compose

This is a philosophy written by engineers, not by a marketing department. It produces systems that are powerful, flexible and occasionally infuriating.

find /var/log -name "*.log" -mtime +7 -print0 | xargs -0 rm --

The command does exactly what it says: finds log files older than a week and deletes them. Clear, short, predictable.

Notice the -print0 and the -0. Without them, any filename containing a space splits into two arguments and the command starts deleting things you never asked about. There is no "Delete old files" button here that already thought this through on your behalf.

That is the difference in one sentence. A graphical interface hands you a finished solution. A terminal hands you components and expects you to assemble them.

4. Self-selection, not superiority

Linux filters people out. Not deliberately, not maliciously. By design.

It tends to lose people who want the shortest path and nothing else, and to keep people who would rather understand the machine than be shielded from it. Understanding costs time up front and pays back later, and not everybody wants that trade.

I want to be careful here, because this is where essays like this usually go wrong. The filter is not a measure of anyone's worth. Not everybody wants to know how their car works. Most people want to drive it to the shop and back, and that is a completely reasonable way to own a car. The plumber who does not care about init systems is not a lesser person than the sysadmin who does. They just have a different relationship with the tool.

The point is not that Linux users are better. It is that Linux does not try to be for everyone, and stops being itself when it tries.

5. Why that is a good thing

Suppose the wish came true and Linux really did go mainstream. What arrives in the box with mass adoption?

Bloated distributions optimized for "easy" rather than for work
Proprietary additions in the name of "compatibility"
Vendor lock-in packaged as a Linux Experience
Telemetry on by default, because it "improves the user experience"

The community today is small but dense. The people in it chose to be there rather than finding it preinstalled. You can see it in the code, in the documentation, and in the answers on forums.

A thousand people who read man pages beat a million waiting for someone else to fix it.

6. The barrier as a filter

Bitcoin works on the same mechanism. To use it meaningfully you have to understand private keys, seed phrases and transaction fees. That repels the casual user, and that is part of why the network stays robust. Its population is self-selected.

Linux is the same story with different syntax. The difficulty is not a bug. It is a characteristic.

7. The honest part

This is where I argue with myself, because manifestos love to skip the uncomfortable bit.

Not every difficulty in Linux is philosophy. A good part of it is just poor work. Documentation written by someone who already knows the answer. Error messages that tell you nothing. Projects that change the config format every other release. Calling that a "filter" is a convenient excuse.

The barrier that means something is the one that makes you understand the system. The barrier that means nothing is the one that costs you three hours because of a missing line in a README.

The first is a feature. The second is a debt the community owes itself.

8. From the garage: sync under fire

A concrete example, because theory does not save data at three in the morning.

I was in an SSH session on one of my own nodes. Just me, a black screen and a terminal. Then htop went red, load average climbing in a shape normal traffic does not make. Someone was working the box deliberately: an aggressive SSH brute force filling auth.log with thousands of lines per second, plus a SYN flood eating the connection tracking table and leaving the kernel with no room for legitimate connections.

And right then, under the load, one of the disks in the software RAID 5 array died.

Not because of the attack. The attack simply exposed it. The drive was already sick and had been hiding behind low traffic. dmesg filled with I/O errors, the kernel marked the device faulty, the array dropped to degraded.

A polished commercial OS would have frozen, or produced a beautiful popup that nobody would see at three in the morning. Debian just kept writing to /var/log/auth.log and dmesg and left me alone in the console to decide what to save first: the network or the data.

The network, as it turned out, and for a specific reason. Every log line the brute force generated was another write competing for the same I/O the array needed. Fix the storage first and the attack keeps feeding the problem. A few iptables rules dropped the malicious traffic at kernel level, and the machine got quiet enough to work on.

Then the corpse. cat /proc/mdstat showed the ugly truth: [_UU]. Fail and remove the dead member with mdadm --manage /dev/md0 --fail /dev/sdX --remove /dev/sdX, partition the replacement in the dark, add it back, and then the longest part of the night: watching a rebuild crawl and hoping the second disk holds.

That last part is not paranoia. During a rebuild the surviving disks work hardest and get read end to end. A single unrecoverable read error anywhere in that pass takes the whole array with it. It is the main argument for RAID 6 or RAID 10 on anything large.

I lost four hours to man pages and commands the whole project depended on. But I came out knowing how to juggle packet filtering and broken storage at the same time, with no interface holding my hand.

That is the trade. You pay once in lost sleep so you do not pay repeatedly in lost data.

Since the story of what it cost is only half a story, here is what I bought with it. Key-based SSH only, password authentication disabled. fail2ban cutting the brute force before it reaches the logs. SYN cookies and new-connection limits in the kernel, made permanent in /etc/sysctl.d/ rather than living in RAM until the next reboot. smartd alerting on rising Reallocated_Sector_Ct, which had almost certainly been climbing for weeks while nobody read it. Monthly array scrubs, so weak sectors surface while there is still redundancy to repair them. And a spare disk on the shelf, already partitioned, instead of a browser tab at three in the morning.

9. Conclusion

Linux does not need mass adoption. It needs the right people: the ones who see a computer as an instrument for thinking rather than an appliance for consuming.

If you want a system that does what you tell it instead of what a corporation decided on your behalf, Linux is waiting. Just keep two things open: the terminal and your mind.

# the barrier is the feature

Originally published in Bulgarian on my own forum, linked as the canonical source above. I run the whole thing on my own hardware, which is how I ended up with the story in section 8.

Enchanted Winter Realms - A Journey Through the Solstice

Toni Angelchovski — Sun, 22 Dec 2024 12:58:01 +0000

This is a submission for Frontend Challenge - December Edition, Glam Up My Markup: Winter Solstice

Note: During the development of this project, I noticed that the theme of the winter solstice has also inspired other participants in the challenge. This highlights how inspiring nature and the magic of this season can be. My inspiration comes from my personal vision of winter, focusing on the details and interpretation of its charm. I hope this project contributes to the diversity of ideas in this challenge.

What I Built

"Winter Solstice Magic" is an interactive web scene designed to capture the essence and enchantment of the winter solstice. The project features animated elements like a sun, moon, stars, aurora borealis, falling snow, and additional festive touches such as a glowing fire, twinkling lights, and shooting comets. The goal was to create a visually engaging experience that immerses the viewer in the magic of winter while showcasing the power of modern web technologies.

Demo

You can experience the project live here: Winter Solstice Magic Demo

The full code is available The is here:

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>Winter Solstice Scene</title>
    <style>
        body {
            margin: 0;
            overflow: hidden;
            background: linear-gradient(to bottom, #003366, #000);
            display: flex;
            justify-content: center;
            align-items: center;
            height: 100vh;
            color: white;
            font-family: Arial, sans-serif;
        }

        .sky {
            position: absolute;
            top: 0;
            left: 0;
            width: 100%;
            height: 100%;
            background: linear-gradient(to top, #1e3c72, #2a5298);
            z-index: -1;
            animation: skyTransition 20s infinite alternate;
        }

        .sun {
            position: absolute;
            width: 80px;
            height: 80px;
            background: radial-gradient(circle, #ffcc00, #ff9900);
            border-radius: 50%;
            animation: moveSun 8s infinite;
            z-index: 1;
        }

        .moon {
            position: absolute;
            width: 60px;
            height: 60px;
            background: radial-gradient(circle, #ffffff, #cccccc);
            border-radius: 50%;
            animation: moveMoon 8s infinite;
            z-index: 1;
            opacity: 0.8;
        }

        .stars {
            position: absolute;
            top: 0;
            left: 0;
            width: 100%;
            height: 100%;
            pointer-events: none;
            z-index: 0;
        }

        .star {
            position: absolute;
            width: 3px;
            height: 3px;
            background: white;
            border-radius: 50%;
            opacity: 0;
            animation: twinkle 3s infinite;
        }

        .aurora {
            position: absolute;
            top: 0;
            left: 0;
            width: 100%;
            height: 100%;
            background: radial-gradient(circle, rgba(0, 255, 150, 0.3), transparent);
            opacity: 0.4;
            animation: auroraEffect 10s infinite alternate;
            z-index: -1;
        }

        .comet {
            position: absolute;
            width: 10px;
            height: 10px;
            background: radial-gradient(circle, #ffffff, transparent);
            border-radius: 50%;
            box-shadow: 0 0 10px 5px #ffffff;
            opacity: 0.8;
            animation: flyComet 6s infinite;
        }

        .light-string {
            position: absolute;
            bottom: 10%;
            width: 100%;
            display: flex;
            justify-content: space-evenly;
        }

        .light {
            width: 15px;
            height: 15px;
            background: red;
            border-radius: 50%;
            animation: blinkLight 2s infinite alternate;
        }

        .title {
            position: absolute;
            top: 50%;
            left: 50%;
            transform: translate(-50%, -50%);
            font-size: 3.5rem;
            font-family: 'Cinzel Decorative', cursive;
            color: #ffddcc;
            text-shadow: 3px 3px 10px #000;
            opacity: 0;
            animation: fadeInOut 10s infinite;
        }

        .fire {
            position: absolute;
            bottom: 5%;
            left: 50%;
            transform: translateX(-50%);
            width: 50px;
            height: 100px;
            background: radial-gradient(circle, rgba(255, 165, 0, 1), rgba(255, 69, 0, 0.7));
            border-radius: 50%;
            animation: flicker 0.5s infinite;
        }

        @keyframes flicker {
            0%, 100% {
                transform: scale(1);
                opacity: 0.8;
            }
            50% {
                transform: scale(1.2);
                opacity: 1;
            }
        }

        .tree {
            position: absolute;
            bottom: 10%;
            left: calc(10% + var(--position, 0%));
            width: 40px;
            height: 60px;
            background: linear-gradient(to bottom, #228B22, #006400);
            clip-path: polygon(50% 0%, 0% 100%, 100% 100%);
        }

        @keyframes fadeInOut {
            0%, 100% {
                opacity: 0;
            }
            50% {
                opacity: 1;
            }
        }

        @keyframes moveSun {
            0% {
                top: 80%;
                left: 10%;
            }
            50% {
                top: 20%;
                left: 50%;
            }
            100% {
                top: 80%;
                left: 90%;
            }
        }

        @keyframes moveMoon {
            0% {
                top: 20%;
                left: 90%;
            }
            50% {
                top: 10%;
                left: 50%;
            }
            100% {
                top: 20%;
                left: 10%;
            }
        }

        @keyframes skyTransition {
            0% {
                background: linear-gradient(to top, #1e3c72, #2a5298);
            }
            50% {
                background: linear-gradient(to top, #000428, #004e92);
            }
            100% {
                background: linear-gradient(to top, #2c3e50, #4ca1af);
            }
        }

        @keyframes twinkle {
            0%, 100% {
                opacity: 0;
            }
            50% {
                opacity: 1;
            }
        }

        @keyframes auroraEffect {
            0% {
                transform: translateX(-20px) scale(1.2);
            }
            100% {
                transform: translateX(20px) scale(1.5);
            }
        }

        @keyframes flyComet {
            0% {
                top: -10%;
                left: 110%;
            }
            100% {
                top: 110%;
                left: -10%;
            }
        }

        @keyframes blinkLight {
            0% {
                background: red;
            }
            100% {
                background: yellow;
            }
        }

    </style>
    <link href="https://fonts.googleapis.com/css2?family=Cinzel+Decorative:wght@400;700&display=swap" rel="stylesheet">
</head>
<body>
    <div class="sky"></div>
    <div class="aurora"></div>
    <div class="sun"></div>
    <div class="moon"></div>
    <div class="stars"></div>
    <div class="light-string">
        <div class="light"></div>
        <div class="light"></div>
        <div class="light"></div>
        <div class="light"></div>
        <div class="light"></div>
    </div>
    <div class="title">Winter Solstice Magic</div>
    <div class="fire"></div>
    <div class="tree" style="--position: 10%;"></div>
    <div class="tree" style="--position: 30%;"></div>
    <div class="tree" style="--position: 70%;"></div>
    <script>
        // Add twinkling stars
        const starContainer = document.querySelector('.stars');
        for (let i = 0; i < 100; i++) {
            const star = document.createElement('div');
            star.classList.add('star');
            star.style.top = `${Math.random() * 100}%`;
            star.style.left = `${Math.random() * 100}%`;
            star.style.animationDelay = `${Math.random() * 5}s`;
            starContainer.appendChild(star);
        }

        // Create a comet
        const createComet = () => {
            const comet = document.createElement('div');
            comet.classList.add('comet');
            comet.style.top = `-${Math.random() * 50}px`;
            comet.style.left = `${Math.random() * window.innerWidth}px`;
            document.body.appendChild(comet);

            setTimeout(() => comet.remove(), 6000);
        };

        setInterval(createComet, 8000);

        // Interactive snow effect
        const createSnowflake = () => {
            const snowflake = document.createElement('div');
            snowflake.classList.add('snowflake');
            snowflake.style.position = 'absolute';
            snowflake.style.top = `-5px`;
            snowflake.style.left = `${Math.random() * window.innerWidth}px`;
            snowflake.style.width = snowflake.style.height = `${Math.random() * 5 + 2}px`;
            snowflake.style.background = 'white';
            snowflake.style.borderRadius = '50%';
            snowflake.style.opacity = `${Math.random() * 0.8 + 0.2}`;
            snowflake.style.transition = 'top 3s linear';
            document.body.appendChild(snowflake);

            setTimeout(() => {
                snowflake.style.top = `${window.innerHeight + 10}px`;
            }, 50);

            setTimeout(() => {
                snowflake.remove();
            }, 3000);
        };

        setInterval(createSnowflake, 150);
    </script>
</body>
</html>

Below is a preview image of the project:

Journey

Creating "Winter Solstice Magic" was an exciting and challenging process. Here is an overview of my journey:

The Idea

I wanted to bring the beauty and mystique of the winter solstice to life through an immersive web experience. The project was inspired by the natural elements of winter and the peaceful yet vibrant atmosphere of the season.

Technologies Used

HTML for the basic structure.
CSS for animations, gradients, and styling.
JavaScript for dynamic interactivity, including the generation of snowflakes, stars, and comets.
Google Fonts to enhance the aesthetic appeal of the title text with the "Cinzel Decorative" font.

Key Features

Dynamic Background: The sky transitions smoothly between gradients to mimic different times of the day.

Interactive Elements: Stars twinkle, snowflakes fall, and comets streak across the screen to add life to the scene.

Festive Details: Twinkling lights and a glowing fire enhance the seasonal charm.

Accessibility: The project was designed to be visually engaging and lightweight, ensuring it works seamlessly across devices.

Challenges and Learnings

One challenge was optimizing animations to ensure smooth performance on various devices. I learned a lot about managing animation performance using CSS and JavaScript. I am particularly proud of the seamless integration of multiple animated elements without compromising the responsiveness of the page.

What’s Next

In the future, I would like to:

Add audio elements, such as subtle winter-themed background music or sound effects.

Introduce user interactivity, allowing viewers to customize aspects of the scene.

Expand the project into a series featuring different seasonal themes.

License

The code for this project is licensed under the MIT License, making it free and open for anyone to use or adapt.

Acknowledgments

Special thanks to the DEV Community for hosting this challenge and providing inspiration through their platform. Thank you for considering my submission! I hope you enjoy "Winter Solstice Magic."

How to Recover Access to BitLocker After Losing Your Password? 🔐

Toni Angelchovski — Wed, 18 Dec 2024 14:25:58 +0000

BitLocker is an incredibly powerful tool for protecting your data, but what happens if you lose your password or Recovery Key? 😟 Don’t worry – this article provides a comprehensive guide to all the options that can help you regain access to your encrypted drive. 🚀

Recovery Key – Your Lifesaver! 🔑
The Recovery Key is a unique 48-digit code that allows you to unlock BitLocker if you lose your password. Here’s where you can find it:

Microsoft Account: Check here if the key is saved in your profile.
Text File or USB Device: Look for the Recovery Key file on another computer or USB drive.
Printout: Review documents you might have printed and stored securely.
Active Directory: If the computer is work-related, your IT department may have stored the key in Active Directory.
💡 Tip: Keep your Recovery Key in a secure place, such as the cloud or a physical backup device!

What to Do If You Don’t Have a Recovery Key? 🚨
If the key is lost, your options are limited, but there are still alternatives:

🛠 1. Check for Cached Passwords
If your device is part of a domain or corporate network, the password might be cached locally. Check:

Active Directory (with the help of your IT administrator).
Local user accounts, if auto-login was enabled.
🔍 2. Recover Unencrypted Data
If the disk is partially encrypted, you can use tools such as:

EaseUS Data Recovery Wizard
Recuva
R-Studio
⚠️ Note: These tools can only retrieve unencrypted files.

⚡ 3. Extract Using the TPM Chip
If you used BitLocker with TPM (Trusted Platform Module), the encryption keys might be stored in your device’s hardware.

Specialized tools can extract these keys, but this requires advanced technical knowledge and is a risky process.
📞 4. Contact Data Recovery Professionals
If the data is critical, professional companies can attempt recovery. They use advanced methods for:

Hardware-level extraction of encryption keys.
File recovery through specialized software.
💰 Drawback: These services are expensive and not always successful.

🗑️ 5. Last Resort – Format the Disk
If none of the above options work and the data is not critical:

Open Disk Management.
Delete the encrypted partition and create a new one.
⚠️ Warning: This will completely erase all data on the disk.

Prevention for the Future: How to Protect Yourself from Such Situations? 🌟
Save the Recovery Key in multiple locations:
In your Microsoft Account.
On a USB drive.
On a securely stored printed document.
Regularly back up important data.
Set up safe data storage: For example, use cloud services like OneDrive or Google Drive.
Conclusion 🧩
BitLocker is an incredibly powerful tool for data protection, but losing the password or Recovery Key can have irreversible consequences. Keep your keys secure and always have backups!

💬 Share in the comments how you handled a similar situation or ask questions if you need help! 👇

✨ Your data is valuable – protect it well! ✨