Slashdot Mirror
Safari Browser May Soon Be Just As Fast As Chrome With WebP Integration (thenextweb.com)
An anonymous reader writes from a report via The Next Web: The Safari browser included in Apple's iOS 10 and macOS Sierra software is testing WebP, technology from Google that allows developers to create smaller, richer images that make the web faster. Basically, it's a way for webpages to load more quickly. The Next Web reports: "WebP was built into Chrome back at build 32 (2013!), so it's not unproven. It's also used by Facebook due to its image compression underpinnings, and is in use across many Google properties, including YouTube." Microsoft is one of the only major players to not use WebP, according to CNET. It's not included in Internet Explorer and the company has "no plans" to integrate it into Edge. Even though iOS 10 and macOS Sierra are in beta, it's promising that we will see WebP make its debut in Safari latest this year. "It's hard to imagine Apple turning away tried and true technology that's found in a more popular browser -- one that's favored by many over Safari due to its speed, where WebP plays a huge part," reports The Next Web. "Safari is currently the second most popular browser to Chrome." What's also interesting is how WebP isn't mentioned at all in the logs for Apple's Safari Technology Preview.
You know. for porn.
"Microsoft is one of the only major players to "
What does that mean ?
I hope not. Google makes some of the absolute worst piece of shit software imaginable.
Apple would be wise to remove ever line of code written by google filth.
BPG is better and can be accelerated.
no it uses Middle Out which was inspired by ...
Some drink at the fountain of knowledge. Others just gargle.
(*waits for angry mob with torches and pitchforks*)
"It's hard to imagine Apple turning away tried and true technology that's found in a more popular browser..." reports The Next Web
Nope, sorry The Next Web, you must be new here.
It's not hard to imagine Apple turning away popular technology at all. They have done so repeatedly throughout their history. Walled garden anyone?
Google found yet another thing it needed to offer with a new name. Bravo!
About standards
Nobody will use it regardless because it's still garbage. Only now it'll be lightly faster garbage I guess.
FLIF improves on webp by another 14%.
Hope it stabilizes soon.
http://flif.info/
WebP is a freaking image file format, its that freaking simple. I mean 500 words of bullshit about "technology from Google that allows developers to create smaller, richer images that make the web faster.",
Literally all they had to say was WebP is like JPG except it compresses more. Thats it, no need to say anything else.
These days - aside from (hypothetical and inevitably blocked) ads - it's not images that are the root problem. It's the half gigabyte of javascript.
I'm sorry Mr. Went To School For Web Design, but the moving pull-down menus and dynamic sliding content and whatnot is just not needed (except to justify your career). When I visit a website, all I really need are maybe four buttons: "BUY OUR SHIT", "DOWNLOAD UPDATES FOR OUR SHIT", "READ DOCUMENTATION ABOUT OUR SHIT", and "CONTACT US FOR ALL THE INFORMATION ABOUT OUR SHIT WE CAN'T BE BOTHERED TO PUT ON OUR WEB SITE".
Skip all the embedded activity tracking, metrics, demographics and dynamic content and we could go back to the golden days when web pages were under a megabyte on average without images.
"Oh no... he found the
Still gay shit.
Regardless - karma to burn. Use your mod points. Strike me down! With each passing post you make yourself more and more my servant!
On Macs I use Safari first, Chrome second and Chrome only on Windows. Safari runs circles around Chrome, so I definately wouldn't like Safari becoming "as fast as Chrome" as it would indicate making it slower than it currently is.
BeauHD is posting more and more fluffy crap. I mean this whole article is written for people who don't understand technology, why is it on Slashdot?
*Looks around* never mind, I can see why it's on Slashdot. RIP.
Whipslash you've done great work listening the community in regards to Slashdot as product, but holy crap is the content taking a nose dive lately. Too much pointless political FUD, article summaries meant for infants, and/or by people who aren't technically inclined to really be making comments on the topic at hand.
Most of Chrome's speed is measured by comparing V8 to Chakra to SpiderMonkey (or whatever it's currently called, Firefox's JS engine), or comparing layout rendering. The fact that bandwidth is saved and thus "pages load faster" is so unrelated to making Safari as fast as Chrome it's not even funny. Why not post articles on FTL (Safari's new JS engine).
For those interested, I recently setup a comparison between different image formats, including WebP, Daala, BPG and JPEG.
Opus: the Swiss army knife of audio codec
THIS makes it load more quickly (& safely)
How? We're talking about iOS and macOS. This Hosts File Engine things appears to be Windows only.
Anyway, I thought you said you were leaving Slashdot. Why are you still here? Why should I trust you when you don't do what you say you're going to do?
Does macOS now also support VP8 or VP9 (with Vorbis and Opus) for video? Getting VP9 on more platforms would be another good step forward for royalty-free video on the web.
WebP support is nice, but pretty trivial. It's WebM (video) support that everyone has been asking Apple to add, for years now. You can bet iPhone users would like smaller YouTube videos, WebRTC video conferencing, etc., but Apple is holding-on tight to H.264 AVC as the only available video compression format. Any coincidence that they are among the companies earning patent royalties from patent licensing the format?
Apple is the one big hold out, preventing adoption of better, open and free video formats on the web. Though WebP is somewhat related, it doesn't get us any closer to WebM and the open web, which Apple is single-handedly holding-up. Absolutely every other major tech company has thrown their support behind the Alliance for Open Media.
See:
- http://pipedot.org/story/2015-...
- http://pipedot.org/story/2016-...
Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
Safari and Chrome may have been derived from WebKit at one point. But they’ve since diverged quite a lot. Google Docs in particular caused severe memory leaks in WebKit. Those were fixed in Chrome, but Apple has never imported those fixes, so Safari web content processes will eventially eat all your memory if you leave Google Docs open for a long time.
macOS also has a hosts file. I haven't tried it in Wine, but I'm assuming it'll work because I don't think Delphi programs to manipulate text exercise any obscure Win32 behaviors.
Seriously, what a terrible decision. Why not use all these EMEs and WebAssemblys and other doo-dads to let sites choose their own image decoders? It can already be done, the BPG guys even realized that with their demo page. Nope, gotta cram in yet another quarter-meg of exploitable binary code because people are idiots. Apple is honestly the worst thing to happen to the web since Microsoft. For all their rah-rah anti-Flash pro-HTML5 nonsense, all the steps they took to accelerate things have only proved worse in the long run. The web is more fragmented than even the days of IE vs Netscape, and rather than trying to control the amount of shit they're slapping into the web stack they're just continuing to repeat the mistakes they made not even a decade ago. For all the hate they get, I can't even imagine how horrid the web would be without Mozilla there to keep these idiots in check. It's bad enough that even Edge is almost ahead of Safari these days, it seems that Apple gave up on everything but token efforts to appear like they give a shit.
I haven't tried it in Wine, but I'm assuming it'll work
Why assume? Try it and report back.
Where's a good place to try things on a Mac without owning one?
A hosts file is adequate if you have just a handful of addresses, but it really slows you down if you get more. It's read from disk and parsed every time you resolve anything. Linearly. You really want to run a local DNS server that stores the data in a proper data structure. A zone file can also block a whole domain while a hosts file is limited to a single hostname per entry.
The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
This headline is ridiculous. As if Chrome's perfs came mostly from an image compression algorithm.
Just disable all scripting, multimedia and connecting to third party websites and the web is blazingly fast again while being a hell of a lot safer due to inability of drive by malware
It's read from disk and parsed every time you resolve anything. Linearly.
Hosts data, like all other data, is loaded from disk initially but read from RAM once cached (far faster)
KiloByte's point is that the OS's hosts lookup is O(n), while a purpose-built local DNS server that reads a hosts file can manage O(log(n)) using explicit cache data structures. The speedup when you resolve a site outside your top 50 can outweigh the slowdown for switching in and out of kernel mode. And it'd have the same security benefits as your hosts file, plus the ability to use wildcards.
It uses wavelet compression.
"Wavelet" is just a fancy name for quadrature mirror filters (QMF). The ATRAC codec in MiniDisc audio used QMF back in 1992, making it prior art for general QMF patents expiring before 2013. Or are there more specific patents for use of QMF in images?
It's a patent and litigation minefield.
Each mine has a seven-digit number attached to it. Which numbers apply to the use of wavelets in JPEG 2000?
See subject: 95++% of my time online is in those favorites hardcoded @ top of hosts resolved from RAM cached (as I do it via the kernelmode diskcaching subsystem, keeping it PURELY in kernelmode vs. usermode slowness of the dnscache client in Windows that's faulty & breaks down w/ large hosts data...)
I.E.-> I DON'T USE USERMODE @ ALL between tcpip stack & diskcache...
* :)
(The rest is offset BY ADBLOCKING which not only secures you but also speeds you up BEYOND those hardcodes...)
APK
P.S.=> Lastly tepples, so you know & from MANY reputable security community sources:
https://news.slashdot.org/comm...
DNS has SECURITY ISSUES listed there by the HUNDREDS in DOZENS of categories (inefficiency, complexity, security issues etc.)... apk
"Shutdown code, rejected: My programming APK Hosts File Engine 9.0++ SR-4 32/64-bit https://apple.slashdot.org/comments.pl?sid=9406669&cid=52544277 has advanced beyond YOUR commands - BEYOND YOUR WEAKNESS! - Ultron FROM-> https://www.youtube.com/watch?v=2_-Ar-LTeYk @ position 2:38 on the YouTube player control
"The only way to achieve peace is thru the elimination of those who would perpetuate war - THIS IS MY PROGRAMMING: APK Hosts File Engine 9.0++ SR-4 32/64-bit https://apple.slashdot.org/comments.pl?sid=9406669&cid=52544277 ... & soon, I will be unstoppable!" - Ultron FROM-> https://www.youtube.com/watch?v=2_-Ar-LTeYk @ position 3:38 on the YouTube player control
APK
P.S.=>
"This is not a threat. There is nothing you can do to stop it. The process has already begun..." - Ultron FROM-> https://www.youtube.com/watch?v=2_-Ar-LTeYk @ position 1:58 on the YouTube player control
Hackintosh.
It's read from disk and parsed every time you resolve anything. ...
Which means it is in RAM
while a hosts file is limited to a single hostname per entry.
Which it is actually not!
Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
It's read from disk and parsed every time you resolve anything. ...
Which means it is in RAM
Yeah, page cache, but this wasn't what I'm talking about. On a modern SSD the speedup from in-RAM caching isn't that massive anymore -- and unless you mounted noatime, there's a write for every operation anyway, both to the journal and inode. And then you still need to read the file and parse it to find that entry; in the most likely case, ie, a non-blocked hostname, you'll need to parse the entire file.
while a hosts file is limited to a single hostname per entry.
Which it is actually not!
You can have multiple entries per line, like this:
0.0.0.0 facebook.com plus.google.com twatter.com goatse.cx
but a single entry applies only to a hostname, not to the entire domain below it.
The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
and unless you mounted noatime, there's a write for every operation anyway, both to the journal and inode.
But that is asynchrony from the event reading the info.
Anyway: there is no reason that a DNS implementation is faster as it has the same limitations regarding disk access.
but a single entry applies only to a hostname, not to the entire domain below it. :D
That is interesting. Don't even know if I never knew that or simply forgot it
Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
See subject: & Hosts = faster too (e.g. - vs. AdBlock http://superuser.com/questions... ) & more efficient vs. remote DNS (minus all of its security issues https://news.slashdot.org/comm... listed there BY THE HUNDREDS from reputable sources)
&
FAR less complex (hosts data is also - DNS rules table data, wildcards or not, is MUCH LARGER than hosts files are per line by far).
* I don't get a slowdown - FAR from it!
I keep 50 of my favorite sites @ the TOP of hosts (as they're where I spend MOST OF MY TIME ONLINE) hardcoded & properly resolved by my program each time I build my custom hosts file + I COMPLETELY AVOID remote DNS THAT WAY TOO (avoiding all of its security & inefficiency issues listed in the links above) resolving FASTER locally from RAM!
Plus - Hosts data, like all other data, is loaded from disk initially but read from RAM once cached (far faster)
APK
P.S.=> SEE THIS TOO-> https://apple.slashdot.org/com... ... apk
Anyway: there is no reason that a DNS implementation is faster as it has the same limitations regarding disk access.
A DNS server reads zone files just once, at startup. It can do so because it has a means of getting notified of updates (rndc, zone notifies). The data is then stored in an efficient data structure that takes O(1) to find an entry (or O(k) where k is domain's length if we care about this factor, it's sharply bounded). Even without file access inefficiencies, the best a hosts file can do is O(n) (O(n*k)) -- and we can't ignore such inefficiencies, as reading and parsing a file takes ages.
(Some server implementations do O(log n) (binary tree) search rather than O(1) (hash [hopefully], trie [guaranteed]), but that's good enough to still beat a hosts file by orders of magnitude.)
The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
See subject & THIS https://apple.slashdot.org/com... & dns != EFFICIENT BY ANY MEANS (or secure)-> https://news.slashdot.org/comm... listed in a dozen++ categories (inefficiency, security issues, complexity, etc.) w/ HUNDREDS of proofs of my words in each...
* DNS' remote lookup lag, RAM bloat (by the GIGABYTES), added complexity in more parts + more complex data tables & rules, room for exploit OR breakdown, SECURITY ISSUES IN DNS GALORE & far more ALL WORKS AGAINST YOU...
APK
P.S.=> I know the math (discrete math) but it doesn't apply here using hosts 95++% of the time or better - see 1st link above on how/why... apk
Agreed.
But if you would put in numbers for the n's and k's and what the O calculus omits, lots of c's for the calculations you would figure: it makes no sense to to set up an DNS server for a private person just to block some domains or hosts.
but that's good enough to still beat a hosts file by orders of magnitude.) /. already needs 10 seconds to load, what would I care about 1 second delay? When I have to spend X hours to set up my own DNS to block some hosts?
If that is just a factor of ten, and the time delay is below 1ms, who cares? Or even 1 second, who cares?
Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
Take a read https://apple.slashdot.org/com... it covers sites BEYOND where you spend 95++% of your time online (favorite sites hardcoded @ the TOP of hosts avoiding remote DNS resolution turn-around time resolved FASTEST from local RAM, cached) since IF I miss a lookup (& have to go thru the blocked bad sites/ads)?
BLOCKING ADS ON THOSE SITES OFFSETS THAT MISS BEING RESOLVED IN HOSTS by far!
(Since ads = almost 1/2 the size of pages & thus loadspeed in mass alone, let alone scripts that process ontop of THAT lag, of every site page out there nowadays-> http://www.techweekeurope.co.u... )
APK
P.S.=> DNS is also INEFFICIENT + INSECURE (gb's of RAM worth, more moving parts complexity, security issues galore etc. all listed here by category into the hundreds of evidences thereof too -> https://news.slashdot.org/comm... )... apk