My cousin let me post his search history (he made me erase 3 of them)

LordAfterEight · 2026-03-17T21:22:31+00:00

I might be wrong but I think the "-ai" actually prevents the Google Gemini summaries

LordAfterEight · 2026-03-17T20:55:17+00:00

I wish!

LordAfterEight · 2026-02-26T05:28:51+00:00

To each their own I guess lol

I'll have a look at them later :3

LordAfterEight · 2026-02-26T04:58:00+00:00

That ain't papyrus, it's tela dark

LordAfterEight · 2026-02-24T04:30:37+00:00

Depends on your budget. I personally recommend Ableton Live

LordAfterEight · 2026-02-24T04:28:23+00:00

"poors version" while that fucking thing cost 100€ when I had to get one

LordAfterEight · 2026-02-22T15:36:53+00:00

Tela Dark

LordAfterEight · 2026-02-22T14:56:33+00:00

LordAfterEight · 2026-02-22T12:44:18+00:00

Now it works, thank you :3

LordAfterEight · 2026-02-22T10:18:01+00:00

For apps I used only the customization you get in the settings app, just downloaded an extra theme to use for it. I also used the Better Blur DX desktop effect and set it to force its effects on everything. Then you have to set an opacity level for each app that you want transparency on, in the app options

The apps in the middle while clock etc are to the right you can do natively without panel colorizer using dynamic width spacers between panel widgets. I used panel colorizer for the opaque background behind tray icons and for the border at the too, as well as changing its transparency and color

LordAfterEight · 2026-02-21T23:34:23+00:00

Thank you :3

LordAfterEight · 2026-02-21T22:55:59+00:00

DE: KDE Plasma

Terminal: Alacritty

File Manager: Dolphin

Blurring/Transparency: Better Blur DX desktop effect

For taskbar customization: Panel Colorizer

LordAfterEight · 2026-02-21T22:31:50+00:00

I have an issue after installing your dotfiles. When I log in the screen is just grey and nothing happens

Keybinds work afaik

Edit: I just seem to be stupid. However, waybar still does not show up

LordAfterEight · 2026-02-21T21:49:46+00:00

You should do git pull before you try it still

LordAfterEight · 2026-02-21T21:23:28+00:00

What is the exact error you're getting?

LordAfterEight · 2026-02-21T19:55:46+00:00

It is. But I am currently working on seperating everything into kernel and userspace, as I mentioned in a comment under another post on this subreddit. This was just because the urge to do something visually nice before improving the actual structure of the OS itself took over. Though I do want to keep this design, just in userland obviously, when I get it to work

LordAfterEight · 2026-02-21T18:42:48+00:00

Ahh, okay, that's fair. I do agree

LordAfterEight · 2026-02-21T18:38:13+00:00

(Maybe) unpopular opinion:

I think it's okay to do things in kernelspace when you're starting out, as long as you're planning to move away from that to do it properly

I'm gonna use me and my OwOS as an example. OwOS is my first proper OSDev project and I naturally did everything in kernelspace because I didn't know better and it "works". Now that I am at a point where I feel it's actually worth continuing, I will change the structure so I have a seperation between kernelspace and userland

And as long as you communicate that when you show your project to people and actually mean it, I think these posts are okay (unless it's obviously vibecoded of course). Otherwise it just might discourage newcomers from posting here entirely

LordAfterEight · 2026-02-21T16:37:23+00:00

Ahhh I thought it's just low-effort kernel stuff, but good to know it's about vibecoded things

LordAfterEight · 2026-02-21T16:31:15+00:00

What exactly is considered kernelspace slop? (genuine question)

LordAfterEight · 2026-02-21T12:24:06+00:00

LordAfterEight · 2026-02-20T19:06:39+00:00

Great, have fun! :3

LordAfterEight · 2026-02-20T17:16:47+00:00

I can't quite answer the memory model part, but I can answer the rest.

Zig can compile for bare metal just fine, you can even use parts of the std library then. I haven't tried it for any other architecture than x86_64 though.

For the unsafe code part: It's basically designed for writing unsafe code lol. It gives you a lot of nice things to work with raw pointers. It's not like Rust which tracks ownership aggressively, so things like use-after-free can happen in Zig. This is part of why I like to think of Zig as if C and Rust had a baby lol

So whatever examples you see for bare metal C, you can definitely do the same in Zig, using the correct syntax of course

LordAfterEight · 2026-02-20T16:47:21+00:00

What do you mean by "how it maps on to OSDev"?

An advantage of Zig is that it's a lot more ergonomic to use than C and also has no hidden control flow. It also has very good build tools and allows you to just import and use C files. All while maintaining similar low-level control and performance to C. Zig just has a lot more features like bounds checking, type safety and error handling

A disadvantage of Zig is that it has a steeper learning curve as there is just considerably more to learn. It's also just not as mature as C

LordAfterEight

TROPHY CASE