![]() ![]() Meanwhile they seem to have switched focus to customers that are actually willing to pay for their tooling, thus hardware manufactures selling medical, IoT and automobile devices, as one can easily see from the upcoming Qt World Summit schedule.Īt personal level I have been using the former approach of C++ plus native views, while at work our mobile projects have been either Ionic based or plain mobile web sites. Regarding Qt, when I tried it about 4 years ago, I was quite disappointed with their mobile support, because they only had the bare minimum, and integrating the platform APIs meant in the end the effort was bigger than just doing C++ plus native views. It was a good decision to focus on JavaScript back then, and it is more so in the context of native apps. I don't see any reason to waste my time with Dart. I also don't believe in RN and for me Flutter is the last hope of keeping Dart relevant outside the Googleplex. And people who like using it can happily ignore you. ![]() I also don't think it would have been a very good choice for Flutter.)Īlso what's with this whole "Dart struggling for survival" meme of yours. I think it may be older than mid-90s too. I remember hearing about it at uni back in the mid-90s when discussing CBD. Hopefully someone will build this stuff for other popular stacks too. Nor is it particular familiar for developers of existing mainstream languages.Īnyways, I agree that there's nothing "special snowflakey" about any of this technology, but no-one else, that I'm aware of, is shipping a language and toolchain that ticks all of these boxes at the moment. Nor could Eiffel have been used for Flutter since the GPL means you can't embed the VM in your app. Even if you want to count Eiffel that's one, not plenty. "There are plenty of programming languages that offer these applicabilities." It's open source under liberal license which allows you to embed it your app. It's performance, even on iOS dev mode is sufficient to do all of the layout and widget code. Does subsecond hot-reload on iOS and Android (also more than just method bodies). It has types to allow working on large codebases, and efficient AOT compilation. It's a familiar language for developers who have written JS, Java, C#, or C++. This is me paraphrasing why the Flutter team think Dart is a good fit: "is there any feature of Dart that is required by Flutter?" It's not technically difficult to deal with but it serves no real purpose except to be different. I've run into nasty bugs with every compiler I've ever used.Īs an engineering decision, is there any feature of Dart that is required by Flutter? This looks like the software analog of the pentalobe screw. Programmers today frequently need to learn new languages, but why? If you believe that these languages are similar enough to be "super easy" to cross between them, then how is it the incremental value of any of these languages so great that it justifies writing a new compiler, and making millions of programmers figure it out? It's not just learning time. Besides using the characters a lot, I can't think of much they have in common. JS and Swift, in particular, feel like opposites. Easy learning is not a zero cost activity.) (Learning to speak a language may be super easy if you already know another one in the same family, but you still have to learn it. I've used 4 out of 5 of them professionally, and I'd say it takes a good 6 months to get comfortable with the new syntax and idioms. Those languages are pretty different from each other. > don’t worry, it’s super easy if you’re familiar with Java, JS, Kotlin, Swift or C# I'm arguing that the architect should have had a plan for how this would work before introducing react native into the app.Īirbnb has done a lot of great react-native work, so I know the issue isn't technical competency, but the linting rules Airbnb popularized suggest a very trees-oriented (not forest oriented) perspective on tech, which is the kind of perspective that makes the above kind of mistake. With react or react-native you really need to know where the data is coming from and how the data will flow through the application. > many_ cases and orgs where it is not a good fit This is often the case with bad technological decisions in startups and is rational because of sunk cost. If you read my comments I said that removing RN was probably the right thing to do by the time it happened. Teams and individuals make mistakes and misjudgments. Not sure what you found negative about my view. I was thinking the same thing about you, no offense. > it's increasingly clear you are pretty fresh in your career Not at all, I focused on the one thing that was mentioned as the most significant reason for team frustration with react native.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |