Conversation

I think putting Rust in here is *slightly* misleading, but that doesn't ruin the point. We have had certain vintages (1995 was one for sure, I think 2009-2010 counts too) where there's suddenly a bunch of languages, and then a long time between. When's the next one?

Quote Tweet

James Socol

@jamessocol

· Sep 16, 2021

Go, Rust, and NodeJS all came out within a year. Sometimes I wonder what problem is gonna push people to create a new batch of languages trying to solve it

steveklabnik

@steveklabnik

Sep 17, 2021

I would *like* to think that at least one of the thing that comes next is that someone solves the usability issues with dependent typing. I also don't really think someone *can* make better syntax for Rust that serves the same goals, but sometimes I wonder.

Brendan Zabarauskas

@brendanzab

Sep 17, 2021

dependent types + low level effects (like syscalls and memory alloc) + low level co-effects (like staging, uniqueness, linearity). that's what I want. oh and leverage dependent records for your module system, and base your ad-hoc polymorphism off that

steveklabnik

@steveklabnik

Sep 17, 2021

yeah i always forget about effects for some reason. that all sounds super great, yeah

Brendan Zabarauskas

@brendanzab

Sep 17, 2021

Yeah! I think there's lots of complexity in Rust that I think could maybe be compressed into a smaller number of foundational concepts.

Replying to

and

The way I described it above is admittedly a bit intimidating, but my hope that we can try to simplify and reduce the number of concepts into a smaller, tighter core. And figure out ways to make that accessible and teachable.

1:26 AM · Sep 17, 2021Twitter Web App

Likes