Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)R

robinm

@ robinm @programming.dev

Posts
2
Comments
133
Joined
2 yr. ago

  • Was Rust Worth It?. From JavaScript to Rust, three years… | by Jarrod Overson | Oct, 2023 | Medium

    Jump

  • I can totally understand the iterating speed due to higher cognitive load of a statically typed language, and non instant compilation.

    However I am very surprised about your refactoring experience. For me Rust is at least in a league of its own. In python/js I am terrified that I could break some unknown parts of my code whenever I touch anything. In C++ I fear that I just broke an invariants and made something UB. In all those languages, I expect regressions when I'm refactoring. But in Rust, even for large scale architecture changes if it compiles I'm quite certain that it's going to be easy to validate and often works the first try. What point points do you enconter that make your experience sub-optimal ?

  • Visual Studio Code is designed to fracture

    Jump

  • I need to re-try it. I really like like lsp/dsp are first class cityzen, including the keybindings, and that there is better text objects than in vanilla neovim. Last time I tried it there was a few things that where not that easy to set-up (I forget what), but I should definitively take the time to learn it.

    I just wish that neovim/kakoune/helix had a marketplace just like vscode. It make the discovery and installation so much easier when everyone use the same tools.

  • I'm impressed so far

    Jump

  • I didn't know about CACHEDIR.TAG, that's good to know. And yes, Rust tooling is stellar.

  • Thumb-Key 2.3.0 Release

    Jump

  • Nice! I'm waiting for #362 to be implemented before migrating away from messagEase, but it's really cool to see that this project is very alive!

  • This week in Rust # 515

    Jump

  • I definitively love llogic comments when he(she?) has no submitions for the quote of the week!

  • Safety vs Performance. A case study of C, C++ and Rust sort implementations.

    Jump

  • That was a fantastic read. I'm both impressed by the stellar performance of C, and the stellar safety of Rust while keeping nealy best in class performances.

  • The Absolute Minimum Every Software Developer Must Know About Unicode in 2023 (Still No Excuses!)

    Jump

  • I do understant why old unicode versions re-used “i” and “I” for turkish lowercase dotted i and turkish uppercase dotless I, but I don't understand why more recent version have not introduce two new characters that looks exactly the same but who don't require locale-dependant knowlege to do something as basic as “to lowercase”.

  • Progress Report #26: rustc_codegen_gcc can now compile Rust for Linux!

    Jump

  • Yes exacly. And I assume that the test suite of all of those project are long enough to average the usual jitter of wall time mesurement.

    What I'm hoping to see is if rust+llvm vs rustc+gcc binary speed are within a few percents or if there is a real difference between the two (I'm expected that we eventually reach the former once thinLTO and other optimisations are implemented).

    And while doing so it could also be possible to measure the difference in max RSS.

  • Progress Report #26: rustc_codegen_gcc can now compile Rust for Linux!

    Jump

  • Now that you can compile and run tests, how performant are they compared to rustc+llvm? I know that thinLTO is not yet enable, and I guess a few other important optimisation, but I'm interested to know what we can already get.

  • Progress Report #26: rustc_codegen_gcc can now compile Rust for Linux!

    Jump

  • This is incredible. Congrats!

  • Was async fn a mistake?

    Jump

  • I totally get the = async { body } (and I think I would prefer it for everything since it makes one liner like fn add(a: i32, b: i32) -> i32 = a+b much nicer and compact). I can also get the "ignore associated type” part. But I fail to see why removing the impl in -> impl Future is useful.

  • Sidechannel pixel-stealing attack works in Chromium on all modern GPUs

    Jump

  • Those side channels attacks are fascinating

  • Qualifying Rust without forking

    Jump

  • It's something that I never understood for other certified toolchain. What is a value of a certified toolchain containing known bugs, including critical and/or security bugs that are fixed upstream?

  • Qualifying Rust without forking

    Jump

  • What ferrous systems does is trully great!

    And throwing out an online birthday party is a nice idea. See you there.

  • Platform that enables Windows driver development in Rust

    Jump

  • With both Linux and Windows actively using Rust, it really seems that this language has proved its qualities.

  • Linux Terminal Emulators Have The Potential Of Being Much Faster

    Jump

  • Just toebe sure, what's the name of this new terminal emulator? termkit?

  • Thumb-Key 2.1.0 Release

    Jump

  • That's very nice! I really hope that at one point, thumb-key will be able support circle and back-and-forth gesture. That's the only thing blocking me from migrating from messagEase.

  • When a Programmer Holds the Code Hostage: The costs of a policy of appeasement

    Jump

  • That's true. But at least you will have evidence that Martin doesn't conform to the team rules.

  • Linear code is more readable

    Jump

  • One way to make it obvious which function can be called at which state is to use different type. Like UnbackedPizza and CookedPizza, and the bake function takes the former and returns the later.