u/Usual_Importance8274

This is my first time writing a post like this.

I'm not sure if it’s allowed, but I found this project quite useful and wanted to share it with everyone.

Here is my story. About six months ago, I started learning Rust and began building my dream game engine.

The first thing I wrote was an ECS library, followed by a Vulkan backend using ash. After that, I managed to render my first triangle, then my first model, and so on.

I swear that once I got past that point, everything started to get messy.

I realized it wasn't because I didn't understand how Vulkan works or how complex the API is (though there's definitely plenty I still don't know).

Instead, I felt my biggest limitation when working with Vulkan was managing objects, systems, and resources together.

The main cause was the ECS system I had written earlier. It couldn't handle the features required to support Vulkan.

Because of this, I decided to rebuild the ECS library from scratch and do it properly this time.

Specifically, I needed to document it thoroughly. That way, when I look back at it later, I'll know what I did, what I intended to do, and where I can add new features.

Regarding ECS, I’m sure everyone in this group already understands it well, but I feel that sharing this might still help someone else.

That’s why I made a video explaining the reasoning behind ECS and what its true power is.

There is plenty of documentation online, and you can find information everywhere or ask AI to explain it.

But honestly, I remember my first days approaching ECS, back when I only used vectors and dictionaries.

Now that I am rewriting it, I realize that not researching deeply enough and relying too much on AI is never a good thing.

In this video, I tried to highlight the core value of ECS: how a chunk is structured and how it stores data.

Please watch it and share your feedback. I put a lot of hard work into this, but I'm sure there’s something I missed or could improve.

Another interesting thing I realized while making this video is that you have to truly understand a concept to explain it to someone else. I felt pretty good after finishing the video.

After finishing this video, I realized that sharing what I learn while working makes the process much more exciting and keeps my spirits high.

To be honest, I tried to break this project into smaller parts so I could make a video for each one. But truthfully, I’m still not sure what to code next. I think I should start by explaining the Chunk first, as I feel that part is more important than everything else.

Maybe I’m in the wrong profession? Perhaps I should be a YouTuber instead of a Programmer :V

video's link: https://youtu.be/59FW2RnZZzk?si=zxxxyojeLKHQBaJ_

Hi everyone,

I work with audio files quite a lot, and sometimes I just want to quickly play a few of them to test without leaving the editor. So I made a small plugin for it, and I hope it's useful for some of you too.

nvim.sfx_player a tiny floating audio player popup. Open an mp3, wav, flac, ogg, … straight from your file explorer (like nvim-tree) and you get a floating window with the file info and a live, colored timeline you control from the keyboard.

Playback runs on mpv over its JSON IPC socket, so play/pause, seek and volume are real-time and gapless, no restarting a process every time.

A few things it does:

• Floating popup with track metadata (codec, sample rate, channels, bitrate, size, duration)
• Live colored progress bar that follows your colorscheme
• Play / pause, seek, volume, loop toggle, all from the keyboard
• One-line integration with nvim-tree, or just call open()from anywhere
• No orphan processes, mpv is always cleaned up when the popup closes
• Fully configurable: keymaps, colors, default volume, seek step, refresh rate, …

Repo: https://github.com/monok-robeto/nvim.sfx_player