nfrmatk
Joined 12 years ago
Joined 12 years ago
No one is forcing you to learn Rust. You don't have to bring yourself spend time learning it. You can keep writing those other languages.
Those languages have been around for a while and they'll continue to be around for a while more. Rust is just getting some time on that stage as well now.
From my vantage point their work fits the definition nicely.
"A collective body" [1] ... "Collectivized or characterized by collectivism" [1] ... "A political or economic theory advocating collective control especially over production and distribution" [2]
[1]: https://www.merriam-webster.com/dictionary/collective [2]: https://www.merriam-webster.com/dictionary/collectivism
This blog post is just a personal journey winding through the thought process it took to replicate that PHP in Rust, something I did because I thought I might learn something.
I have been thinking about and trying to work with this paradigm for a few years now. To be honest, it's been a struggle. Partly because it requires unlearning some habits and partly because there's limited opportunity to practice in my $DAYJOB where I'm working in codebases heavily invested in other paradigms.
I've seen and read many, many videos, blog posts, etc. on this topic. Everyone loves to introduce the concept with a contrived example and then stop there. What I would love to see more of are complete examples for everything from simple to complex applications.
I think there's potentially a lot of value in thinking this way (or at least taking as much from it as you can), but it's hard to learn and then to teach others without more examples to draw on.
I try to keep it simple, HTML, Sass (but really just vanilla CSS), and no JS. I generate the site with Zola (https://www.getzola.org/), which has been fantastic. Nothing fancy here, probably write a post once a year, but I have fun doing so.