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.
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..
A truly well-designed Mac app is not just form, it is function as well. If you think a good Mac citizen is only what it looks like you're not looking at all.
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.
Your experience couldn't be more different than mine. I love Pixelmator Pro. One of my favorite apps on my computer. Super quick and snappy. Does what I need it to. Which doesn't mean it does what everyone needs it to. I get that it isn't a Photoshop replacement. But not everyone needs a Photoshop replacement.
Your experience is starkly different than mine. Are you sure you aren’t thinking of Pixelmator, Pixelmator Pro’s much more toy-like predecessor from ~10 years ago?
My experience is that while there’s a feature and community gap for both Pixelmator Pro and Affinity, Affinity just tried to copy Photoshop, positioning it as a worse but cheaper Photoshop, while Pixelmator Pro feels like an attempt to make a better photo editor, losing some familiarity points but also being tangibly better than Photoshop at most use cases it can handle, which is many. It’s also an excellent macOS citizen. Between those two factors, it seems much more up Apple’s alley.
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.
Yeah, in my experience, Pixelmator looks the part but isn't a very good software, especially for vectors.
Affinity stuff doesn't look as good but gets much closer to Adobe quality tools.
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.
Ladybird is playing catch-up with features already done years ago. They can either break compatability, or follow. Theyre following, which makes them yet another dead end.
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.
Big fan of sublime merge. I recommend it a lot to people who need to dip their toes in source control and want some layer of abstraction, but also want to feel like they’re connected to the underlying tool (git). Merge balances this very well.
I know a lot of devs hate on Perforce (and I am no exception), but I've grown to actually really like p4merge (the Perforce merge tool) for handling conflicts.
It's a bit of an odd one, and it has a bit of a learning curve, but it's free (as in beer), relatively easy to install, and seems to work well for me. I haven't found a FOSS tool that I like as much yet.
I don't think I've actually used Kdiff3. I always assumed that it was Linux only but apparently I was objectively wrong about that. I should give it a shot.
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.
We use it in my team and it works well enough, but iOS is a bit second class citizen. Everything translates to Obj-C (NSObject at the root), so even something as simple as a data class becomes NSObjects with a cumbersome dev experience rather than a native swift enum.
We're looking forward to native swift export to go stable - it's currently experimental / beta.
The other big problem is debugging. It's impossible to breakpoint kotlin when debugging from swift, so some bugs that are realised only from the swift client side can be tricky and time consuming to fix.
reply