My understanding is that wgpu has a lot of constraints and complexity imposed on it by all the backends it has to support (especially WebGPU) and that Blade is meant to be a much simpler closer-to-metal api for people who want more control (and know how to not shoot themselves in the foot)

> I would be using eframe instead of WGPU as the backend.

Do you mean using egui-wgpu directly rather than through eframe? The default backend of eframe is wgpu (it used to be glow/opengl), and you can still use callbacks to directly render whatever you want with wgpu in an eframe app

> EGUI and WGPU have great integration

Can confirm, it was stupid simple to integrate egui into my wgpu gamedev project

> Am I missing something about Zed? I have tried and failed to get into it.

I also tried Zed after getting annoyed at Helix a few times, and thought "oh cool, this is like vscode but fast and even has a helix mode!" but then didn't find any killer features worth abandoning the synergies of having an all-in-terminal-workflow over

Are there technical reasons that Rust took off and D didn't?

What are some advantages of D over Rust (and vice versa)?

- You can build it into a single binary with no external deps

- The Rust type system + ownership can help you a lot with correctness (e.g. encoding invariants, race conditions)

Yeah, documented *and credited*. I'm not against the idea of disseminating knowledge, and even with my misgivings about LLMs, I wouldn't have said anything if this blog post was simply "LLMs are really useful".

My comment was in response to you essentially saying "all the criticisms of LLMs aren't real, and you should be uncompromisingly proud about using them".

> Moreover there is a strong pattern of the most prolific / known open source developers being NOT against the fact that their code was used for training

I think it's easy to get "echo-chambered" by who you follow online with this, my experience has been the opposite, i don't think it's clear what the reality is.

However, if I was using a more recent/niche/unknown theorem, it would absolutely be considered bad practice not to cite where I got it from.

LLMs are doing this on an industrial scale.

I feel like this wording isn't great when there are many impactful open source programmers who have explicitly stated that they don't want their code used to train these models and licensed their work in a world where LLMs didn't exist. It wasn't their "gift", it was unwillingly taken from them.

> I'm a programmer, and I use automatic programming. The code I generate in this way is mine. My code, my output, my production. I, and you, can be proud.

I've seen LLMs generate code that I have immediately recognized as being copied a from a book or technical blog post I've read before (e.g. exact same semantics, very similar comment structure and variable names). Even if not legally required, crediting where you got ideas and code from is the least you can do. While LLMs just launder code as completely your own.

The HDR experience on KDE is about as good as the Windows one. Last time I tried Gnome, there was no way to configure SDR and HDR brightness separately, but it was definitely still usable.

This time, it's become quickly evident that he is following through.

The sentiment in Europe has changed from "well this isn't ideal, but we can just wait it out" to "this is scary and existential, we need self-sufficiency as soon as possible"

Desktop Linux is (becoming) usable for a normal person just in time, I was surprised how easily a non-technical friend switched over to Bazzite (immutable fedora with gaming extras).

> Visa, Mastercard, Paypal

The EU has already been working on a "Digital Euro" for a while

> all social media commonly used

I'm hoping more decentralized social media continues to pick up steam

Sure x86 is an absolute mess, but I don't think it's a primary bottleneck. High end x86 cpus still beat high end ARM cpus by a significant margin on raw performance. Even supposing x86/ARM are bottlenecks... yeah a bottleneck at double digit billion ops per second.

> Languages unlock performance for the masses. Javascript will never be truly fast because it doesn't represent the machine.

C# and Go are already really fast (https://github.com/ixy-languages/ixy-languages) languages for the masses and at this point you can compile most things to WASM to get them run in the browser.

> The web has complexity also of client/server with long delays and syncing client/server and DOM state, and http protocol. Desktop apps and game engines don’t have these problems.

Hugely multiplayer games consistently update at under 16ms.

From a quick look at various "benchmarks" JpegXL seems just be flat out better than WebP in both compression speed and size, why has there been such reluctance from Chromium to adopt it? Are there WebP benefits I'm missing?

My only experience with WebP has been downloading what is nominally a `.png` file but then being told "WebP is not supported" by some software when I try to open it.

While this true for traditional SDF rendering (e.g. raymarching), the method of "interpolating cached distances" used here means that you will always get blending between objects.