iOS Native vs Web Programming

[AdonisSMU]

Downloading static resources has next to no impact on server side resource usage (except for transfer allowance). Of course this assumes you have configured the server correctly to use a decent static resource HTTP server such as Nginx which is lightning fast for such operations. You could even use a CDN which would speed it up even more.

Caching can be used both for browser clients and with API clients and so it doesn't make much difference one way or another. Remember you are just caching the result of a server side operation in RAM so that the server doesn't have to do the same operation over and over again. It doesn't matter if the result that you are caching is a bunch of HTML or JSON / XML.

Static resouces to be stored somewhere... Caching can be expensive and is annoying when you need to change something right away.... Javascript mvcs are slow and so are the animations...css helps with some of that but not in all cases... And there different levels of support so it goes back to my if you have to write proprietary code anyway...

Now the use case forgetting around the app store is a valid one but even then you have to get special permission for that...

 

[Cromulent]

Static resouces to be stored somewhere... Caching can be expensive and is annoying when you need to change something right away.... Javascript mvcs are slow and so are the animations...css helps with some of that but not in all cases... And there different levels of support so it goes back to my if you have to write proprietary code anyway...

Ah but Javascript and CSS are handled on the client. On the server side they are just files and really if you are running a production site and your Javascript and CSS are not stored on a CDN you are doing something wrong.

Yeah caching can be expensive. But that expense is generally required if you run a busy website. It cuts down on the amount of hardware you need to throw at the website for it to run correctly. Using something like Varnish is great for busy websites. It can be a pain to configure I'll grant you that but the advantages outweigh the disadvantages I think.

Now the use case forgetting around the app store is a valid one but even then you have to get special permission for that...

No idea what you are talking about here.

 

[AdonisSMU]

Ah but Javascript and CSS are handled on the client. On the server side they are just files and really if you are running a production site and your Javascript and CSS are not stored on a CDN you are doing something wrong.

Yeah caching can be expensive. But that expense is generally required if you run a busy website. It cuts down on the amount of hardware you need to throw at the website for it to run correctly. Using something like Varnish is great for busy websites. It can be a pain to configure I'll grant you that but the advantages outweigh the disadvantages I think.



No idea what you are talking about here.

The browser simply isn't low level enough and some would argue shouldn't be low level enough to have the type of performance apps have. It's noticeable and obvious...

The last part was me agreeing with the need to get around app stores etc via website.

Google Search in a sense is an app store in that it will blacklist sites etc which is essentially doing the same thing Apple does with it's app store. The difference is that Apple is being more forth coming about with what they are doing. Google is more lenient about what they will allow to be in their search results. In the end its still two sides of the same coin. Google with their forced openness(with exceptions). Apple with their forced closeness (with exceptions).