Alcro - Rust용 HTML5 Desktop 앱 개발 툴

 lorca와 같은 용도이며 rust를 위한 툴. 이름은 거꾸로(anagram)

https://github.com/Srinivasa314/alcro

Rust 학습을 동영상으로 시작

O'reilly에 있는 동영상으로 Rust가 어떤 언어인지 보고 있다.

Intro to Rust는 짧고 인상이 남게 특징을 설명해준다.

 Rust in Motion은 좀더 심화(?) 학습인데, 너무 빠르게 진행한다. 특히 Carol Nichols. 코드를 보면서 설명할 때는 여유있게 설명을 하면 좋겠다. 이미 아는 사람에게 말하는 것처럼 진행을 한다.

One Program Written in Python, Go, and Rust

https://www.nicolas-hahn.com/python/go/rust/programming/2019/07/01/program-in-python-go-rust/

Python, Go, Rust를 재밌는 글. Go와 Rust에 대한 특징을 잘 정리했다.

Static vs dynamic type system.

Somewhat like giving instructions to someone who always stops you to ask you to clarify what you mean, versus someone who always nods along and seems to understand you, though you’re not always sure they’re absorbing everything.

Rust

I also started with the book instead of just attempting to dive in headfirst. This was massively helpful, and probably the best introduction to any programming language I’ve ever experienced.

Haskell과 Rust에 대한 글

Haskell and Rust

https://www.fpcomplete.com/blog/2018/11/haskell-and-rust

몇부분 발췌.

Haskell works exceptionally well as an application language, especially for web applications and networked servers. Haskell has seen productive use in everything from financial technology to non-profit web platforms. We believe Haskell excels when you want to be able to maintain quality and maintainability without compromising developer productivity.

Rust is stronger for systems programming, embedded, game development, and high-performance computing. Rust is more reliably performant than Haskell, relying less on compiler magic and more on zero-cost abstractions. This emphasis means that the designers try to introduce as much programming convenience as possible where it won’t involuntarily reduce performance. Rust’s Iterators is an excellent example of this. Haskell tries to obtain some of these benefits with the use of developer-written rewrite rules which are notoriously brittle and hard to debug.

Haskell is going to be stronger when you need maximum productivity when going from a prototype to a production-ready system that can nimbly handle functional and infrastructural changes. Rust can be a better choice when you can plan a bit more and are willing to sacrifice some productivity for better performance or because your project requires a fully capable systems language.

더 읽을거리

• Summary of Haskell
• Summary of Rust
• Our blog posts on Haskell
• Our blog posts on Rust