Site Apps as response to browser bloat and lack of functionality
Name:
Anonymous2018-09-08 10:31
Face it, the criticism about "Apps" for every website would be far more relevant if Apps weren't much faster and resource efficient than browsers. Browser bloat fragmented the web, mobile devices turned to lightweight apps and secure app stores. Another aspect is extensions/plugins being replaced by safer but more limited "WebExtensions" which are slower and less capable than site-specific apps.
Name:
Anonymous2018-09-08 14:27
The issue is that every §§app’’ is a feature-limited homemade browser displaying the website itself.
Name:
Anonymous2018-09-08 14:52
you can literally turn a web app into a ``native'' app using one of many different wrapper options
>>20 what does this have to do with anything you fucking retard anus? the pointer points to address, minified URLs also point to address. neither of them do anything with what's stored under said address and both need to store the address, so their're aren't compressing anything.
Name:
Anonymous2018-09-10 12:05
infinitely compress and freeze my dubs
Name:
Anonymous2018-09-10 12:13
>>21 But they are compressing the data stored at the minified URL. Usually you would need the full url. But with minifiers, you just need the ID, which can be as short as a single character (depending on the scope of things you want to compress).
Name:
Anonymous2018-09-10 12:25
>>23 Ultimately, that's just moving the data to another location.
Name:
Anonymous2018-09-10 12:39
>>23 no, they store the original data along with the minified data. and the original data is short anyway, it's not like they minify movies or system images - URLs are generally not even a kilobyte long. the point of compression is to store less, not to store the same thing but also provide a shorthand
Name:
Anonymous2018-09-10 13:07
>>25 You are being deliberately obtuse for the sake of technical correctness in face of real-life application. Reducing the presentable full URL to a shortened one is compression for any clientside code.
Name:
Anonymous2018-09-10 13:13
>>26 no, I am explaining the difference given the context of what compression is used for. and what people use compression for is large sets of binary or textual data. URL ahortener is not an equivalent of compressing a 4K movie so that it doesn't clog your're are disk, it's an equivalent of storing this film on a remote server and writing down the URL. example.com/gay-niggers-from-outer-space.avi is not compression.
example.com/gay-niggersTsk.-from-outer-space.avi is not compression.
Technically you are correct. But for all practical purposes, you are using a 0.2KiB identifier instead of the 4GiB film. This achieves exactly the same goal as compression. If you are still unconvinced, think of it like this: The compression algorithm is a mapping from the minified ID to the full resource. If we have a finite amount of resources, we can put the mappings in the compression algorithm definition. Then the algorithm is simply switching on the ID and returning the corresponding resource.
Name:
Anonymous2018-09-10 13:19
>>28 that's not solving the problem, that's moving it somewhere else. either you need to have those gigabytes or someone else has to, and the thing about relying on someone else is that... well, it's not that reliable.