this lets you implement `std::error::Error`, which you really should to make it less painful when you want to erase the type (`std::error::Error` is `dyn`-compatible)
345 karma · joined August 28, 2023
https://bsky.app/profile/did:plc:z2dxz4qxqnye24swc7g3lgz3 https://tangled.org/did:plc:z2dxz4qxqnye24swc7g3lgz3
this lets you implement `std::error::Error`, which you really should to make it less painful when you want to erase the type (`std::error::Error` is `dyn`-compatible)
for inline SVG, i read somewhere you can use <title> and <desc> to describe the SVG document, but i don't know how they work in practice
i don't really see any reason to use GIFs here; any widely available video codec like H.264, VP8/VP9 or AV1 will result in significantly smaller file sizes, look better, and will allow enabling controls for seeking and play/pause
Is there even a human at any step or is this an agent running in the background with "go to HN front page" as its ultimate goal?
When it receives a post, it creates a row in the Post table. When it receives a comment, it creates a row in the Comment table, which has a column pointing to the Post it's replying to. Then, getting all comments under a post is easy SQL.
About your second question: yes, you're correct. What handle you use and where your data is hosted are completely separate matters.
https://hacks.mozilla.org/2018/10/calls-between-javascript-a...
As much as Mozilla and Firefox can be criticized for both technical and non-technical reasons, at least I share the same core values. I don't seem to share any core value with Brave or its creator. Plus, yeah, still smells like Google :)
But if Evan Wallace didn't obsess over performance when building Figma, it wouldn't be what it is today. Sometimes, performance is a feature.
Unlike passwords, you can have multiple passkeys per account. You can have 5 passkeys for your amazon account if you use your amazon account on 5 different devices. If you lose device 4, or if it gets stolen, you can just delete passkey 4. The other ones are safe.
Or, you can use a syncing service like a password manager. Both solutions work!
Most browsers with fingerprint protections will for example introduce random noise in graphics and audio APIs.
Lossless video would make much more sense for digital content like screen recordings, where the assumption that few pixels change between consecutive frames makes much more sense.
cargo install --locked miniserve
miniserve path/to/directory
[1]: https://github.com/svenstaro/miniserve> This post is my personal opinion, not necessarily representative of Servo or my colleagues at Igalia.
...so I don't believe it's fair to say that you lost all the good will you had for Servo based on just this article.
Ubj vf guvf n ceboyrz gubhtu? Vg qbrfa'g frrz gb ivbyngr nal bs gur shapgbe ynjf!
I worry about this. The built-in mobile operating system components are reliable, accessible, and responsive. I really like it when an input element opens the Android UI because I know how it works and that it is reliable. This applies to <select>, but also date/time inputs for example.
> Form Components Are Uncontrolled by Default, Which Can Cause Issues > [...] > What happens if you remove the bind? One-way binding? No, it only sets the initial value, then the input's internal state takes over, contrary to expectations.
I strongly disagree. This is literally how HTML works. This makes forms with default values MUCH less awkward to author.
IMO, you can even skip having a theme switch—that's how native stock OS apps behave (calculator, notepad, settings, etc.).
For websites, I think that should be enough. For web apps however, you might want more control over the theme somewhere in the settings page, as people are more likely to spend a lot of time in your app and may want to customize it a bit more.