Conversation

You do eventually start hitting the corners that could be seen as regrettable. But despite that I do still feel reasonably happy writing it in my day job and spare time, and it affords tremendous leverage when it's at its best. An important language to study and use.

Quote Tweet

Yosh

@yoshuawuyts

· Feb 6, 2018

I like Rust a lot as a language. It's such a carefully crafted system. It's true that there's a lot of complexity tho; but a lot of it feels like it stems from careful delibaration, and not some weird spec accident. _very_ excited.

Yosh

@yoshuawuyts

Feb 7, 2018

Ohh curious! What kind of corners do you hit?

Brendan Zabarauskas

@brendanzab

Replying to

@yoshuawuyts

- Naming of `String`/`str` - separate value/type syntaxes (ugly dependent type retrofit) - lack of an effects system, leading to (futures context controversy & surprising panics) - outcome of mutpocalypse - `=` vs `:` for struct field inits - Hash API performance - more...?

12:48 PM · Feb 7, 2018Twitter Web Client

Replying to

hah, thanks for sharing! Yeah, I can already relate to some of these. Curious to see the fun ways in which I'll run into some of the others haha :D

Brendan Zabarauskas

@brendanzab

Feb 7, 2018

Cool! Just trying to be honest about a language I love! As I say, it's one of the better ones out there, and it's production ready, has a healthy ecosystem, and pretty easy to deploy for *most* things, so those are big bonus points aside from raw feature lists.

Replying to

and

Some of these were to lack of 'innovation points' and lack of research at the time. In the end you have to ship. It's up to future languages to experiement with the design space - there's still lots to explore.

@ollfredo

's github.com/ollef/sixten is interesting, for instance.