It makes me wonder if the language itself is too complex. Not in terms of the learning curve, but in understanding the ramifications of each design decision you make, and how they affect the codebase, and the project more broadly. What makes me sad is that this line of thought destroys my confidence in Rust, or at least in my ability to use it as a tool. That if I had to write some critical code 'in anger' that I would be better off reaching for Go or Java rather than for Rust. [2/2]
I started learning Rust at the end of 2016. And even today there are many aspects I really value and enjoy, from reading and writing the language, to the community, tooling, philosophy, and design decisions. After all this time though I still find myself struggling to 'write Rust in anger'. When it comes down to the wire. When there's business at stake. When you just need to deliver some tangible value from the software you put out there. I keep finding Rust getting in the way. [1/2]
Happy new year folks. Sure, time is a construct and time will continue to flow on but my brain makes this weird separation between segments of 365 (sometimes 366) days and I feel compelled to wish you all well for the coming 365 days.
Read this and watch the video in there too. Don't do resolutions. Resolutions bad.
For all their problems, I'd like to thank computers for giving us a glimpse of a better world.
A bright and colorful world of overwhelming abundance. A world in which we all have superpowers.
A world in which we are free to be ourselves. A world in which we can find others we want to be with, and keep others who are toxic to us away.
The dopamine we get from interacting with this better world is not fake. A better world can be addiction-forming of course, like food. Who wouldn't want more?
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.