A while ago, a senior person at our company learned through some channels that a certain national-level APP was rejected for three months because Apple App Store reviewers detected React Native hot update content. Our hot update platform has similar principles to the problematic APP, so we also face the risk of rejection. Therefore, we need to think of some ways to hide the hot update bundle and avoid being discovered by reviewers.

Actually, this problem is quite complex because it's not purely a technical issue but also involves various complex commercial interests. Under many constraints, it's difficult to find an optimal solution. Moreover, this issue is quite sensitive, so I can only briefly outline my thinking process. This article will not provide specific code implementations.

Serious declaration: If anyone hides hot update data according to the ideas in this article and the application gets rejected or removed, I will not be responsible.

This article was originally a Zhihu answer, which received good response, so I refined some details and reorganized it for publication

On December 17, 2020, PaperClip Studio launched a new product - "The Birth of an Artificial Intelligence" Interactive Teaching Video. Because I've been exposed to MOOCs since high school and have always been very interested in online education, I immediately followed up and experienced their trial lesson - "Recognizing Numbers".

This article contains some of my insights after studying multiple platform UI frameworks. Due to limitations in energy and technical expertise, there are inevitably shortcomings in this article. Please feel free to provide guidance.

Today let's talk about the practical application of De Morgan's laws in programming. The title looks intimidating, but actually you only need a little bit of high school math knowledge to understand it. Moreover, this knowledge can be quickly applied to projects after mastering it, with a very high investment-return ratio.

React Native as a cross-platform framework has one of the most headache-inducing problems: version updates. Especially when encountering major version updates, the configuration and build files for JavaScript, iOS, and Android all undergo significant changes. Sometimes these configuration files are coupled together, where one change affects everything.

In 2020, if I had to recommend a data collection software for the general public, it would definitely be Houyi Web Scraper. Compared to the web scraper I previously recommended, if web scraper is a small and precise Swiss army knife, then Houyi Web Scraper is a large and comprehensive heavy weapon that can basically solve all data scraping problems.

Let's discuss the excellent features of this software.

Preface​

React Native, as a cross-platform framework, has one of the most headache-inducing problems: version updates. Especially when encountering major version updates, the configuration and build files for JavaScript, iOS, and Android all undergo significant changes. Sometimes these configuration files are coupled together, where one change affects everything.

This article assumes that the person leading the React Native upgrade is a frontend developer who is familiar with JavaScript-based frontend build processes. If conditions permit, it's strongly recommended to involve iOS and Android developers during the upgrade. For some trivial upgrade details, face-to-face communication is far more efficient than search engines.

Tip: Because each modification and new content will hide the article for re-review, it's recommended to read the original blog post for the best reading experience

👉 Read Original Blog Post

If you find this article useful, please remember to like it 🌟. Thank you, it really means a lot to me!

This article is translated from Lydia Hallie's ✋🏼🔥 CS Visualized: CORS. She used many animations to explain the concept of CORS. Since no one has translated this article in China yet, I've translated and corrected some errors based on my understanding of the original text, hoping to help everyone.

The HTTP protocol is arguably the most familiar network protocol for developers. Its characteristics of being "simple and easy to understand" and "easy to extend" have made it the most widely used application-layer protocol.

Despite its many advantages, the protocol specification contains numerous hidden pitfalls due to various compromises and limitations during its definition, which can easily trap unsuspecting developers. This article summarizes common pitfalls in HTTP specifications to help developers consciously avoid them and improve their development experience.