Using Rust at a startup: A cautionary tale

Post by purplerabbit » Wed, Nov 23, 2022, 3:55 PM UTC

TranquilMarmot wrote: post #166

eyelidlessness wrote: post #104

Earlier quoted context omitted.

FWIW the “parse don’t validate” attitude which has become popular in TypeScript circles does this equally well. In Rust you’ll define the types you expect to deserialize as structs with Deserialize trait implementations, in TypeScript you’ll define a basic schema with runtime decoding and corresponding (inferred) static types. Like you say, maybe 45 seconds more typing, with the same value guarantees. I like that thi…

To me the greatest thing about TypeScript is that there are times that I absolutely know that something doesn't need to be extra safe or to have validation, and I can easily slap a `// @ts-expect-error` on it and either ignore it or come back and fix it later. I know some people think that's a horrible thing and sacrilege, but damn it if it makes it easy to move fast when you need to.

Post by jasonjmcghee » Wed, Nov 23, 2022, 4:22 PM UTC

Casperin wrote: post #251

jasonjmcghee wrote: post #188

Earlier quoted context omitted.

I've read and written a huge amount of python and rust, also a fan of rust and don't find it particular difficult to read. As long as there is proper linting, both should be readable. That being said, python is about the simplest language there is to read. Of course if you have many times nested and improperly indented list comprehensions- sure that gets confusing. But that should be fixed with proper linting (black…

I don't necessarily agree that Python overall is difficult to read, but one thing that seems to get my every time is the foo = x if y else z

  foo = y ? x : z

  foo = if (y) { x } else { z }

Post by insanitybit » Wed, Nov 23, 2022, 4:25 PM UTC

optymizer wrote: post #167

pclmulqdq wrote: post #68

Earlier quoted context omitted.

In my experience, Python is one of the least productive programming languages for projects with more than 3 people. If you have a big project, you are going to spend a lot more time reading code than writing it. Python is write-optimized. By contrast, using Rust makes it easy to force a readable coding style on yourself and others.

Python is not readable to you? The beginner friendly, whitespace-enforcing, almost-like-pseudocode-in-English language - that Python? - is not readable enough, but Rust, where you liberally sprinkle ', {}, !, &, :: or #[] everywhere _is_ readable to you? You must be trolling. You know what Rust looks like to me? Perl without the dollar signs. There's your write-only language, you just have it backwards.

Post by rsr » Wed, Nov 23, 2022, 4:51 PM UTC

Post by 3a2d29 » Wed, Nov 23, 2022, 5:29 PM UTC

arcticbull wrote: post #247

3a2d29 wrote: post #201

Earlier quoted context omitted.

You can find a GC language that does all those things that rust does but without: 1. The risk of future unsafety (a GC language will always safer than rust) 2. Faster development that's easier to change on a dime. 3. No risk of memory leaks (which can happen in safe rust)

> 1. The risk of future unsafety (a GC language will always safer than rust) [citation needed] > 2. Faster development that's easier to change on a dime. Yes, development can be faster at the expense of safety, which is a trade-off that favors the use of other languages at early company stages. Agreed here. > 3. No risk of memory leaks (which can happen in safe rust) ... at the expense of making collection non-determ…