Hacker News new | past | comments | ask | show | jobs | submit login

To be fair, they're only whining about PWAs, because Apple artificially locked down all native apps. Apple forced the developer shift, their own preferences didn't necessarily change.

If you could install + sell iPhone apps freely, like you can with OSX / macOS apps, 99% of developer complaints about PWAs would vanish.




No because the reason that developers want PWAs do that they can have the same shitty experience across all platforms - much like Electron apps


The developers on HN clamoring for PWA support are not the same devs making "one layout works fine on all screen sizes" webapps.

I'm sad you're equating the two groups.


Yes because the developers on HN can make good graphical apps using cross platform frameworks unlike the

- Java developers

- every mobile OS provider ever who said the same thing - Palm, Microsoft, Google (dart), RIM and even Apple at one point had the same “sweet solution”

- all Electron developers


You're equating webapps with cross-platform frameworks, so we'll just talk past each other.

None of what you mentioned is all of "what webapps are",

just a short list of shortcuts to the technical definition of one.


So exactly what is the difference between a “cross platform framework that runs on top of a VM that abstracts the difference in the underlying hardware” in this case of cross platform frameworks and a web app where it runs on a top of a browser that serves the same purpose and also abstracts the underlying hardware that has the same drawbacks?


Performance? UX? I mean, tons.

What drawbacks do webapps compiled to WASM have, for you today?

Let's make sure we're talking about the same thing.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: