I love building a startup in Rust but wouldn't pick it again

Post by erik_seaberg » Fri, Feb 17, 2023, 7:16 PM UTC

wvenable wrote: post #58

nemothekid wrote: post #5

Earlier quoted context omitted.

I prefer having extra work done writing code (adding "?") than having to do extra work reading code. Exceptions are functionally invisible control flow; it isn't clear to the reader that a function may blow up if the exceptions are unhandled.

Assume all functions can throw and there is no extra work reading. A function that has no possibility of error is so uninteresting in the context of error handling. Furthermore, handling errors has little to do with where the error is actually caused. In general, you can only do two things with errors: log and kill the operation or retry the operation. Neither of these has anything to do with the leaf function 20 ite…

Post by steveklabnik » Fri, Feb 17, 2023, 7:17 PM UTC

lenkite wrote: post #201

estebank wrote: post #142

I find it surprising that so many people are arguing about the benefits and drawbacks of `?`, when in my experience the handling of Result and Option haven't been an issue in practice on the consuming side (`?`, `.unwrap()`, `.map()`, `.ok()`, if let, match, let chains, let else, etc. help a lot), but where all the pain comes from is having to declare the appropriate error type itself. Libraries like `anyhow` takes s…

All these workarounds for easier Result handling truly make me wonder whether Rust will eventually evolve exceptions as a feature - of-course without explicitly terming them so.

Post by marcosdumay » Fri, Feb 17, 2023, 7:19 PM UTC

RcouF1uZ4gsC wrote: post #38

Question for HN, all things being equal (you are not more familiar with one language/framework) what language would you choose to build a startup in?

Post by steveklabnik » Fri, Feb 17, 2023, 7:24 PM UTC

pdimitar wrote: post #181

estebank wrote: post #127

Earlier quoted context omitted.

> - bad error messages (even though that was a focus for the rust team!) I would love to hear more! (If you have the time.)

Not the fault of Rust compiler per se but in my case the errors that mismatching trait impls from async libraries yield can be downright suicide-inducing. I recognize this is not entirely on rustc though.

    pub async fn foo() -> i32 {
       unimplemented(); 
    }
    
    pub async fn bar() {
        let f = await foo();
    }

    error: incorrect use of `await`
     --> src/lib.rs:6:13
      |
    6 |     let f = await foo();
      |             ^^^^^^^^^ help: `await` is a postfix operation: `foo().await`

Post by justinclift » Fri, Feb 17, 2023, 7:24 PM UTC

throw14082020 wrote: post #216

dcow wrote: post #162

Earlier quoted context omitted.

> - Verbose. I've seen a just few lines of JS get replaced with hundreds and thousands of Rust. Please, more detail (=

I should've been clearer, sorry. The verbosity and complexity of `wasm_bindgen`/serialization between JS and Wasm (written in Rust) is primarily the thing I am frustrated at here when I see hundreds and thousands of Rust code. A concrete example: creating a Websocket client in Javascript/Typescript vs in Rust/Wasm. In general though (outside of Wasm), Rust is less readable. And with regards to Rust errors, I've found…