dassurma
Joined 9 years ago
Karma
289
Submissions
63
Member since
Oct 15
[ my public key: https://keybase.io/surma; my proof: https://keybase.io/surma/sigs/FpZ-zMW2qZbl6VdJbyjr5mpkKqwQUuGIOsl8OMW6iSM ]
View on Hacker NewsRecent submissions
Comment · 4 years ago
I am not! I have no styles that should affect scrollbar visibility. What browser & OS are you on?
Comment · 4 years ago
The WebGPU spec is currently edited by two Google employees and one Mozilla employee. I am not sure how to make sense of your accusation.
Comment · 4 years ago
You can use the SPIR-V compiler toolchain to just transpile from GLSL to WGSL :)
Comment · 5 years ago
Hi! Squoosh team lead here :)
What kind of explanation would you like to see? We link to the repo and the Privacy explainer at the bottom of the page. Why is it important to you to know that it’s made by Googlers?
Comment · 5 years ago
The thing with GIF is that it’s rarely better than a paletted PNG.
As for animations, video formats with a very low fps are usually way better suited and smaller than GIFs.
Comment · 5 years ago
The goal of Squoosh is more to teach out about all the options and levers codecs have. JPEG is not “suggested”, it’s just literally the first codec we ported to Wasm so that’s the auto-selected one :D
The Squoosh CLI has an auto-optimizer that will make an image as small as possible while staying under a given Butteraugli threshold, but you still have to decide on the format yourself.
Comment · 5 years ago
<3
Comment · 5 years ago
Do you mean serve the app from an S3 bucket? It’s a fully static site without any server-side components, so go nuts.
If you mean compress all images in an S3 bucket? Not directly. But we do have a Squoosh CLI!
Comment · 5 years ago
The difficulty is:
Do you express the resulting file size or the amount saved? “30%” could mean you “30% of the original file size” or “you shaved off 30% of the original file size”. You could denote the difference with a sign, like “-30%” but that still confuses people. We ran both options by a lot of our colleagues.
“x% of the original file size” is the least ambiguous, but who has the space to put that entire phrase in their app :-/
Comment · 5 years ago
Yes, that is Jake. This is Surma.
You seem to be right. Gonna fix the CLI (the CLI is my doing)
Comment · 5 years ago
It _is_ cached, but the wasm binary itself as well as the optimized version to improve startup times. The cache however is per origin. So no other origin can make use of the cache which prevents the fingerprinting aspect.
Comment · 5 years ago
I did test that and maybe should have mentioned it in the article :) The repo history actually still has an RGBA buffer dump I think.
Comment · 5 years ago
Idk man. webassembly.org — the site authored by the inventors — literally starts with “WebAssembly (abbreviated Wasm) is a binary instruction format for a stack-based virtual machine.”
Comment · 5 years ago
That’s the whole point. V8 is _really_ good at taking any form of JS code and making it fast, without me having to apply optimizations. The other languages only started being competitive once I hand-optimized them.