BrandoDev_it

Thanks for your time, talking with a KDE developer is important to me. The reason for choosing Vulkan was about explicit control over synchronization, resource management and frame scheduling, without having to maintain also OpenGL; even though I don't exclude a software rendering fallback for VMs or something. It wasn't a first-minute choice, I realised it when I wanted to improve performance compared to other DE. Currently I'm developing a benchmark suite, this is not complete yet but I've already found out Vela around 40% lower input-to-display latency in one of my tests (compared to Plasma), apparently thanks to late latching.

Thanks. Fractional scaling was one of the foundation of Vela: it is really one of the reasons why Vela exists. So I thinked about it since the first minute. The issue is of course that something like at 125% with logical coordinates don't always came at actual physical pixels. And even small rounding can cause blurry text. So in Vela fractional scaling works everything in logical coordinates until the rendering stage, then it rounds to physical pixels. If you want to deep dive: https://github.com/vela-desktop/vela/blob/main/docs/renderer...

You're not wrong, but at the same time KDE has to deal with a lot of legacy code from the past. Vela breaks with the past, supporting only Vulkan 1.4

I understand, well Vela integrates good with KDE Apps. I think you should give it a try

I'm sorry currently this is more focused to Desktop computers, ARM is not a priority for early beta

No, this is written in C (the compositor itself) and C++ (parts which talks with QT) However, the naming problem is known and currently there is an issue open (#174)

I can't wait for qwen4 flash next or something like a 150b moe from qwen.

Fable 5 is not anymore frontier and even if, I hardly believe five very small 27b models can do like Fable 5. I think this is whishful thinking more than a fact

Hello, yes I'm aware of this issue and I fixed it. Unfortunately my DNS wasn't correctly configured because I had two different A records with two different ipv4 (only 1 correct) and certificate auto-renewal was trying with the wrong ip. However website is now online again and dns configuration is now correct.

LabWC is definitely not modern

Thanks, I would love to have a honest feedback if you can run it even in a nested session

You can already use Vela as daily especially if you are on an AMD. I'm here if you have any questions

I wrote this post from Vela. Vela is my daily driver since days

I can't wait for a smaller moe dinstillation from this excellent model