home.social

Search

1000 results for “hywan”

  1. A Function Inliner for Wasmtime and Cranelift, fitzgen.com/2025/11/19/inliner.

    A great article about the new function inliner inside Cranelift. The article mentions a nice algorithm to partially keep parallelism during the compilation time for the inliner (that’s the most interesting part).

    #compiler #cranelift #WebAssembly

  2. What We Learned from the Recent Mandrill Outage, mailchimp.com/what-we-learned-.

    Mailchimp encountered a database failure. This is the story of how they have fixed it.

    #database #Postgres #outage #MailChimp

  3. Who needs Graphviz when you can build it yourself?, spidermonkey.dev/blog/2025/10/.

    SpiderMonkey has replaced Graphviz by a custom graph layout renderer for their internal devtools. This article explains how the algorithm works, step by step (inspired by Sugiyama et al.'s algorithm, used by Graphviz, but simplified and with more constraints).

    Pretty neat!

    #SpiderMonkey #graph #layout #DevTools #compiler

  4. Who needs Graphviz when you can build it yourself?, spidermonkey.dev/blog/2025/10/.

    SpiderMonkey has replaced Graphviz by a custom graph layout renderer for their internal devtools. This article explains how the algorithm works, step by step (inspired by Sugiyama et al.'s algorithm, used by Graphviz, but simplified and with more constraints).

    Pretty neat!

    #SpiderMonkey #graph #layout #DevTools #compiler

  5. Who needs Graphviz when you can build it yourself?, spidermonkey.dev/blog/2025/10/.

    SpiderMonkey has replaced Graphviz by a custom graph layout renderer for their internal devtools. This article explains how the algorithm works, step by step (inspired by Sugiyama et al.'s algorithm, used by Graphviz, but simplified and with more constraints).

    Pretty neat!

    #SpiderMonkey #graph #layout #DevTools #compiler

  6. Who needs Graphviz when you can build it yourself?, spidermonkey.dev/blog/2025/10/.

    SpiderMonkey has replaced Graphviz by a custom graph layout renderer for their internal devtools. This article explains how the algorithm works, step by step (inspired by Sugiyama et al.'s algorithm, used by Graphviz, but simplified and with more constraints).

    Pretty neat!

    #SpiderMonkey #graph #layout #DevTools #compiler

  7. Who needs Graphviz when you can build it yourself?, spidermonkey.dev/blog/2025/10/.

    SpiderMonkey has replaced Graphviz by a custom graph layout renderer for their internal devtools. This article explains how the algorithm works, step by step (inspired by Sugiyama et al.'s algorithm, used by Graphviz, but simplified and with more constraints).

    Pretty neat!

    #SpiderMonkey #graph #layout #DevTools #compiler

  8. Looking for LED bulbs with white colour (daylight, 5000-6500K) and with a high CRI (>90). Any recommendations?

    #LED #CRI

  9. Faster linking times with 1.90.0 stable on Linux using the LLD linker, blog.rust-lang.org/2025/09/01/.

    tl;dr: rustc will start using the LLD linker by default on the `x86_64-unknown-linux-gnu` target starting with the next stable release (1.90.0, scheduled for 2025-09-18), which should significantly reduce linking times.

    #RustLang #linker

  10. Sunsetting the `rustwasm` Github org, blog.rust-lang.org/inside-rust.

    Active and important projects like `wasm-bindgen`, `walrus`, `weedle`, `wasm-pack`, `twiggy` etc. are moved into either their own organisation, or the maintainer's account, e.g.:

    * github.com/wasm-bindgen/wasm-b
    * github.com/drager/wasm-pack
    * github.com/AlexEne/twiggy

    #RustLang #WebAssembly #RustWasm

  11. Beeper.com allows to use multiple messaging accounts in a single app.

    Behind the scene, a Beeper account is a Matrix account, and it uses Matrix bridges to connect to other networks. Alrighty, classic.
    But you can’t use your Matrix account inside Beeper. I repeat: you can’t connect to Matrix. But it’s Matrix!! It’s the simplest case.

    I’m really disappointed.

    #matrix #beeper

  12. Ordering Numbers, How Hard Can It Be?, orlp.net/blog/ordering-numbers/.

    Well. Ordering numbers from different types (like i32 and u32) can be error-prone and not that trivial.

    #computer #arithmetic #ordering

  13. Ordering Numbers, How Hard Can It Be?, orlp.net/blog/ordering-numbers/.

    Well. Ordering numbers from different types (like i32 and u32) can be error-prone and not that trivial.

    #computer #arithmetic #ordering

  14. Ordering Numbers, How Hard Can It Be?, orlp.net/blog/ordering-numbers/.

    Well. Ordering numbers from different types (like i32 and u32) can be error-prone and not that trivial.

    #computer #arithmetic #ordering

  15. Ordering Numbers, How Hard Can It Be?, orlp.net/blog/ordering-numbers/.

    Well. Ordering numbers from different types (like i32 and u32) can be error-prone and not that trivial.

    #computer #arithmetic #ordering

  16. Ordering Numbers, How Hard Can It Be?, orlp.net/blog/ordering-numbers/.

    Well. Ordering numbers from different types (like i32 and u32) can be error-prone and not that trivial.

    #computer #arithmetic #ordering

  17. A valid HTML zip bomb, ache.one/notes/html_zip_bomb by @ache

    The article shows how to create an HTML zip bomb for AI crawlers not respecting the `robots.txt` file.

    A zip bomb is a huge file (like 10Gib), that once compressed, has a reasonable size like 10Mib. An AI crawler will uncompressed it and will see all its memory being consumed, leading to a possible crash.

    That’s an effective way to counter-attack disrespectful AI crawlers.

    #html #ZipBomb #ai

  18. `uutils/coreutils` 0.1.0 has been released, github.com/uutils/coreutils/re.

    It took me a moment to share the news but it’s a good news!

    `uutils/coreutils` is a cross-platform reimplementation of the GNU `coreutils` in Rust.

    > This release brings major performance gains, SELinux support, and expanded GNU compatibility.

    #gnu #RustLang #utils

  19. `uutils/coreutils` 0.1.0 has been released, github.com/uutils/coreutils/re.

    It took me a moment to share the news but it’s a good news!

    `uutils/coreutils` is a cross-platform reimplementation of the GNU `coreutils` in Rust.

    > This release brings major performance gains, SELinux support, and expanded GNU compatibility.

    #gnu #RustLang #utils

  20. `uutils/coreutils` 0.1.0 has been released, github.com/uutils/coreutils/re.

    It took me a moment to share the news but it’s a good news!

    `uutils/coreutils` is a cross-platform reimplementation of the GNU `coreutils` in Rust.

    > This release brings major performance gains, SELinux support, and expanded GNU compatibility.

    #gnu #RustLang #utils

  21. `uutils/coreutils` 0.1.0 has been released, github.com/uutils/coreutils/re.

    It took me a moment to share the news but it’s a good news!

    `uutils/coreutils` is a cross-platform reimplementation of the GNU `coreutils` in Rust.

    > This release brings major performance gains, SELinux support, and expanded GNU compatibility.

    #gnu #RustLang #utils

  22. `uutils/coreutils` 0.1.0 has been released, github.com/uutils/coreutils/re.

    It took me a moment to share the news but it’s a good news!

    `uutils/coreutils` is a cross-platform reimplementation of the GNU `coreutils` in Rust.

    > This release brings major performance gains, SELinux support, and expanded GNU compatibility.

    #gnu #RustLang #utils

  23. Magic Completions in `rust-analyzer` (a Language Server Protocol implementation for Rust), rust-analyzer.github.io/book/f.

    - `expr.if` expands to `if expr { }` or `if let … { } ` for `Option` or `Result`
    - `expr.dbg` expands to `dbg!(expr)`
    - `expr.match` expands to `match expr { … }`
    - `tmod` expands to `#[cfg(test)] mod tests { use super::*; #[test] fn test_name() { } }`

    #RustLang #LSP #completions

  24. Magic Completions in `rust-analyzer` (a Language Server Protocol implementation for Rust), rust-analyzer.github.io/book/f.

    - `expr.if` expands to `if expr { }` or `if let … { } ` for `Option` or `Result`
    - `expr.dbg` expands to `dbg!(expr)`
    - `expr.match` expands to `match expr { … }`
    - `tmod` expands to `#[cfg(test)] mod tests { use super::*; #[test] fn test_name() { } }`

    #RustLang #LSP #completions

  25. Magic Completions in `rust-analyzer` (a Language Server Protocol implementation for Rust), rust-analyzer.github.io/book/f.

    - `expr.if` expands to `if expr { }` or `if let … { } ` for `Option` or `Result`
    - `expr.dbg` expands to `dbg!(expr)`
    - `expr.match` expands to `match expr { … }`
    - `tmod` expands to `#[cfg(test)] mod tests { use super::*; #[test] fn test_name() { } }`

    #RustLang #LSP #completions

  26. Magic Completions in `rust-analyzer` (a Language Server Protocol implementation for Rust), rust-analyzer.github.io/book/f.

    - `expr.if` expands to `if expr { }` or `if let … { } ` for `Option` or `Result`
    - `expr.dbg` expands to `dbg!(expr)`
    - `expr.match` expands to `match expr { … }`
    - `tmod` expands to `#[cfg(test)] mod tests { use super::*; #[test] fn test_name() { } }`

    #RustLang #LSP #completions

  27. Magic Completions in `rust-analyzer` (a Language Server Protocol implementation for Rust), rust-analyzer.github.io/book/f.

    - `expr.if` expands to `if expr { }` or `if let … { } ` for `Option` or `Result`
    - `expr.dbg` expands to `dbg!(expr)`
    - `expr.match` expands to `match expr { … }`
    - `tmod` expands to `#[cfg(test)] mod tests { use super::*; #[test] fn test_name() { } }`

    #RustLang #LSP #completions