Nice write up; agree with some thoughts, disagree with others.<p>Think this is daft though:<p>> The word "native" has always bothered me. No one can seem to agree on a definition, but we all agree that "native apps" are always optimal.<p>> I propose the following alternative definition of native: an app that behaves to the quality standards of the platform it's deployed to.<p>> A well engineered Electron app will give you "native" platform fidelity, regardless of programming language.<p>These are simply things I disagree with, and I find it troubling to see them promoted, because I've heard them before, recently, in person, from colleague.<p>You can argue that 'native is better' or not, but really? Do we have to fuss around with wording and pretend there's some magical alternative definition of what native means, in order for us to cool and be writing 'native' apps?<p>If I define 'native' as, written using sql, can I run 'native' queries in my database?<p>I mean, I get it; the point is that native may not be best, for many reasons.<p>...but it bothers <i>me</i> that I've heard people talking about how to define native; imo if you've gone down the rabbit hole of 'define all your terms to mean custom things' so you can call whatever you're doing whatever you like, you've lost the plot, and you're <i>deliberately deceiving people</i>.<p>That's bad behaviour, and I don't respect it.