YahiaPsy If you really believe that you haven‘t seen his video about the apple developer conference. He didn‘t understand one thing from the keynote but still feels educated enough to talk it down to the ground.
Do you think a ex google ex Facebook tech lead doesn’t understand the main native framework for the one of the largest frameworks in the world... built and maintained by a company he held a high position at?
I think it’s always a good idea to show different points of view. React native is a tool like any other language or library and it’s how you use and apply certain tools for certain problems that is important.
Wasn't expecting to see you here, loved your Firebase tutorials! They were super easy to understand and helpful. Any plans to make WatermelonDB tutorial?
My daily worry would be if he is sarcastically, ironically or directly insulting my work and existence. At first I would laugh with him, and then I'll read between the lines and become depressed.
@@flarebear5346 It effectively requires me to use macos which I personally find to be intolerable. I also have no desire to write swift or objective-c.
@@sbrugby1 Yeah, why write in good languages that are being adopted and not dropped when you can stick with your ancient and bloated web libraries? This is the guy who's always surprised when layoffs come that he got the axe. You live NOW, not 2005. Grow up and learn a present-tense development skill-set, you dinosaur.
He's a smug moron. His idiocy stems from not technical ineptitude but strong opinions not based in reality. This is the clearest in his video where he shits on Linux saying all it's good for is backed development. His idiocy really shines there.
I dont even remember why i unsubs him, i did got clickbait at first, because ex-fb etc, then his videos is not build me to be better. i better watch ben's video... increase my skill, and also still talk the bigger picture.
@@lordswaggity1213 I just watched that and he had no clue what he was talking about. He thought that front end coding was completely dependent on PhotoShop. (This is at a time when Figma and Sketch had become top design tools) Modern front end stacks create the ability to code front ends without interface builders. Also he seemed ignorant that Linux is the key ingredient in industrial design things like ATM machines, payment systems and automobile's electronic systems.
ill say one thing, If you are a proficient with Reactjs ...Learning React Native should be piece of cake . And judging by the number of websites that uses React framework i could confidently say React native has a bright future. React Native and Electronjs are like brothers now.
it has nothing to do with "full time developers", but might be typical for developers spending time in front of screens all day - it has something with missing diet components and/or not enough sun exposure during daytime. Malnutrition / Missing certain vitamins in the diet will cause skin and saggy eyes IMO.
In my humble opinion, I would prefer to write my apps with the android sdk or the xcode/swift respectively. Cross platform tools are always great for approximately 85% of the job, but I've also seen that 15% turn into a major pain-point. In some respect, it seems like a real win for business costs to use react-native, but sometimes the cost of those edge-cases can be monstrous and sometimes you are stuck with workarounds that never get fixed the right way because you're stuck on this cross-platform scaffolding instead of just using the tools that are developed with the intention of that exact platform.
This here. Also if your app uses a lot of low level native APIs, i doubt react native could do much. Finally, building layers and layers of abstractions across the native library is a few steps from disaster
Theres always going to be an ala cart of pros and cons... its really about whats the most important factors for the individual... is it scalability, cost efficient, whats the workload vs throughput?... that all comes with cost analysis and experienced software infrastructure engineers
You shouldn’t tie your identity to things in general, it’s a bad habit. There are bad technologies badly engineered, poorly designed. Try not to purchase their merchandise. I have an “X Window” t-shirt I use to clean up cat puke.
@@smallbluemachine that's human problem. If you will work in a field for like 5-10 years, you will definitely start judging yourself based on that field's standards.
Great video. Every framework is made by incredible people. Imo, we all have to apprericiate to them instead of saying it is garbage. Everything has its own pros and cons.
OMG THANK YOU!! I am so glad to hear both sides of this topic. you were great at explaining all of his topics and really gave a complete overview of everything.
Even brand new projects with React Native requires you to write a lot of native code (or use whatever libs are available) if you want to interact with low level hardware etc.
Agree. And some big firms have stated just that. Library support. And does anyone wonder how long Apple will 'play nice' with the companies putting out these frameworks? About 2 yrs ago (I think) Apple said they would start rejecting apps that were obviously built from generic code with just minor modifications. Using that reason alone they could start rejecting RN apps.
@@WestCoastAce27 apple seems to not care as long as you are updating and publishing insider their appstore, because at the end of the day that is at least 100 bucks annually for the privilege. Now PWA? oh they hate those, safari support for some functionalities? same, those mean people can circumvent their appstore which makes them go funky.
@8:31 I've been working on RN for two years now, and I can tell you that 60% of the time you need to put on the native work to deal with the small bugs that come out from these implementations (actually, the safe area keeps failing on some new devices). One awful scenario that I found myself into was adding some features from firebase in both native versions. It was a huge pain. Still, I have seen the power that hybrid apps bring to the market. Our competitor had a similar version of one of the purely native apps we had in the company, but theirs was hybrid (you could tell by the small gaps in performance). It had 10x more users and features than ours. You could tell easily that it had a "deeper" and more robust development, better practices/architecture and other characteristics of good software engineering instead of the "native performs better" strategy.
I did two apps, one with google java and one with react native, react native is much easier and ofc there're alot of bugs, but for me its faster as I do all necessary processing at my node js server
"A React developer can get up to speed quickly and begin being productive quickly" This is spot on! I really like your channel. This is exactly my experience I learned React, got a job as a React Developer and the company I work for has RN apps, so guess who picked up RN skills on the job! this guy! I don't put too much stock in TechLead, he is talking about very specific cases of Big tech companies in Silicon Valley, I could say PHP is garbage, or .NET is garbage, or ABC library is garbage but there are still people who are making a living off of that language/framework/etc, I agree with Brad Traversy, we need more positivity, "This is XYZ Technology why is great!"
Well, I've had a quiet diverse experience in terms of frameworks both web and mobile. And there's NO perfect framework, or perfect fit for cross-platform dev, it always comes down to what exactly is needed for the intended application. But I must say, the first time I was invited to a multi-project hire, built with react native (site and apps), fully leveraging expo, react and code reuse made by a fairly good developer, it was a PURE delight, was one of the best hires in my 10 yr development career, being able to Reuse a lot and having the ease to publish with Expo saved me COUNTLESS hours, and is a very powerful combo for developers who don't need to build high performance apps, but need to deliver more (qty) in less time.
As someone who worked in enterprises for years. 15-20 days window to use the SafeAreaView is not enough and it's probably going to be stressful for everyone. Things move slower in enterprises where different features and widgets are maintained by different engineering teams. A huge coordination effort is needed for that and everyone will have to fit it within their scrum sprint. The safe area view might not be a single wrapper around the entire application but it could be implemented depending on a lot of variables. Meaning that planning is needed to happen beforehand. I remember seeing a lot of applications that had content showing behind the status bar after iPhone X released and wondering why they didn't fix it. It's probably super easy for someone maintaining a calculator app, but it's quite difficult for a many other companies. In my opinion, React Native is great for indie developers since they usually work solo and it would be a huge undertaking to develop and maintain 2 separate code bases, for each app. Because usually they would develop multiple apps. But for companies who have one app as a product that requires the best performance and stability, React Native is not gonna cut it. It's just too risky. That's why I think Tech Lead mentioned it would be easier to hire 2 separate teams, just remove the headache and stress.
Yeah I kind of agree with tech lead here. Almost all of the projects I've been involved with that have been using react native have had many of these issues. Lots these of apps that only use react native on a few components or in headless mode etc. There are still performance concerns and there will always be some performance overhead to using JavaScript outside of a browser. Also, what happens when you need to grab something from one of the native APIs but there isn't a good third party library for it? Now all the sudden you need devs who can use swift/objective-c and java/kotlin. There are other concerns as well, why should I go and use jsx when I can use some of the new declarative ui libraries for iOS and Android? Now I certainly am not saying that react native isn't a fine choice for simple and less intensive applications but for these larger and more involved apps it just doesn't fully cut it.
I have used React-native for a ton of apps and tbh the only issue i have with working with it is maintaining external libraries and dealing with all off the odd non-descriptive errors, but this is a JS problem more than a react problem. I still feel like learning a native language is going to save you a lot of headache in the long run.
I have been getting vague errors while building or executing the react native apps.i really find them irritating, comparatively flutter seemed more promising to me
React Native is probably one of those new things that might make your app easier to make but it turns out to be slowly and underdeveloped & documented (and its libraries) with a sparse community.
I also think it's worth mentioning that in cases like the SafeAreaView, even if React Native's developers didn't add built-in support, since React is open-source, and you're literally meant to use third party modules and packages using NPM/Yarn, you'd probably end up with some random developer adding safe area support anyway, and that goes for any other features Android or iOS might have in the future. Even if FB stops supporting React, it'll still keep growing.
I just migrated from android to react native and I am really happy with it. Because you can ship new features in no time. And you can find great resources out there that can easily add productivity to your app
React native is good for your weekend agency app, and a fast way to prototype and validate your idea. As soon as you need access to the machine and do complex stuff, everything starts becoming a mess and it becomes an unnecessary layer of abstraction.
I've been working full time with react native for about two years on amazing projects from some of the biggest companies in the world, and personally I do feel like it's garbage. It has a lot of potential NOT to be garbage, in fact it has potential to be an awesome technology but as of right now I truly do despise it. It truly is trash in my opinion.
It's hard to list all of the problems I've had over the years so far but the ones we had recently that I can remember are: Flatlist component seems to have a fixed limit and when I tried to implement lazy load I was faced with issue #25239 that still hasn't been fixed in months. Another problem I had recently was that at least 30% of the app that I made only looking at Android devices (I was using Windows only so I couldn't test on iOS emulators) is now completely broken on iOS, some styling features differ from OS to OS so what seems OK on Android might not be OK on iOS when you test on it. Other than that, there's always some major complications whenever you're trying to build the app like it just suddenly doesn't want to build for whatever stupid reason so you have do figure out why, trying every method of clearing caches possible (e.g. cd android && ./gradlew clean - going into android studio and resetting cache, syncing files with the project etc) there's always some really stupid and mysterious reason why you app suddenly, out of nowhere, stops working. When you want to debug code there really are no breakpoints, I mean you can try and use DevTool's breakpoints but good luck with that, you're better off filling up your entire code with 'debugger' statements in each and every line to see what's happening. On that topic as well, there is no proper CSS inspector, you can toggle the app inspector hitting CTRL+M for sure but it's super shitty and you're also just better off coloring whatever View or component you want to understand better, so get used to making rainbow-looking-ass screens and components. Well, these are just some, a very small portion of the problems I've had with this absolutely shitty trend on the market recently, it gets my bills paid for sure and pays well as well but it's still quite shitty, I miss web development. Oh another problem that is driving me insane lately is that we have to implement Google Analytics on the app but the RN app I'm making is going into another app (as a .aar (lib)) and therefore we have to use the GA of the dad app, passing down the native methods so RN can use throughout the app, that part is going quite OK but the native guy that's doing this with me is having a lot of problems having to link RN dependencies by hand so the other RN app that's already in there (also as a lib) doesn't conflict with the one I'm making or the dependencies I'm using. Also, let's be fair here, RN performance is never going to be on par with native development. It's so easy to code something that runs out of memory - create too many components with too many methods and there you go: X app stopped working!
@@habibsspirit I have to agree, react native is garbage. I switch to Flutter and I'm much happier. Making a list with react native is so slow. Actually react native is slow in everything
Based on my experience, I would advise choosing to learn either one and learn it well. You will be able to judge by yourself. The absolute truth is you will be successful either way you go. I still have bias like everyone else. I prefer native applications.
The problem is a lot of people/viewers do. Brad traversy came out and talked against techlead because he was bombarded by people saying that there is no need to know react native and quoting techlead.
my problem with "dont take techlead srsly" rationale is that its not obvious satire or shitposting, i dont see how any of his videos come off as blatanly comedic. He's like Dan Lok but for coding
My issue with React Native was that the CLI was broken at the time I began building my mobile app and Expo didn't support in-app payments which would have cost me money down the line, so I went with Ionic React. I am very happy with it so far, the components are performant and intuitive, the framework points me toward cleaner coding practices than Material-UI (which I'm using for my web app) does, the completed apps I've seen that were made with it are fast and beautiful and as a React developer I was able to get up to speed with it very quickly once I learned and got familiar with TypeScript. I can actually port components from the web app (NextJS/Material UI) to the Ionic mobile app in a very short time and mostly all I have to do is add TS interfaces and type checking and convert the MUI components to Ionic components. As a solo app developer I am very thankful for cross-platform frameworks.
It’s a framework (think of it as a developing tool) for programmers to code for iOS and android at the same time, as android and iOS are different operating systems
RN is not garbage and is intended for case where you have small team, already or working on React Web App/Next js app and you want a mobile app. Thats is what it bridges, its not intended for making high performant apps or mobile for scratch.
Thanks for clearing the air around this topic. TechLead is over his head making such a claim. Instead of making videos in which he writes code on a particular concept, he rather sits and talks about his past experience working at facebook and google. I sometimes doubt his ability to write meaningful programs.
yikes. He might be whatever, but doubting his technical ability makes you look like a clown. The very fact that he got into Facebook with that kind of compensation package should be a testament, but if it's not, I suggest checking out his resume tips videos where he displays his own. Check that out.
@@ritwik5774 The fact that he's ex facebook, ex google, he could not be as good as you think. Talking trash about a framework that others are spending money and time learning in order to land a job does no good for anyone. Have you watch him code anything like a simple project or a crash course? I read a thread where someone nailed down the reasons he got fired at google. His code wasn't as good as expected. Working at a big company seems like a huge accomplishment but getting fired is another story.
I think if I want to make a graphic intensive app, like a mobile game, I wouldn’t consider react native but if I’m building a Facebook, Twitter, or instagram, then react native will be the best tool. I don’t believe the developer at Facebook are so dumb that they create a garbage framework for developing apps, so far as I’m concerned TechLead is an entertainer.
Having been through this with the Openfit app, I can say that there are definitely downsides to choosing React Native for a production app. I think it's fantastic for quick POC, demoing your idea across multiple devices quickly, but when Product expects a smooth performant app identical to what they'd expect from native, things start to fall apart. Namely the development environment is always failing in a large team of engineers, performance (not that these can't be mitigated as stated above), latency between bridges, UI needs to be written twice, once for mobile in RN and a second time for web optimized for browsers. Perhaps someday more libraries with a unified api will be developed and maintained, but currently the time spent maintaining a "universal" UI library is just really cumbersome. Swift UI & Kotlin aren't difficult to learn and are married to the devices and ecosystems for Android & Apple. My new recommended approach is unify the logic serverside as your single source of truth, then maintain 3 simple SDK's that maintain clientside state and connections. UI is then written natively with each device optimized appropriately, for each ecosystem. Yes, you're writing and maintaining 3 apps, but you are in React Native as well, the time is just spent figuring out why your build is failing or how to update based on the last major release, etc. ;)
As a native mobile dev that has used react native, i can honestly say that a production company should not use react native as there main mobile tech stack, unless your a startup who is trying to save money.
Definitely agree we did the same mistake for a product that has a lot regulations and need to use some specific 3rd party libraries as well as Apple ODR (On demand Resources). Spent 1 year to try React Native and revert it back :)
RN was garbage when I used it about a year and a half ago. A ton of native APIs aren't supported, or you have to use some unmaintained 3rd party plugin. Deployment is still a pain in the ass. OTA updates don't exist unless you use Expo-which is a great project but just not advancing fast enough to actually fill that huge gap it need to fill, so you almost always have to eject. Another point against RN is that at the time I worked with it styled-components was slow to the point of being unusable, and there wasn't a good way to handle different resolutions. Airbnb's implementation of RN sounds really stupid (most big, incremental, project changes are destined for failure), but that doesn't mean RN is actually good. If you're not using it to do a lot of native stuff (which again, RN/Flutter/Xamarin suck at having/maintaining a long list of official native APIs), then old-ass Cordova/Phonegap (or actually probably Ionic's Capacitor?) and just a really performant PWA is my favorite approach. They have a few native APIs, and anecdotally, in a medium sized project & a small project it just felt much more performant. I'm 99% sure time will prove me right and everyone will abandon RN/Flutter/etc. and return to the Phonegap approach of just wrapping everything in a web wrapper now that phones are way more powerful than they were in the 1800's when Phonegap came out. Consider how many successful apps are on Electron. I suspect it's because the platform Electron operates on is simply more powerful, which phones are nowadays. Maybe RN is more performant now (I heard they were doing a rewrite?), but unless Facebook starts dumping tens of millions into the Expo team's approach, RN is always going to be garbage Facebook forces in-house devs to use so they can pretend there are real-world successful apps built with it. Otherwise it's just not simple and fast enough for anyone to actually develop anything quickly with it. I don't watch Techlead. He's a profiteering meme channel, but these "ex tech lead, ex millionaire he can't code lmao" comments are cringe. He was good enough to get hired by Google/Facebook. He just didn't like working at those places so he bailed and now critiques them for money. You can pay your bills programming AI that will screw mankind over for profits, or you can pay your bills critiquing organizations that do that. I think the latter is more honorable.
Cory Simmons “I don’t watch Techlead” riiiight and you just magically know all these things about him. Alright TechLead fanboy, go back to defending him for Doxing kids and stealing business ideas for programming courses.
It's a good thing to see both of your videos. TechLead is more on extremely high level of things (I've only seen some videos), true to his mentality, and also clever in his "marketing". You know the small tricks, the video titles you've both used are an example of that. But I respect really the fact that he doesn't say what people wants him to say, that a thing demanding viewers like also. And I guess it's his target market. None of you did long video on the RN, so for the 10min time, you both did a great job. Thanks to have deepened the subject and for your different perspectives.
I've got rules for myself to write react native applications: Render everything at once. Never use hooks, especially useState. All components manipulations like hiding, moving and appearings do with Reanimated. And one more, a little rule, never use touchables from 'react-native' including brand new Pressable, use only react-native-gesture-handler instead. The result - everything extremely fast, smooth and no any flickering. And bonus, code twice (yes, twice!) smaller and readable.
I've been using RN for production and I don't see how the performance is poor. People who think RN performance is poor probably used an older version from 2017. I don't mind using multiple codebase as long as I use the same language and share codes.
Ive been in the industry a bit and met no mobile developer who wants to work within these hybrid frameworks... the idea of writing your whole app in react-native, Cordova or any other dumb hybrid is that you’ll almost always have to create plugins that are OS specific, and because there’s new features released for iOS and Android every year; you’re almost never afforded these libraries in these hybrid application around launch. Why write an app in html, css, jsx/tsx then still have to write plugins in java and objective c? Practically it seems like a big waste of productivity and leads to endless headaches.
I think my main objection to React Native is simply the fact that it's too complicated. It attempts to build this functional reactive abstraction on top of two separate platforms which have a more object oriented style. The result is effectively a fist fight between a Catholic and a Protestant. React Native "pretends" to be functional, but it still has to go through this imperative object oriented layer beneath it. The different programming paradigms clash with each other. This makes simple things like navigating from one screen to another a complicated affair, since what ought to be a component reacting to a state change needs to be phrased in terms of the underlying object oriented frameworks. If you want to do functional reactive, I would imagine it would be better to do it at the level of the native SDK's themselves, something more in line with Swift UI. That way, you're not introducing this extra communication layer through object oriented code. Another option: do what game engines do and go underneath the SDKs. Write a cross-platform C library that generates render commands you pass off to the GPUs on the different hardware platforms and never go through any object oriented code that way. I think abstraction is fine. In fact it's quite often very useful. But I object to this particular way of doing abstraction, for the reason that it's not built on top of a programming paradigm that matches its design. It's sort of like Kowloon Walled City in Hong Kong, this giant mess of corridors and apartments just stacked on top of each other with little rhyme or reason. There comes a point where you have to say it's probably not a good idea to stack another level of apartments on top of that thing and we'd all be better served if the whole edifice were demolished. And that's why I think React Native is garbage.
@@pallavbh23 Take a look at the Handmade Hero series. Casey does a great job of showing people how to create a cross-platform game engine from scratch. A similar approach could be used for cross-platform mobile apps
You can carry around a full toolkit with different sized screwdrivers and pliers or you can carry a gerber multi-tool on your belt. It won't be as good as the specific screwdriver you need and the specific set of pliers, but the gerber is going to be good enough in many cases.
Yep dark mode was a huge problem for our app as well... and it took a fair chunk of time to get support for it..but yeah. Great response haha. Like every language there are use cases for each where one may be better than the other. Just remember that a cpu is just a rock we taught how to learn with electricity 😂
I have two years of experience with react native if you want to do stuff like background tasks is not possible, push notifications are not so good, react native is very community-dependent and you generally end up using many third-party libraries which could be deprecated at any time. I applaud the efforts of Facebook and the Expo Team to keep React Native up to date, you guys do an amazing job, but unfortunately, they will always put out fires. I think for that reason React Native doesn't have a stable 1.0 version yet.
well I have 4 year of experience rofl rn is great to bootstrap your idea and grow your project to a point that you have resources to migrate IF you really needs - like if your projects really needs background tasks then you wouldn't even start a rn project; you don't have try to lift the world and code in swift and kotlin(putting aside a lot of web knowledge and practice) just because you want to go full native because, in many cases, you won't need.
So 3 years in future, React Native was probably the worst investment I have done so for as a mobile lead myself. "If you're not doing anything too crazy" should not be the only reason that justifies to choose React native. We have came across many issues regarding 3rd party libraries in the long run especially maintaining them. Also we were supposed to use ODR (On Demand Resources) for some Regulatory reasons and it was a nightmare so we eventually had to have many native codes to implement. Yes we were gaining time on release to market for the features but we ended up losing nearly the same for maintenance and debugging. As a developer I would choose to minimize the debugging and bug fixing any day .
The problem with Flutter is that it's nor Java/Switch, nor Javascript, so you kind of invest in a riskier knowledge. The market dictate and it will have to be WAY better than React Native to change market direction.
@@jonathanantoine4962 That's why i love Flutter. Dart code is expressive, clean and minimal. Dart was specially designed for this task. When i used flutter I was not a master of Dart either, but i was able to quickly go through it and do the job right. Also, flutter does an amazing job using a custom renderer. I think it will change the market direction in few years :)
@@jonathanantoine4962 No Flutter will catch RN for sure. Its still very young and growing fast. I've used flutter well for many projects and i got quite good results in less amount of time. Give it a try and see for yourself.
Knowing TechLead he'll respond to you with a video called "Reacting to Ben Awad, as a millionaire" with some answer as cheap as "I consider myself successful even though I'm suicidally depressed, also I'm a millionaire and that's why I don't code anymore anyway." ...Don't bother dude.
Dude all he does is clickbait and try to promote his side business. Totally worthless channel that used to have "some " value for developers. Don't waste your time responding to someone that wasn't serious from the beginning.
Well, it's not garbage, it's more of a niche choice. Have to meet few constraints: app requirements are met by react native capabilities, tough to crack due to 'unknown unknowns'. (see later article reference) company has limited resources to invest into an app hiring native teams. Second reason is that it's simply not a "boring technology" yet. For those who the phrasing does not ring a bell: mcfunley.com/choose-boring-technology is generally what mature companies will stand by and for a very good reason. This disqualifies the technology for companies which maintains an app as a long term product in constant development and maintenance. As even if 95% features of native are supported, those 5% may come back biting your arse and being not worth the risk down the line. Ben talks about companies having 50% code of react native as seemingly an evidence for migration, but that's faulty assumption as well. See companies experiment to see if things can work out. That however does not mean 'adopting'. Good example for React Native in particular is Air B n B being react native poster child a for quite a while, dropping it in it's entirety and going back for native. This does not mean that React Native is garbage. It means that it has limited use cases. And if you are fine with that, you can really leverage it for your benefit. I do believe that this piece of technology is great for smaller web agencies or freelancer who do one time gigs which are generally under simple requirement constraints easily met by React Native's profile and capabilities. As for you tubers. TechLead, JoshuaFluke, Swarkovitz guy even TraverseMedia are mainly youtubers, not programmers, who's concern is to create popular content first. It's validity second. I have no doubt that some of them were actual professionals who are practicing the trade, however as focus shifts, skills change as well. And it's easy to become a bit restricted by your audience in terms of what kind of content to produce when you generate enough gravitas. There are very few genuine professionals on youtube. One which you may want to check, and I recommend it for newbies / beginners especially is Frederick Christensen. You'll notice the difference in tone and attitude right away. Ben's shortcomming is seemingy lack of actual professional working experience. Very well reasoned person and seemingly genuine with balanced though process and concern for intellectual honesty. I may be wrong, but that's a vibe I get.
If you are a company use React Native when you want: 1. Faster time to market. 2. A great pool of developer talent that can leverage existing React knowledge. 3. Not just a simpler process for assembling a product team but also reduced complexity in the product release cycle. Also, React Native is highly extendable. Potential performance bottlenecks that you experience down the line as your product grows can be mitigated with Native Modules that bridge to React Native.
Problem with 'one app' for multiple platforms is that you will end up with the lowest common denominator for both and will always feel like you are trying to catch up to innovations and not innovating your self.
how i am here...? 1. Search React native on youtube.. 2. then.. found why React native is garbage. 3. then found this.. Why React Native is NOT garbage. 4. then I switched off my phone and went to sleep...
I love how people address React Native as RN. But RN is commonly used in casual text conversations as "right now". Then people bash React Native for its performance. The irony is too funny! 😂😂😂😂
Ben is quite biased to take him seriously. I do React now don't like it as much as it over complicates simple things. Good TS support and a lot of ways of doing things. For App development would definitely learn Flutter instead of React-Native.
I love react native and it’s so heart breaking when people hate on it. It’s not perfect by any means, but no framework ever is. RN is such an amazing framework along with a thriving, supportive community. RN was my gateway to iOS development, and now I’m learning how to write native modules/comps with swift/objc. There are a lot of pain points, but the RN OSS community is always there to find solutions.
If someone uses it, its not garbage , they say Wordpress is garbage but it is used my millions and all over the place. For it to be garbage , it will only be used by his/her creator, nobody else would use it (assuming it was a product meant to create revenue or people willing to pay for it)
