Crash After 10.49.3 Update Due to Missing Framework about realm-swift HOT 6 CLOSED

➤ PM Bot commented:

Jira ticket: RCOCOA-2345

from realm-swift.

embed & sign was not selected. There are, like, 49 other features that have been on-request for years that would be more useful than a privacy manifest. Just saying.

from realm-swift.

I understand that this is how you feel, but the issue regarding the privacy manifest has been especially active with many people chiming in and requesting a solution. Additionally, it's pointless to compare feature requests that would take 6 months to those that take less than a week. At the end of the day, we prioritize our work based on user feedback, business needs, and complexity. Even if a feature is highly requested but would take us a year to complete and there are hardly any paying customers asking for it, that would be lower priority than something that's quick to do and would unblock someone paying for Atlas.

from realm-swift.

@nirinchev I do pay for Atlas. I pay a lot for Atlas. And six months is nothing--there's very basic requests that have been open for ten years on Realm.

Fundamentally, there seems to be a disconnect between what the team sees as priorities and what developers using the SDK see as priorities.

More broadly, that might explain why MongoDB has been declining in popularity over the last few years and why Postgres is ascendant.

from realm-swift.

I don't believe there's such a disconnect, but obviously you're entitled to feel differently. While we may not be working on the features you want us to work on, we're addressing requests that the community has asked for and is benefitting from.

Six months of development time is significant and it's not like the team has been sitting on their hands for 10 years - we've shipped continuous improvements and allocated resources to the best of our abilities. Have we gotten everything right - surely not, but I fundamentally disagree with the notion that there are basic requests that have been open for 10 years. While on the surface it may seem simple like "add support for case-insensitive sorting", the technical aspects of it are complicated and the cost/benefit tradeoff hasn't justified prioritizing this over other functionality we've worked on.

I understand your frustration and appreciate the feedback, but don't appreciate the way it's delivered. Denigrating the team or the product is not going to make us ship features faster and is not conductive to productive collaboration.

from realm-swift.

@nirinchev I'm not denigrating the team. Do not assign malice where none is intended--leave that for Gen Z. I do appreciate the challenges involved in creating Realm and recognize that it's a complex project.

But, to use your example, there seems to be little recognition that Alice, Bob, amy is a nonsensical sort order. The team has dismissed that for 10 years and developers have had to (silently) work around the limitation. That silence has perhaps mislead the Realm team into thinking these sorts of shortcomings aren't a big deal. I'm not sure we (the SDK users) have done an adequate job of providing feedback.

I do admit that I was a little piqued when I fired off that original comment. A client discovered the bad sort order in an app I build for them and asked me why "allen" was listed after "Susan". I wasted a ton of time investigating only to discover it's another longstanding problem with Realm. To the client, I just look like an incompetent developer and I have to explain a bunch of technical mumbojumbo about databases and query engines.

from realm-swift.