PeyTy

Greentea OS: Brew Code, Run .exe, Join the Vibe

Greentea OS is an alpha-stage, GPL3 desktop OS from scratch that boots from zero to Solitaire**.exe** in 2s+ on an average laptop.

Hey there, fellow programmer! I'm PeyTy, the guy who kicked off Greentea OS back in 2016. It started as a vision: what if we built an open source OS that runs .exe files like Windows, but feels like sipping a warm cup of green tea?

Or maybe like something that has a decent, fully GPU-accelerated compositor at 240 fps GUI, yet offers infinite backwards compatibility and speaks of software preservation without blinking?

Fast forward to July 2025, and we're in alpha — running apps like Solitaire, Minesweeper (including the very original XP version!) and a Calculator with a slick, as cozy as you want GUI. Now, we need you to help us brew something truly epic.

PeyTy

Legal Ambiguity

The reverse engineering (when involved) should occur under the relevant laws, to avoid any ambiguity and "religious" understanding of the reverse engineering approaches: some community members of other projects tend to abuse the "ideological superiority" of the chosen project, by bending, obscuring and twisting the processes.

Examples are notable comments by project leaders like Alexandre Julliard citation "You should not look at ReactOS code at all, a lot of it is reverse-engineered using methods that are not appropriate for Wine. It's not a usable source of information for us." - source https://bugs.winehq.org/show_bug.cgi?id=50464#c6

Such comments, historically, speaking from the shared experience of multiple contributors, tend to create a harsh "us vs them" environment for everyone, implying that the "other" project is somehow "bad by default" because it "does not follow" some obscure, unclear, never fully specified rules (even when it's completely unintentional and the rule authors a

PeyTy

Title: "The Great Kernel Clash: Rusty Revolutions & Linus’s Last Stand"

In a plot twist no one saw coming (except everyone), the Linux kernel community has been rocked by a spicy drama involving Asahi Lina (a.k.a. the GPU sorceress), Linus Torvalds (the kernel’s grumpy grandpa), and a programming language so hipster it makes avocado toast look basic: Rust.

---

Act 1: The Rise of the Rust Crusader

Asahi Lina, famed for reverse-engineering Apple’s M1 GPU using Python scripts and sheer audacity , decided to write the world’s first Rust-based GPU driver for Linux. Why? Because manually debugging C code’s segfaults was too mainstream. “Rust’s like a helicopter parent,” she declared. “It won’t let you forget to initialize variables, even if you’re literally rendering a spinning cube in the kernel!” .

But not everyone was thrilled. When Lina tried to merge her Rust driver, Christoph Hellwig, a C-ode traditionalist with 20+ years of kernel cred, blocked the patch,

PeyTy

I'm pretty sure people would ask me about this.

Why not create a yet another Linux distro?

My personal experience covers:

• Ubuntu 12.04 LTS and newer releases since then
• ArchLinux (Antergos)
• Kubuntu
• Puppy

PeyTy

Hi! This is my idea about the feature I want to add into my own language Hexa* and especially Zig** (because it fits Zig very well!).

* not promoting Hexa here, really want Zig to fight Rust "monopoly" on safe memory management

** very unlikely that I will implement it myself, hopefully someone will be yakbaited

I was evaluating usage of Zig for my projects and never liked the absence of any assisted memory managemnt (defer is not really a solution to complex memory issues but it doesn't matter on the subject) (and Rust is too annoying to deal with).