git-credential-manager VS webrender

You can still use HTTPS, just not username/password as authentication. Personally, I think using HTTPS Git Credential Manager is simpler than SSH, as GCM allows you to use GitHub OAuth in your browser to sign in.

Hi, use git Credential Manager https://github.com/git-ecosystem/git-credential-manager been using it with Github and Azure Repo. Make sure that you update your machine global git config to use it.

Download Git for Windows and choose Git Credential Manager (GCM) as credential helper on the installation steps.

This is an application indepentend from git, so best use its channels. A quick search through their Github repo found this issue: https://github.com/GitCredentialManager/git-credential-manager/issues/899

Mathematically, what you want to do here is to calculate the area of the pixel square (or circle; however you want to approximate it) that the shape covers. In this case a linear ramp actually approximates the value better than smoothstep does. (I had the derivation worked out at some point; I don't have it handy, unfortunately.) Of course, beauty is in the eye of the beholder, and aesthetically one might prefer smoothstep.

By the way, since the article mentions ellipse distance approximations, the fastest way to approximate distance to an ellipse is to use a trick I came up with based on a paper from 1994 [1]: https://github.com/servo/webrender/blob/c4bd5b47d8f5cd684334... Unless it's changed recently, this is what Firefox uses for border radius.

[1]: http://mesh.brown.edu/taubin/pdfs/Taubin-tog94.pdf

That's something I was thinking a lot about back when I was working on Servo. Wasm + a protocol to talk to WebRender (expose display lists [0] to the wasm runtime). Some sort of "mini web", a minimal runtime that would do just enough that most web APIs could be re-implemented and shipped from the webpage directly. The DOM, the CSS parser, the layout engine, … could just be shipped as wasm modules.

Kind of defeat the purpose of view-source, but nowadays, it's kind of a lost battle already.

And I didn't think too much about sandboxing, network or whatnot. Just a fun idea…

[0]: https://github.com/servo/webrender/blob/c4bd5b47d8f5cd684334...

This source code:

https://github.com/servo/webrender/blob/master/wr_glyph_rast...

suggests to me that the glyph rasterization (which is the CPU-limiting factor for text rendering) in WebRender (which is the new FF 93+ GPU-accelerated rendering engine) is implemented in Rust and to be run on CPU.

Both Servo and Fifefox make use of webrender, which is an awesome piece of tech and is well suited to render a web page. Some GUI projects attempted to use webrender directly as well, like Azul and moxie-native

Surprised noone mentioned https://github.com/servo/webrender

Firefox article outlining which parts use Rust https://wiki.mozilla.org/Oxidation#Within_Firefox Servo/WebRender, the 2d renderer used by firefox: https://github.com/servo/webrender

Hi, what do you think about using webrender instead of wry on desktop? That is, instead of a full featured browser, just the bare minimum to render the DOM.

This is in the context of rust.

> it adds a line to a `go.sum` while with a hash of the code at the version specified

Cargo.lock also contains a checksum

> You can distribute your code without a copy of the dependency

Also true in rust, and the default way of using rust.

> If the hashes are different, an error is thrown.

Also true in rust.

For an example of what this looks like: https://github.com/servo/webrender/blob/54b725be37f13b166946...

You haven't described anything different between go and rust in your comment since every feature you've pointed out applies equally to both.

Yes! This is because web browsers use the platform text input stack

Browsers are a great example of cross-platform UI, because they sprinkle platform-native widgets throughout the canvas that they render. Which reminds me that people were trying to use webrender[1] to build native apps in Rust.

[1] https://github.com/servo/webrender