Why Go and Not Rust?

Re:Why Go and Not Rust? by slifin on Monday September 16, 2019 @12:21PM (#20985667)

Rich Hickey describes simple as unbraided, like a class is identity, state and schema all braided together

And easy as close by and accessible i.e. npm i latest-framework might be easy but not simple

https://www.infoq.com/presentations/Simple-Made-Easy/

[ Parent | on HN ]

Re:Why Go and Not Rust? by modwest on Monday September 16, 2019 @04:57PM (#20988529)

This presentation had an outsize influence on my professional development as a programmer. If I've watched it once (and I have), I've watched it a dozen times.

edit: The "Limits" slide (go to 12:30 in the vid) is one that I really internalized early on. And looking at it again years later, the principles from that slide absolutely guide my app development:

- We can only hope to make reliable those things we can understand

- We can only consider a few things at a time

- Intertwined things must be considered together

- Complexity undermines understanding

[ Parent | on HN ]

Re:Why Go and Not Rust? by setr on Monday September 16, 2019 @12:36PM (#20985839)

isn't the same idea exactly covered by the term "(de)coupled"?

[ Parent | on HN ]

Re:Why Go and Not Rust? by modwest on Monday September 16, 2019 @04:40PM (#20988348)

It can include decoupling, but no it's not synonymous.

[ Parent | on HN ]