The reflog is your friend in situations like that.
Claims top 5 and offers zero evidence and very little content beyond what an LLM might write.
I’m going to sound very negative here and it isn’t because I don’t like open source software. I use it and contribute to it. The problem with OSS apps is that they get cloned by people who don’t care about the license and repackaged with predatory subscriptions or with malware. In the case of malware these lowlifes go out on sites like Fiver and offer to pay unsuspecting developers to distribute the app. If the app is downloaded even once, that developer now faces a lifetime ban from distributing Android apps. I suspect similar things happen on the App Store. It’s just more visible in the Android forums I follow than it is in the iOS ones.
I have seen stories of oss apps being cloned and then Apple mistakenly not letting the original dev upload updates because the app has been flagged in their system as being a spam app or built from a template. This is usually correctable with enough email to support.
My recommendation is to keep your app closed source on both platforms. If you want to contribute to the communities, release a library or contribute to one. If you want to show How to write an app, make something minimal and trivial like a todo list. You can also create a blog.
I would guess that it has more to do with the Amazon App Store. The catalog is not very big and just a fraction of what the Play Store is.
Baking recipes should be in weights for any dry ingredient. Converting them to volume measurements produces inaccurate results. One person may pack the flour in harder than the next. However baking requires precise ratios to be right. Change the ratios too much and that bread recipe just became a cookie recipe.
I read his book “Extraterrestrial: The First Sign of Intelligent Life Beyond Earth” about Oumuamua. https://en.wikipedia.org/wiki/%CA%BBOumuamua it was well thought out and examines the object from many angles. He never says it was aliens. He only says that everything we know about it says it isn’t natural and could be aliens. He does say that it passed through so quickly that we really didn’t get a great look at the object and have to make some guesses about it based on observations.
Prior to sealed classes, I wished they were more like swift enums that could carry dynamic data and have different associated types per case. Now if I want that, I can do that with a sealed class. It’s still nice to have smarter enums if I need a little extra smarts and want to keep the logic close to the enum.
Maybe the code generator? I have no idea. It seems like there shouldn’t be an issue.
It works fine for me. Does your phone trust the computer? Did Xcode properly prepare the phone for development? Developer mode must also be turned on in the phone’s settings. It’s under privacy and security.
I find zipline to be interesting and so is the companion project treehouse. My main problem would be basing an application off of it at any company that isn't CashApp. If I start using a 3rd party open source dependency I always consider how vital it is and how comfortable I would be trying to maintain and support it if the creators decided to abandon it. That or how easy would it be to switch to something similar. It just feels risky but I do like reading about it from the sidelines.
Fellow American here, I definitely read it the wrong way.
I think the responder means that duplicate code is usually easy to refactor into single methods. Typically I see copy pasted code that is changed just a little bit. However much of a duplicated function can be broken into smaller functions and the redundant code removed in favor of calling into the functions. Often what is left then becomes easier to reason about and refactor accordingly. I love the PRs that I make which delete more code than I add but still manage to add functionality. It doesn’t happen often but it’s fun when it does.