> Given these positive signals, we would welcome contributions to integrate a performant and memory-safe JPEG XL decoder in Chromium. In order to enable it by default in Chromium we would need a commitment to long-term maintenance. With those and our usual launch criteria met, we would ship it in Chrome.
That conversation doesn't apply to their core products: Search, Mail, Maps, Chrome, Android. Their commitment to maintaining these services over decades has been amazing. It's everything else that sucks.
I asked it to analyze my tennis serve. It was just dead wrong. For example, it said my elbow was bent. I had to show it a still image of full extension on contact, then it admitted, after reviewing again, it was wrong. Several more issues like this. It blamed it on video being difficult. Not very useful, despite the advertisements: https://x.com/sundarpichai/status/1990865172152660047
I’ve never seen such a huge delta between advertised capabilities and real world experience. I’ve had a lot of very similar experiences to yours with these models where I will literally try verbatim something shown in an ad and get absolutely garbage results. Do these execs not use their own products? I don’t understand how they are even releasing this stuff.
Whoa, you can now search clipboard history. Go to Spotlight Search, Command+4. You'll get a list of entries, each with a copy button, and is searchable. Even shows the app it was copied in.
Either way, I think it is better to not copy passwords to the clipboard or the selection, but store and transfer them via password-manager/browser/etc APIs.
And seriously, managers like 1Password clear the clipboard after some time. I would guess that there’s some clipboard API that allows managers to exclude copied passwords from being permanently added to the history.
Still, there are pieces of data that one might not want to store in such unobvious place as clipboard history so it’s good to know about it.
I use KeePassXC which does empty the keyboard after a few seconds. But keeping history seems like a breaking change to the social (if not technical) contract of the OS' clipboard API.
Yeah, it's very unfortunate for WebGL/WebGPU apps, where every call has to pass/convert typed arrays and issue a js gl call. It pretty much kills any advantage of using WASM. Hope that changes.
How can you reconcile this with all of the AAA games that have been shown to work well on Wasm+WebGL ? What is different between your usage and theirs?
