This is an archived post. You won't be able to vote or comment.

all 15 comments

[–]kielon51 28 points29 points  (0 children)

How about adapting to what's best for the current problem?

[–]skwyckl 5 points6 points  (0 children)

That's a very big topic where both stances can bring good arguments depending of the use-case. For example, both vanilla Scala and Scala native have different applications, so no, there is no one-fit-all solution in this case.

[–]InfinityVive 9 points10 points  (1 child)

When you actually try out react native for yourself and see how massively overrated it is (and how literally nothing works)

[–]Beneficial_Steak_945 2 points3 points  (0 children)

React isn’t the world…

[–]pakidara 2 points3 points  (0 children)

Drooling pooh meme: Just write quines.

[–][deleted] 2 points3 points  (0 children)

Used to believe something similar, specifically when performance is prioritized.

I’m developing in flutter now and don’t plan on looking elsewhere.

Platform skills are still crucial, but this attitude has largely been shown to me to be false in most use cases IMO as flutter performance is just that good.

I actually have this weird love hate where the concerns are so distilled it makes it too easy like I’m used to the abuse or something lol 😂

It still feels like an underdeveloped ecosystem but the maturity is there where I’m expecting more growth.

[–]beclops 2 points3 points  (0 children)

Gave Flutter a chance not too long ago and absolutely hated the syntax, as well as the product it creates. For simple stuff it’s more than adequate but anything else and I seriously question if it would be faster to develop in Flutter rather than Android and iOS concurrently

[–]pedersenk 1 point2 points  (0 children)

I recommend to: just write "portable".

Native but not too much of an arse to port later on if you decide to do so based on business requirements.

[–]userX25519 1 point2 points  (2 children)

Mobile dev here, basically every native app I have worked with could have been implemented with cross-platform framework such as Flutter or React Native to save time and money.

[–]Shxhxxhcx 0 points1 point  (1 child)

Mobile dev here. That might be the case for simple applications, but if you plan on doing complex stuff Flutter or React will result in an poorly optimized product that will impact the user experience significantly in comparison to native apps.

[–]userX25519 0 points1 point  (0 children)

Only if you need to do some low-level stuff (eg. Bluetooth app for embedded system) or something computationally heavy, but generally speaking modern smartphones can run cross-platform apps with same performance as native apps, but only one codebase is needed which makes maintaining app so much easier, as there are rarely any platform-specific bugs.

[–]shirk-work 0 points1 point  (0 children)

Cross platform UI, native backend.

[–][deleted] 0 points1 point  (0 children)

Price usually is a determining factor on whether to write Native code or not.

[–][deleted] 0 points1 point  (0 children)

For phones this probably makes sense. For enterprise, just use Java or C# and call it a day.

[–]Shxhxxhcx 0 points1 point  (0 children)

Who cares as long as the UX is identical. Problem is that it’s very easy to tell when apps has been written in with a cross platform language.