Embed Notice

@cherold @obsolescentsapien @drazraeltod @pluralistic because the web stack was never designed to make applications with, and as a result of that and the inherent limitations of having to get an app through a browser, it will always be slower and more buggy and more awkward to use then a native app. And trying to make web applications closer to the functionality of a native application through stuff like pwa and single page web application toolkits like angular and react will only make the web page more and more bloated and overcomplicated. A lot of single page web applications nowadays are actually comparable in size to the average native application at around 40 MB or so it's just that you have to download that every single time instead of storing it with you and you get a worse experience from it. You may not notice the janky scrolling and awkward touch surface sizes and stuff like that in web apps but I certainly do. There are just a lot of interface things that are finally tuned in the native UI toolkit that you can't really fix with a web application toolkit. There's a free and open source clone of Discord that I want to use with my friends but right now it only really has a progressive web app version and I tried using that directly but it's simply gross and terrible to use which is why I'm having to build my own native client for it.