@Berke

Guys I just made the a meme for my project :)

𝐝𝐞𝐯𝐥𝐨𝐠 𝐯𝟎.𝟏.𝟑

𝐡𝐞𝐲 𝐞𝐯𝐞𝐫𝐲𝐨𝐧𝐞, 𝐛𝐞𝐫𝐤𝐞 𝐡𝐞𝐫𝐞. 𝐛𝐢𝐨𝐬𝐚𝐤𝐚 𝐯𝟎.𝟏.𝟑 𝐢𝐬 𝐨𝐮𝐭. 𝐭𝐡𝐢𝐫𝐝 𝐢𝐭𝐞𝐫𝐚𝐭𝐢𝐨𝐧, 𝐬𝐚𝐦𝐞 𝐟𝐨𝐮𝐧𝐝𝐚𝐭𝐢𝐨𝐧, 𝐛𝐞𝐭𝐭𝐞𝐫 𝐞𝐯𝐞𝐫𝐲 𝐭𝐢𝐦𝐞.

𝐖𝐇𝐀𝐓 𝐂𝐇𝐀𝐍𝐆𝐄𝐃 𝐒𝐈𝐍𝐂𝐄 𝟎.𝟏.𝟎

𝐁𝐑𝐀𝐈𝐍 𝐇𝐄𝐌𝐈𝐒𝐏𝐇𝐄𝐑𝐄𝐒.
𝐀𝐥𝐥 𝟑𝟎𝟕 𝐧𝐞𝐮𝐫𝐨𝐧𝐬 𝐧𝐨𝐰 𝐟𝐨𝐫𝐦 𝐭𝐰𝐨 𝐥𝐨𝐛𝐞𝐬 𝐥𝐢𝐤𝐞 𝐚 𝐫𝐞𝐚𝐥 𝐛𝐫𝐚𝐢𝐧. 𝐑𝐢𝐠𝐡𝐭 𝐡𝐞𝐦𝐢𝐬𝐩𝐡𝐞𝐫𝐞, 𝐥𝐞𝐟𝐭 𝐡𝐞𝐦𝐢𝐬𝐩𝐡𝐞𝐫𝐞, 𝐭𝐢𝐠𝐡𝐭 𝐛𝐮𝐧𝐝𝐥𝐞 𝐢𝐧 𝐭𝐡𝐞 𝐦𝐢𝐝𝐝𝐥𝐞.

𝐍𝐄𝐔𝐑𝐎𝐍𝐒 𝐆𝐋𝐎𝐖 𝐎𝐍 𝐅𝐈𝐑𝐄.
𝐂𝐨𝐥𝐨𝐫 𝐜𝐨𝐝𝐞𝐝: 𝐲𝐞𝐥𝐥𝐨𝐰 (𝐟𝐢𝐫𝐢𝐧𝐠) > 𝐠𝐫𝐞𝐞𝐧 > 𝐜𝐲𝐚𝐧 > 𝐛𝐥𝐮𝐞 > 𝐠𝐫𝐚𝐲 (𝐢𝐧𝐚𝐜𝐭𝐢𝐯𝐞). 𝟓 𝐭𝐢𝐞𝐫𝐬 𝐨𝐟 𝐚𝐜𝐭𝐢𝐯𝐢𝐭𝐲.

𝐋𝐈𝐕𝐄 𝐆𝐑𝐎𝐔𝐏𝐒 𝐏𝐀𝐍𝐄𝐋.
𝐒𝐄𝐍 / 𝐌𝐎𝐓 / 𝐈𝐍𝐓 𝐚𝐜𝐭𝐢𝐯𝐢𝐭𝐲 𝐛𝐚𝐫𝐬 𝐰𝐢𝐭𝐡 𝐚𝐜𝐭𝐢𝐯𝐞 𝐜𝐨𝐮𝐧𝐭𝐬 𝐚𝐧𝐝 𝐟𝐢𝐫𝐢𝐧𝐠 𝐫𝐚𝐭𝐞𝐬. 𝐑𝐞𝐚𝐥-𝐭𝐢𝐦𝐞.

𝐖𝐎𝐑𝐌 𝐕𝐈𝐄𝐖 𝐎𝐕𝐄𝐑𝐇𝐀𝐔𝐋𝐄𝐃.
𝐆𝐫𝐚𝐝𝐢𝐞𝐧𝐭 𝐛𝐨𝐝𝐲, 𝐥𝐢𝐯𝐞 𝐦𝐨𝐭𝐨𝐫 𝐛𝐚𝐫𝐬, 𝐬𝐩𝐞𝐞𝐝 𝐚𝐧𝐝 𝐩𝐡𝐚𝐬𝐞 𝐫𝐞𝐚𝐝𝐨𝐮𝐭. 𝐀𝐜𝐭𝐮𝐚𝐥𝐥𝐲 𝐜𝐫𝐚𝐰𝐥𝐬 𝐧𝐨𝐰, 𝐝𝐨𝐞𝐬𝐧’𝐭 𝐯𝐢𝐛𝐫𝐚𝐭𝐞.

𝐅𝐎𝐑𝐂𝐄-𝐃𝐈𝐑𝐄𝐂𝐓𝐄𝐃 𝐋𝐀𝐘𝐎𝐔𝐓.
𝐏𝐫𝐞𝐬𝐬 [𝐟] 𝐭𝐨 𝐭𝐨𝐠𝐠𝐥𝐞 𝐅𝐫𝐮𝐜𝐡𝐭𝐞𝐫𝐦𝐚𝐧-𝐑𝐞𝐢𝐧𝐠𝐨𝐥𝐝. 𝐀𝐥𝐥 𝟑𝟎𝟕 𝐧𝐞𝐮𝐫𝐨𝐧𝐬 𝐫𝐞𝐚𝐫𝐫𝐚𝐧𝐠𝐞 𝐛𝐲 𝐫𝐞𝐚𝐥 𝐬𝐲𝐧𝐚𝐩𝐭𝐢𝐜 𝐜𝐨𝐧𝐧𝐞𝐜𝐭𝐢𝐨𝐧𝐬. 𝐀𝐜𝐭𝐢𝐯𝐞 𝐜𝐥𝐮𝐬𝐭𝐞𝐫𝐬 𝐜𝐥𝐮𝐬𝐭𝐞𝐫. 𝐈𝐬𝐨𝐥𝐚𝐭𝐞𝐝 𝐠𝐫𝐨𝐮𝐩𝐬 𝐝𝐫𝐢𝐟𝐭.

𝐍𝐄𝐔𝐑𝐎𝐍 𝐋𝐀𝐁𝐄𝐋𝐒.
𝐓𝐨𝐩 𝟖 𝐦𝐨𝐬𝐭 𝐚𝐜𝐭𝐢𝐯𝐞 𝐧𝐞𝐮𝐫𝐨𝐧𝐬 𝐬𝐡𝐨𝐰 𝐭𝐡𝐞𝐢𝐫 𝐧𝐚𝐦𝐞𝐬 𝐫𝐢𝐠𝐡𝐭 𝐨𝐧 𝐭𝐡𝐞 𝐠𝐫𝐚𝐩𝐡.

𝐇𝐄𝐋𝐏 𝐎𝐕𝐄𝐑𝐋𝐀𝐘.
𝐏𝐫𝐞𝐬𝐬 [𝐡], 𝐞𝐯𝐞𝐫𝐲 𝐜𝐨𝐧𝐭𝐫𝐨𝐥 𝐥𝐢𝐬𝐭𝐞𝐝. 𝐍𝐨 𝐦𝐞𝐦𝐨𝐫𝐢𝐳𝐚𝐭𝐢𝐨𝐧.

𝟓 𝐓𝐀𝐁𝐒.
[𝟏] 𝐆𝐫𝐚𝐩𝐡 | [𝟐] 𝐖𝐨𝐫𝐦 | [𝟑] 𝐒𝐭𝐚𝐭𝐬 | [𝐂] 𝐂𝐫𝐞𝐝𝐢𝐭𝐬 | [𝐈] 𝐈𝐧𝐟𝐨 (𝐬𝐜𝐫𝐨𝐥𝐥𝐚𝐛𝐥𝐞 𝐭𝐞𝐜𝐡 𝐝𝐨𝐜)

𝐈𝐍𝐓𝐄𝐑𝐀𝐂𝐓𝐈𝐕𝐄 𝐒𝐓𝐈𝐌𝐔𝐋𝐀𝐓𝐈𝐎𝐍.
[𝐣] 𝐩𝐨𝐤𝐞 𝐀𝐒𝐄𝐋 | [𝐤] 𝐩𝐨𝐤𝐞 𝐀𝐒𝐄𝐑 | [𝐮] 𝐩𝐨𝐤𝐞 𝐀𝐖𝐀𝐋 | [𝐨] 𝐩𝐨𝐤𝐞 𝐀𝐖𝐀𝐑.
[𝐩] 𝐭𝐨𝐠𝐠𝐥𝐞𝐬 𝐚𝐮𝐭𝐨-𝐬𝐭𝐢𝐦. 𝐇𝐞𝐚𝐝𝐞𝐫 𝐬𝐡𝐨𝐰𝐬 𝐥𝐢𝐯𝐞 𝐲𝐞𝐥𝐥𝐨𝐰 𝐟𝐞𝐞𝐝𝐛𝐚𝐜𝐤.

𝐎𝐍 𝐀𝐔𝐑.
𝐲𝐚𝐲 -𝐒 𝐛𝐢𝐨𝐬𝐚𝐤𝐚. 𝐁𝐚𝐬𝐡 𝐜𝐨𝐦𝐩𝐥𝐞𝐭𝐢𝐨𝐧 𝐢𝐧𝐜𝐥𝐮𝐝𝐞𝐝.

𝐎𝐍 𝐂𝐑𝐀𝐓𝐄𝐒.𝐈𝐎.
𝐜𝐚𝐫𝐠𝐨 𝐢𝐧𝐬𝐭𝐚𝐥𝐥 𝐛𝐢𝐨𝐬𝐚𝐤𝐚.

~𝟓𝟎𝟎 𝐋𝐈𝐍𝐄𝐒 𝐎𝐅 𝐑𝐔𝐒𝐓.
𝟒 𝐦𝐨𝐝𝐮𝐥𝐞𝐬. 𝐙𝐞𝐫𝐨 𝐠𝐞𝐧𝐞𝐫𝐚𝐭𝐞𝐝 𝐜𝐨𝐝𝐞. 𝐄𝐯𝐞𝐫𝐲 𝐥𝐢𝐧𝐞 𝐡𝐚𝐧𝐝𝐰𝐫𝐢𝐭𝐭𝐞𝐧.

𝐑𝐎𝐀𝐃 𝐀𝐇𝐄𝐀𝐃

𝐧𝐞𝐮𝐫𝐨𝐭𝐫𝐚𝐧𝐬𝐦𝐢𝐭𝐭𝐞𝐫𝐬 (𝐆𝐀𝐁𝐀/𝐠𝐥𝐮𝐭𝐚𝐦𝐚𝐭𝐞) . 𝐬𝐩𝐞𝐞𝐝 𝐜𝐨𝐧𝐭𝐫𝐨𝐥 . 𝐦𝐮𝐬𝐜𝐥𝐞 𝐩𝐡𝐲𝐬𝐢𝐜𝐬 . 𝐝𝐫𝐨𝐬𝐨𝐩𝐡𝐢𝐥𝐚 (𝟏𝟎𝟎𝐤 𝐧𝐞𝐮𝐫𝐨𝐧𝐬) . 𝐦𝐮𝐭𝐚𝐭𝐢𝐨𝐧 . 𝐫𝐞𝐜𝐨𝐫𝐝/𝐩𝐥𝐚𝐲𝐛𝐚𝐜𝐤 . 𝐦𝐚𝐥𝐞 𝐜𝐨𝐧𝐧𝐞𝐜𝐭𝐨𝐦𝐞 . 𝐧𝐞𝐮𝐫𝐨𝐧 𝐬𝐞𝐚𝐫𝐜𝐡 . 𝐇𝐞𝐛𝐛𝐢𝐚𝐧 𝐥𝐞𝐚𝐫𝐧𝐢𝐧𝐠 . 𝐨𝐩𝐭𝐨𝐠𝐞𝐧𝐞𝐭𝐢𝐜𝐬 . 𝐩𝐚𝐫𝐚𝐦𝐞𝐭𝐞𝐫 𝐭𝐮𝐧𝐢𝐧𝐠 . 𝐧𝐞𝐭𝐰𝐨𝐫𝐤 𝐦𝐞𝐭𝐫𝐢𝐜𝐬 . 𝐦𝐮𝐥𝐭𝐢-𝐰𝐨𝐫𝐦

𝐖𝐇𝐄𝐑𝐄

𝐆𝐢𝐭𝐇𝐮𝐛: 𝐠𝐢𝐭𝐡𝐮𝐛.𝐜𝐨𝐦/𝐁𝐞𝐫𝐤𝐞𝐎𝐫𝐮𝐜/𝐛𝐢𝐨𝐬𝐚𝐤𝐚
𝐀𝐔𝐑: 𝐚𝐮𝐫.𝐚𝐫𝐜𝐡𝐥𝐢𝐧𝐮𝐱.𝐨𝐫𝐠/𝐩𝐚𝐜𝐤𝐚𝐠𝐞𝐬/𝐛𝐢𝐨𝐬𝐚𝐤𝐚
𝐜𝐫𝐚𝐭𝐞𝐬.𝐢𝐨: 𝐜𝐫𝐚𝐭𝐞𝐬.𝐢𝐨/𝐜𝐫𝐚𝐭𝐞𝐬/𝐛𝐢𝐨𝐬𝐚𝐤𝐚

𝐬𝐭𝐚𝐧𝐝 𝐫𝐞𝐚𝐝𝐲 𝐟𝐨𝐫 𝐦𝐲 𝐚𝐫𝐫𝐢𝐯𝐚𝐥 𝐰𝐨𝐫𝐦

𝐛𝐞𝐫𝐤𝐞, 𝟐𝟎𝟐𝟔

—> Stardence Devlog. BioSaka v0.1

“Stand ready for my arrival, worm.”

I made a worm brain using Rust. It runs in a terminal.

The BioSaka worm brain has 307 neurons and 2800 synapses.

These numbers come from the real worm connectome.

Some people like White and his team spent years studying a worm under a microscope.

They made 8000 pictures of the worm.

I used those pictures to make my BioSaka worm brain.

It only took me a weekend to do this.

The BioSaka simulation uses something called LIF neurons.

This means that every time the clock ticks the neurons lose some power the synapses fire and the gap junctions connect.

The BioSaka worm body also moves a bit.

The graph that shows what is happening also lights up.

It is like a world inside the terminal window.

I used ratatui to make the user interface for BioSaka.

I used crossterm to handle the keyboard for BioSaka.

I used rand to add some noise to BioSaka.

The connectome data for BioSaka is added to the program when I build it.

This means that BioSaka does not need to read any files when it is running.

It just does the calculations.

The hardest part of making BioSaka was getting the worm to look like it is really moving.

It had to look like it was crawling and not just shaking.

I had to use a kind of wave to make this happen.

This wave is called a wave and it has something called phase propagation.

Stand ready, for my arrival, worm.

— berke, 2026

Bros OS Devlog #1 – 4 Years, 95k Lines, and a Filesystem Named After My Girlfriend

So here’s the thing. Four years ago I sat down and thought, ‘Yeah, I’ll just write my own operating system.’ You know, casually. Like one does. Fast forward to today: I’m knee-deep in 95,122 lines of Rust, running my own kernel on a custom CPU I named BROS HM-1 (2 cores @ 2.4 GHz, because why not), booting with my own fork of GRUB, and managing files on a filesystem named after my girlfriend. It’s been a ride. This is Bros OS v1.1.2C – a proprietary x86_64 operating system built from scratch in Rust (no_std). And yeah, it’s closed source. I’ll get to why.

The BerkeOS -> Bros OS Story
Originally this was BerkeOS on GitHub. People started stealing the repo – cloning it, stripping the credits, and passing it off as their own work. Happened more than once. So I pulled it down and took everything private. That’s really the only reason Bros OS is closed source. Not because I’m a gatekeeper, but because a few bad actors ruined it for everyone. The code’s still alive, still growing – just on my machine now. There’s also a pending Turkish patent application covering the filesystem and boot process.

What’s Actually In This Thing?
Monolithic kernel, 513 Rust source files, no_std bare metal. Brosh shell – 185+ commands, pipes, redirection, job control. You can almost forget you’re not in bash. Almost. DefneFS v3.2.3 – custom FS with ATA PIO, AHCI, NVMe, SATA. Full partition manager, VFS layer, disk quotas. Drives: Alpha://, Beta://, Gamma://. Full network stack – TCP/IP, UDP, ICMP, ARP, DHCP, DNS, HTTP, NAT, routing, tunneling. All hand-written. Modular graphics – VGA, framebuffer, VESA, double buffering, font rendering, BMP image support. Retro aesthetic, fully intentional. USB XHCI driver – works on real hardware. Plug in a keyboard and it just works. Virtual memory, ELF loader, SMP, ACPI, crypto (AES128/SHA256/MD5), crash dumps, cron/at scheduler, init system, Deno text editor.

BAHAR Bootloader
I forked GRUB2 – the entire thing – just to change one line of code. Somewhere deep in grub-core/kern/main.c, I swapped ‘Welcome to GRUB!’ for ‘Welcome to BAHAR!’. Overengineered? Absolutely. Worth it? 100%. It’s technically a custom bootloader now. Don’t @ me.

DefneFS – Yeah, It’s Named After Her
Defne is my girlfriend. She sat through four years of me yelling at linker errors, celebrating page fault fixes like I won the lottery, and explaining what a context switch is for the 50th time. She never once told me to stop. The filesystem is the heart of any operating system, and she’s the heart of this project. Seemed fair. She genuinely liked the idea too. That helped.

How It Was Built
OS Dev Wiki carried me through the first two years. Absolute goldmine. Rust no_std on bare metal – no allocator, no standard library, no println!. You build everything from the ground up, then rebuild it because you did it wrong the first time. Dev setup: OpenCode (Sisyphus) handles orchestration. Local Ollama serves MiniMax 2.5 and DeepSeek for code gen. About 18,739 lines (19.7%) are mine – hand-written, reviewed, finessed. The rest is AI-assisted but I read every single line before it hit the codebase. Nothing went in on autopilot. Best part about local models: you can retry 50 times without burning API credits. Worst part: prompt engineering becomes a second full-time job.

Four years. 95k lines. One very patient girlfriend. And I feel like I’m just getting started. OS dev is a treadmill that never stops. But honestly? I wouldn’t have it any other way.
– Berke

BROS Operating Systems UI/UX