I'll get a lot of hate for that but there are two things that irritates me the most :
Not using the right tools for a use case, like using JavaScript to create desktop apps
Sacrificing app quality for money, like calling a web view an app or using bad cross platform tooling instead of the native frameworks. The UI/UX quality gets so much worse when you don't follow each platform principles
Re 2: that's because you have the mindset of a dedicated developer. Which is of course good for a dev, however, on the business side sometimes it's more important to deliver and make $$ then slowly solve issues (if you ever solve them) than make it perfect from the start.
Personally I think the best solution is a compromise, don't 100% mess the code just for easy gains, but do find suitable shortcuts when possible (and yes, non-native apps can be suitable shortcuts in some cases)
First of all, I don't really hate you or your answer, but I'd like to transcend its sentiment.
Development is all about the compromises you make - and you will make them, consciously or not. For example, by adhering to a "use the right tools" workflow, you compromise on the ability to use tools you deem "wrong" to greater effect, which especially for prototyping can be a bad choice.
Which brings us to your second point: when we are aware of the compromises, we should also know the consequences and make them transparent. Using electron for an UI means that you trade consistency with the platform with consistency over platforms.
If you make this choice, it should be a conscious one - just like all of the other compromises you make all the time on a daily basis. However, that does not mean that you sacrifice app quality - and how much money you spend on what is not the choice of the developer, but of the manager. The developer's task here is to make the consequences of each choice transparent.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'll get a lot of hate for that but there are two things that irritates me the most :
Or you can use something like Ionic with Capacitor and get native plus web stack
Re 2: that's because you have the mindset of a dedicated developer. Which is of course good for a dev, however, on the business side
sometimesit's more important to deliver and make $$ then slowly solve issues (if you ever solve them) than make it perfect from the start.Personally I think the best solution is a compromise, don't 100% mess the code just for easy gains, but do find suitable shortcuts when possible (and yes, non-native apps can be suitable shortcuts in some cases)
First of all, I don't really hate you or your answer, but I'd like to transcend its sentiment.
Development is all about the compromises you make - and you will make them, consciously or not. For example, by adhering to a "use the right tools" workflow, you compromise on the ability to use tools you deem "wrong" to greater effect, which especially for prototyping can be a bad choice.
Which brings us to your second point: when we are aware of the compromises, we should also know the consequences and make them transparent. Using electron for an UI means that you trade consistency with the platform with consistency over platforms.
If you make this choice, it should be a conscious one - just like all of the other compromises you make all the time on a daily basis. However, that does not mean that you sacrifice app quality - and how much money you spend on what is not the choice of the developer, but of the manager. The developer's task here is to make the consequences of each choice transparent.