On 18 February 2015 at 11:14, Anne van Kesteren <ann...@annevk.nl> wrote:
> On Tue, Feb 17, 2015 at 8:47 PM, James Burke <jrbu...@gmail.com> wrote: > > Echoing the sentiment about "hard": it adds a lot more complication. > > A service I now need to monitor as a developer to keep running, when > > it is not needed if I do a native app. It can also require a different > > set of developer skills. > > This will always be true for the web. You're not just in charge of > writing the application, but also making sure it's "available for > download". There's a lot of parties around the web helping out with > infrastructure needs, but if they're not good enough compared native > perhaps that is a place where we can do some good. > The difference between putting up a static website available to download is an entirely different prospect to maintaining a live active service. Github has make publishing / updating static sites free and easy along with several other services, self hosting a static site I dont think is prohibitive. But having to run proxy servers for network (socket or cors) access very much is. > > > > I work on the email app for Gaia. It would give me nightmares to try > > to secure a general email server proxy. I would not want to make > > guarantees to people on its reliability or trustworthiness, and having > > to be on the hook to possibly accommodate government snooping > > requests. > > > > I greatly prefer a model where the browser asks the user "OK to > > connect to this server" for cases where this cross domain access is > > needed, so that the user knows what is happening, it is a special > > privilege, and the user should have control over it. > > I don't think anyone has found a model that the user actually understands. > > > > Maybe there is a different way to go about this, but CORS or running a > > proxy is not a sufficient story. > > > > Without this sort of capability, any email web app is at a distinct > > disadvantage to a native app environment (also see the need for TCP > > sockets in the email case). > > Well, unless the application is coupled with the email server and > there's some WebSocket bridge in place. As long as we keep stuck in > the "web has to be like native" thinking I don't think we'll advance. > We need to play to the web's strengths. > > > -- > https://annevankesteren.nl/ >
_______________________________________________ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
