Andrius Janauskas on React native developmentLead Software Engineer @ Qoorio
One of the challenges with react native development is dealing with current architecture of communicating between JS and native threads. This talk by one of the react native engineers gives insight into new architecture being developed by Facebook and how it might solve some of the issues commonly faced by developers. https://youtu.be/UcqRXTriUVI
React Native's New Architecture - Parashuram N - React Conf 2018
youtu.be
7

Appreciate
Comment
Share

No comments yet
Be the first to comment

Download Qoorio to talk & learn from other Humans
MORE INSIGHTS YOU MIGHT LIKE
Learn more by discovering other insights
Andrius Janauskas on React native developmentLead Software Engineer @ Qoorio
Great news for all react native developers: authors behind reanimated library have announced major new version. It makes writing animations for react native apps much easier for the developers, but the real reason to be excited are the huge performance benefits promised. New library is written utilising new Javascript interface and is not using bridge calls at all. Animations written in javascript are executed and initialised synchronously on native side. This is groundbreaking stuff in my opinion. Check out full medium blog here: https://blog.swmansion.com/introducing-reanimated-2-752b913af8b3
Introducing Reanimated 2 - Software Mansion
blog.swmansion.com

Appreciate
Comment
Share

Justas JanauskasQoorious human
Hope Qoorio will benefit from it soon!
Karolis Grigas on Web developmentFront-end developer, team lead, dancer
Current most popular way of developing web - React - is not sustainable. And that is a sentiment shared by React dev team (@dan_abramov at https://twitter.com/dan_abramov/status/1259614150386425858?s=20) and a great article at https://macwright.org/2020/05/10/spa-fatigue.html It's interesting that web development is going through a common phenomenon of circling back into old truths and a lost way of developing software. Client-side only applications are not sustainable, slow, and are only trying to emulate what a simple static html file with some styling and javascript sprinkled on top does. But it never will, purely because of the overhead of running the code, whose results should've come from backend in the first place. And that goal - static html with javascript small enough to fulfill interactivity on the open page - sounds eerly similar to how web used to be developed 10 years ago. Output some html, and manually write javascript for that page in particular. Very performant, but equally fragile and unscalable when it comes to complexity. Meanwhile, the modern tooling and developer experience for managing complexity is absolutely great. So joining these two things together sounds like a positive direction. Our web applications should serve the results of running it as the main response, with minimal post-processing needed. It should serve minimal javascript for that page, and that page only. Browsers know how to navigate, and they do it ridicilously well. At the same time, from developers experience application mental model remains what it is now - application is one, sound, and non-leaky model which can transition and resume it's state and any point, broken down into components with the same properties. It's just that these components don't return complete representations of themselves, but only minimal result in form of html, with minimal interactivity in form of javascript. The future sounds exciting.
Second-guessing the modern web - macwright.org
macwright.org
10

Appreciate
Comment
Share
When you read a non-fiction book, do you remember it? I love reading development books (Atomic Habits, How to Win Friends, etc) but I would only remember perhaps four or five key points afterwards, even if I really enjoyed the book I wanted to not only remember more of it, but also maximise my use of the book in my life. I tried starting a reading club, which fizzled out. I tried a podcast with a friend, which we became too busy to do regularly. In the end, I have settled on a good solution: -read a chapter -go back through the chapter and write down the main points (as if you were going to give a podcast on the chapter after) -at the end of the book, once you have notes for each chapter, go through them and write ten essential points for the entire book and five great quotes -add these fifteen things to a ‘development book’ that you refer to regularly -use these fifteen things to come up with 2-5 actionable things you will do every day/ week/ month/ time you do ‘x’ activity, based off this -write these 2-5 things in an ‘action’ section of your development book, as well as adding them to your daily/ weekly/ monthly routines as required The difference this makes is immense- reading the book takes twice as long (or more), but the takeaway from the book and impact in your life is ten times the size. Try it and see how it goes!

Appreciate
Comment
Share

Luis Tavira JiménezEstudiant
Thanks for the insight!😋
Download Qoorio to talk & learn from other Humans
Become Open HumanFAQBlog
We use cookies to personalise content, provide social media features, and analyse our traffic. We value your privacy and only use the most necessary and analytical cookies. You can opt out at any time.