tomovo

You mean removing sense of humour? No thanks. But I can see they work.

Stop bragging, mine fits into a csv file.

The justification by Apple is that it keeps the concentricity between window corner and the red/green/yellow window controls. Which, as you may notice, it does.

It's wrong though, because the window is the higher element in the hierarchy (container) and should not be affected by what is inside. It creates a larger inconsistency than the "consistency" it supposedly brings.

Owning stock?

Sunk cost fallacy. It didn't work out, the decision was made, they move on. I like that.

Now at least parts of it are paged out...

I loved Coffee Run and the BCON24 Identity. Brilliant stuff. When it comes to Blender itself the only regret I have is that they ended support for Intel Macs but I understand it's a burden to support older platforms.

Sadly mac-assedness doesn't automatically mean feature richness or overall robustness. Those are actually quite hard to achieve when you spend half of each year updating the UI widgets to the latest SDK and fixing new performance problems you didn't cause. That should be clear when you compare Affinity Photo and Pixelmator Pro.

Regarding the "searchability" point: I tried using the Google search field on the left to search for "openbao", which is listed right below as one of the topics. Got 0 results. Second time I tried, I got a reCaptcha from Google itself: a first in years. That's not very reassuring.

I guess it depends a lot on the use cases. I've used both the original Pixelmator app and the "Pro" may have been a rewrite internally but it didn't feel like a significant step up for me at the time, more like a rebrand and a way to charge for it again. And so many bugs. The development team did respond to a few of my bug reports, which was nice.

Maybe. Form over function, not a surprise.

It's a pity Apple didn't choose to acquire Affinity when there was a chance. Pixelmator Pro looks like a toy app compared to Logic or Final Cut. I don't see how it could ever catch up to Photoshop. Even at such small scale it's always been very buggy in my experience and development seems to have stalled (apart from some obligatory AI features).

I am glad the standalone purchases are still available and I assume they will stay updated in sync with the subscription-based ones. I would hate my copy of Logic getting slowly obsolete..

I don't see any connection between catching up and being a dead end.

I think Ladybird is becoming more than that. It's actually helping set the web standard specifications straight in many cases and a from-scratch implementation will have its own advantages once it catches up. Which it will. There's no permanent winner as long as the standards are open.

I'm guessing the DisplayPort is there to support the original Valve Index directly.

Yes and the podcast was fun to listen to. Great chance to follow work in progress of an experienced game developer, week by week.

I don't think that's the end of the discussion. Let's try to talk separately about developers and publishers. I'm sure game developers would love to spend time making the game run on everything. But publishers work with a budget and schedule and have to consider the returns. If the potential new customers bring more support load and bad reviews, it's not worth it. That, I think, is the end of the discussion for the publisher.

Now I've got to mention Sublime Merge as my personal favorite: super fast, nice clean UI on all platforms, still maintained, single purchase license.

Are they putting work into the SDK or is there some integration going on? The way I understand it the SDK is compiled straight into Android binaries, whereas Skip transpiles? How does that work together?

If you mean Kotlin Multiplatform, it works pretty well. Not easy to debug, the GC is a bit weaker than the Android implementation and optimized builds can get crazy slow as the app grows. The interface uses auto-generated ObjC headers which are very verbose. Native Swift API is in beta. Overall still worth it for a commercial app, I think.

Yes and any package dealing with UI is automatically disqualified, so 25% really is pretty good.

Not on genuine HP concrete.

Meta-Object Compiler, a sort of preprocessor for code that uses Qt: https://doc.qt.io/qt-6/moc.html

Make sure to keep that <firstname> in the message. This will emphasize how much good human being you are.

"more and more push back"

I think it depends on the circles you're in. For example, I see a lot of interest in the "Handmade" way of doing things, largely inspired by Handmade Hero. Almost feels like a comeback of what you consider to be dying. There are people who are interested, but one needs to look for them. I recommend it.

While I appreciate all his work on LLVM, Chris Lattner's Swift didn't work out so well for me, so I'm cautious about this.

Swift has some nice features. However, the super slow compilation times and cryptic error messages really erase any gains in productivity for me.

- "The compiler is unable to type-check this expression in reasonable time?" On an M3 Pro? What the hell!?

- To find an error in SwiftUI code I sometimes need to comment everything out block by block to narrow it down and find the culprit. We're getting laughs from Kotlin devs.

Does SteamOS count as something Carmack would discourage as well? Yes it's a Linux-based system and yes even based on an existing distro, but it is a purpose-specific OS and it seems like it's working well for Valve and people using it to play Windows games without Windows...

The graph has no units or scale. What is the project size at the crossover point? The article says "certain size" which is unclear.

They need to feed it to all the LLMs to get help keeping it from falling apart.

They could go back to Win32 + WinForms and everything would be fine.

This dramatically reduces memory usage for lists or grids with many items

I'd love to see a specific example with before/after numbers.

Lottie [...] ends up loading every frame as a raw bitmap.

Isn't Lottie rendering the vector data directly to screen?