开发者

submitted by /u/techzexplore [link] [留言]

submitted by /u/Fcking_Chuck [link] [留言]

The company added a warning to prospective investors that a major dilution could be in the cards after it goes public.

​ Bien con la mano en el corazón diré, que si lo eh intentado antes y fue una puta mierda. No sé si se puede insultar aquí, pero bueno. Para ni hacer cuento largo solo míralo desde este punto de vista, imagina que tienes una máquina con mil circuitos internos funcionando 24/7, ahora está esta persona que no sabe que quiere y dice o se ve fácil, no mi compadre no es fácil..bueno si solo si sabes a dónde apuntas después de eso, no es fácil. Soy humano, el que escribe esto no una IA. submitted by /u/Silent-Preference216 [link] [留言]

If you've spent any time building React Native apps, you've already bumped into the question. You're setting up a new project, you need to move users between screens, and suddenly you're 40 minutes deep in a documentation rabbit hole wondering whether to go with the familiar React Navigation setup or take the leap to Expo Router. This article is going to break it all down, no hype, no fanboy energy, just an honest look at both options so you can make the call that actually fits your project. First, What Does "Routing" Even Mean in a Mobile App? On the web, routing is pretty intuitive. You type a URL, the browser goes to a page. Simple. In mobile apps, there's no URL bar, no browser history button, nothing like that. But users still need to move between screens, go back to where they came from, open modals, tab between sections, and all of that has to feel smooth and natural. So in mobile development, routing is basically the system you use to manage how screens stack on top of each other, how state is preserved when you go back, how deep links work, and how the app knows which screen to show based on where the user is in the flow. Think of it like this: routing is "moving between screens while keeping your app's memory intact." When someone logs in, fills out a form, gets distracted and opens a modal, then comes back, the app should remember all of that. Routing is the machinery underneath that makes it happen. In React Native, this doesn't come out of the box. The framework gives you the building blocks, but you have to wire up the navigation yourself. That's where libraries come in. Why Navigation Is Such a Big Deal in React Native React Native apps are essentially single-page applications. Everything runs in one JavaScript thread, rendered to native views. There's no browser doing the heavy lifting of managing history or transitions. You're responsible for it all. Bad navigation kills good apps. A janky transition, a broken back button, a modal that doesn't dismi