u/kernel-236

[Rice] Just finished my first rice (core at least) now preparing for Hyprland’s Lua migration

Hey everyone,

I recently finished my first rice, at least the core of it. It’s been a great learning experience that forced me to understand the graphical stack much better and how all the pieces fit together.
In the meantime, knowing about Hyprland’s upcoming migration from its proprietary config format to Lua, I started studying the language a few weeks ago. I’ve covered the basics: syntax, tables (and how to use them for data structures), metatables and metamethods and a bit of how C API binding works. Nothing advanced, but enough to feel ready for something practical.
My goal now is to start converting my configs before it becomes mandatory.

I’d love to hear from anyone who’s already started the migration or knows Lua well in similar contexts:
Any common mistakes when translating declarative configs into Lua?
Is it worth modularizing with require from the start, or keep it all in one file initially?
Any patterns or conventions you found useful (e.g. clean keybind management, handling multiple monitors)?
Resources beyond the official docs?

Thanks in advance for any feedback and suggestion!​

reddit.com
u/kernel-236 — 3 days ago

Hi everyone,

I wanted to open a discussion about how people here structure their R projects for clinical/research analyses, especially for prospective and retrospective studies.

In my last project I started using the {targets} package (tar_make(), pipelines, dependency tracking, reproducibility, etc) and honestly it was probably the cleanest project architecture I've ever had. It made the workflow much easier to maintain and rerun without manually tracking which scripts depended on others.

With this package, I really liked the idea of treating the analysis as a pipeline rather than a collection of disconnected scripts.

Now I'm curious how other people here organize their projects: Do you have a personal framework/template you reuse? How do you avoid "script spaghetti" as project grow?

Would love to hear how more experienced users structure their workflow and what practices ended up scaling well over time

reddit.com
u/kernel-236 — 7 days ago
▲ 54 r/hyprland+2 crossposts

After installing Arch from scratch on bare metal, I finally put together my first full setup.

Everything was chosen and configured manually step by step.

Main and almost only components:

WM: Hyprland (Wayland)

Bar: Waybar with some simple custom css

Launcher: Rofi

Terminal: Kitty

File manager: Dolphin

Lock: Hyprlock

I am still refining keybinds and workflow, but it finally feels like my system.

I know many of the "polished" elements are still missing but I can feel the workflow starting become consistent across all the pieces I configured, and that's been the most rewarding part so far.

I am now looking for ideas on useful apps to integrate into my system (especially things like todo apps calendars, or anything that improves daily usability on Wayland)

Really appreciate feedback or suggestion on what to improve or implement next.

u/kernel-236 — 14 days ago