This sounds like the inevitable slow death of RN to me. Web developers simply moving on to new tech that's better/more common on the web while RN languishes as the massive set of open source libraries required are abandoned
+1, this system should be improved with a topic based subscription so individuals can opt-in/out of lower level alerts, but keep the ability for local governments to blast everyone in an area for emergencies
Reliable and fast push notifications from trusted accounts are the critical piece of infrastructure that needs a public option. Something less than the existing emergency alert systems that allows for individuals to subscribe to and is easier for local governments to onboard to.
What I don't understand is why the VFX industry doesn't follow market dynamics and pay the artists what they are worth given the talent shortage. Or maybe they are and that story isn't getting told?
React Native follows this pattern by moving most JS processing off the main thread allowing scrolling and other input to happen without blocking for a response from the JS VM. However this does end up causing a lot of problems with text input and gestures as now you have a sync issue between the threads, if you get caught processing a bunch of stuff in the JS thread the app may appear to be responsive with scrolling but nothing happens in response to button taps or text insertion. It is the only way RN was going to work on lower end hardware though so probably is the right solution if you assume running react everywhere is a good idea.
Columns are LWW (last writer wins) registers within rows which are LWW maps. When concurrent writes occur because peers may not be communicating, there is typically an arbitrary but convergent selection based on peer id.
* More generally, frameworks like RN and Flutter are a good choice if your app doesn't need extensive/precise/efficient access to native platform features and a bad choice if it does
+1, if you only ever do superficial platform features RN isn't a problem. However if you want to implement the platform features, like Widgets, Siri/Shortcuts support, Apple Watch support, Spotlight search integration now you're going to start having to maintain extensive bridges to communicate between native and JS.
> With JSI now you can get efficient access to native platform features. Before you were able to bridge pretty much any native feature with a native view or extension, but you were bottlenecked by the JS bridge. Nowadays you can use JSI for anything intensive.
JSI indeed makes things more efficient, but you still have to maintain code to translate between native and JS.
Third, I just took the class as well and the forums on piazza are also a great resource. They went live when the class started and the community was very helpful for a beginner. There are still some active people there so check it out.
I'm an iOS developer with a similar amount of experience. I'm based out of a small city in Georgia which has no developer community so its very hard to stay motivated and keep challenging myself. Glad to hear you got a job, mind me asking what your process was for finding it?