_bent

they just have to implement Vulkan, enough for it to run Dawn or wgpu

Custom mesh normals is huge, because this used to be a PITA.

Tugged away at the end is defining custom cameras through OSL, which is a very very interesting feature, because it allows more physically accurate lens emulation, with dramatically more interesting bokeh than the standard perspective camera model: https://www.reddit.com/r/blender/comments/1kehtse/new_camera...

It definitely does on macOS and I think also on Windows. You have to set the color management for the viewport to Display P3. In older versions this precluded you from using AGX or Filmic, but I think you can actually use AGX with Display P3 now.

they did say "relevant". Though arguably Chromium will probably overthink their decision if both Safari and Firefox support it.

No you have S, M and L cones in your eyes, which represent (roughly) blue, green and red. Your eyes are most sensitive to green and yellow because the spectrum of the M and L cones overlaps. This is why a lot of sRGB is green and why the Bayer pattern has one red, one blue and two green elements. Red, yellow and blue are the primary colors used in art education.

This appears to be very well written and easy to understand even if you only know the basics of digital image encoding.

I found the parts about patching and frames with different blend modes very fascinating. I wonder if it would be possible to build a GUI DCC app that uses JpegXL as its project format. It seems that it could support layers, splines, symbols (transformed instances of layers), blend modes and animations without "baking" any of it to pixels

well there's MIRI

We've had kids accessing an Internet without any working age barriers for over 30 years now.

There have been problems, be that grooming, Facebook parties and maybe addiction to TikTok.

But being able to access adult content be that sexual or violent in nature doesn't really seem to have had much negative consequences.

Sure I wouldn't want my 10 year old to see 2 girls 1 cup - but I reckon it wouldn't be the end of the world if he did.

It's good that we have content recommendations. But we shouldn't try to actually enforce them.

Again: with all the options kids have had for accessing porn online in the last couple of decades, if it was actually THAT bad, we'd be having an epidemic. Yet we don't. The kids are alright

reading through the report, it's not unlikely to be a race condition

most importantly a RAW file hasn't been demosaiced, ie instead of pixels of colors, it's a grid of scalar sensor measurements that, depending on the pattern (eg Bayer) each represent either red, green or blue intensity. since we only know one for each position in the image, the other two have to be interpolated (which is demosaicing)

It's an aquihire

those are layout grids and not grid layout (huge difference!)

It doesn't play to the strengths of designers to have them think in terms of Flex layouts and it doesn't play to the strengths of developers to have them translate a design 100% specified to the layout-algorithm and hierarchy of components into code. Yet this is the workflow Figma encourages.

What the author encourages is that the designers work more free-flowing with sketches and wireframes and that the developers take over earlier to bring that into a workable structure. And that the collaboration between designer and developer doesn't stop at an async hand-off, but that they finalize the design together -- in code.

Some of the commenters here seem to be annoyed at designers that make "hard to implement designs" and therefore think they want designers to constrain everything with auto layout. But this doesn't address the cause of the issue, which is designs being made by designers in isolation, which are then being treated as gospel for developers to 100% match. This is the real problem.

In my opinion the gravest issue with Figma encouraging this workflow is actually the feature gap. Figmas feature set is extremely underpowered in comparison to CSS. Figma doesn't even have grids. If designers are now building stuff only with the tools that Figma allows, all the cool and creative ideas that developers could bring in, because they are actually pretty easy to implement on their platform (the designer just doesn't know about it) will go away.

I can only recommend you this talk by Matthias Ott: https://www.youtube.com/watch?v=1Pq7VqNrtk4

It's a bit frustrating that the footage is first shot, then denoised in post, then renoised in post, then denoised in encoding and then renoised at decoding.

Link to the actual podcast: https://134.209.21.148/public/poll_radio

The result is somewhere between dadaism and a biting satire of the current media landscape and ai hype vapor like notebookllm

The Reddit translations are so insanely terrible. They are so much harder to read the the original English posts. It's like every word has been translated independently

here comes another chinese earthquake ebrrrbrbrrbrrbr

considering the Typst founders are German I wonder if this was one of their concerns with LaTex. Typing \ on QWERTZ is painful

The resolution algorithm is the pubgrub algorithm from Darts package manager pub, implemented in Rust for Cargo https://youtu.be/LGXx5Bqcgq8

Ralf Schumacher?

Windows got worse

where do you see raytracing? it's just reading back the texture of the layer behind a bit distorted. honestly that's cheaper than a blur

Apple does this for iOS 18 via the AccessorySetupKit

yeah slint, which is most similar to Qt

see https://www.boringcactus.com/2025/04/13/2025-survey-of-rust-...

you still can't have multiple windows with flutter, which disqualifies it for building desktop apps.

> a) Ginger Bill (the Odin language creator, no affiliation) stated on a podcast that Odin will never have an official pkg manager

The cognitive dissonance for how one can believe that Rust preventing you from derefercing freed memory at compile time is overzealous nannying by the language authors -- while at the same time deliberately making code reuse harder for users because they could make engineering decisions he doesn't like is staggering.

i got this one recommended in the sidebar https://www.youtube.com/watch?v=Vo6axEMVRcY

iirc the formal correctness of Rusts memory model was proven by Ralf Jung https://research.ralfj.de/thesis.html

How is solving merge conflicts harder than developing an entire browser engine?

Plus Igalia, MS, Mozilla, Brave, Arc, Vivaldi etc could maintain a shared fork that kept stuff like Manifestv2 if they wanted.

They could've just bagged Google's money and spend only as much as necessary on the browser and kept the rest for the future. If Google won't be allowed to pay them for Google Search anymore they'd still have enough money to maintain Firefox for another decade+. Mozilla trying to diversify with services nobody wants is the root of the issue, not the remedy.