3 ms·
What are you referring to, with this? PWA is one of my pet topics, and I am not aware of any such limiting factors, and I'd like to be.
by aaaaaaaaata 5y ago
What are you referring to, with this?
PWA is one of my pet topics, and I am not aware of any such limiting factors, and I'd like to be.
- rektide 5y agoIn this case Wallabag appears to use a lot of PHP, so porting it to be a self-contained standalone static page is going to be a bit tricky. But assuming porting the codebase weren't so hard, the real issue is that the web platform- even for PWAs- is cruel & iron-hearted about who can talk to who. Applications are still the only free & open communicators on the planet, and that's just fucked, so blasted wrong. CORS is probably going to block most basic interactions. Wallabag is a basic simple application, something that conceptually could easily run as a standalone static web page. But if that page tries to go fetch("https://www.washingtonpost.com https://www.washingtonpost.com") it'll probably immediately hit some CORS restrictions & die. The web got deeply mishandled when we decided it was unsafe to let sites access each other. There's been a deep freak out, an anti-connectedness that's been ruling us for the past ~2 decades, and few forces have moved the needle the other way. We're all afraid of ads & tracking, the security atmosphere is tight & hot, but it's also isolating & destroying the idea of the web, a cross-connected medium. PWAs have gotten all manner of new great APIs & access, but they still have ridiculously brutal & harsh connectivity constraints that have only gotten higher harsher more brutal year after year. (WebRTC aside, There's not been a single year where the web has gotten better able to interconnect, better able to communicate. The cruelty & hostility barometer has gone up and up and up. People misuse the web for bad, so we'll make the web worse, ad infinitum.