I’m extremely excited to be adding a new format to New Rustacean: discussing good crates in the Rust ecosystem. Suggestions wanted!
Started writing the script for the first “Crates You Should Know” episode of New Rustacean tonight. I’m pretty excited about adding this format to the repertoire.
One big personal upside to this documentation project: I’m going to know Rust a lot better before I’m done.
This is a great summary of what I enjoy about Rust: it just lets me get stuff done—quickly, usually elegantly, and it’s always speedy:
— nrc (@nick_r_cameron) December 30, 2016
A thing I just learned:
cargo doc --open: full, local docs for every dependency your Rust crate has.
Setting up AppVeyor for Lightning so I can be sure everything works cross-platform. 🎉 But for the record: batch files are barbaric. 👎🏼
This is fun: Lightning now loads the YAML configuration I defined. Doesn’t do much of anything with them, but it loads them!
(I’m developing Lightning totally in public, so you can follow along here.)
Just had my first experience of writing a lifetime-requiring function in Rust and inherently knowing exactly what lifetimes it needed.
One of the great joys in programming is when you start to feel even just a little bit fluent in a technology.
I keep trying to read documentation about templating engines in Rust and getting distracted by e.g. restyling rustdoc output.
(That’s not a thing that’s happening, though I’d happily chip in if it were, just a thing that distracted me. Web Inspector.)
Your friendly reminder that docs.rs is an incredible piece of software that is invaluable for working with Rust.
Spent a chunk of the afternoon figuring out how to implement Rust’s
Result type in TypeScript. Pretty cool!
Pro-tip for dealing with
HashMaps in Rust: the
entry API is often your friend.
Lots of compilers tell you “Foo is broken!” I love that both the Rust and Elm compilers try to explain why and how to fix it.
One of the things I most enjoyed working more on Lightning this weekend: the Rust compiler is so helpful.
Minor Rust surprise (though namespaces help):
std::fmt::Write are not the same (and for good reason).
Writing Rust just makes me super happy.
I’m simultaneously incredibly sad to be missing Rust Belt Rust and so relieved not to be traveling any more this year.
Spent a good chunk of the evening working on this static site generator—by contributing to another library. #opensource software FTW.
Discovered that Syntect can do highlighting for HTML as well as for editors. More Rust awesomeness.
It looks my options for HTML templating in Rust are… quite varied. This is good!
Curious: I noted during my drive back from vacation today that whenever other conscious thoughts lapsed, my Rust CMS project came to the fore.
My online writing needs are weird. I have searched for years, and unfortunately… I need to write a custom CMS.
I thought briefly about hammering together what I need with Metalsmith.io and its plugins. But that would be a stopgap.
So the inevitable comes to pass: I commit to, however slowly, build the CMS I need.
Probably in Rust—so it should be crazy fast.
Status: looking at C bindings for Pandoc and thinking about implementing a Rust wrapper for libpandoc vs. shelling out to pandoc. 🤔
First pass: just going to shell out on the command line. Second pass… well, if speed is what I’m going for…
I’ve guessed this for a while, but I can confirm it now: Clap is a really fantastic command-line argument library.
For posterity’s sake (ha!) it’s worth note that the original link here was to
lightning-rs. I actually noted as much, writing:
That repo name is for “Yet Another Static Site Generator (This One’s In Rust)” because I feel so creative today.
Note the headdesk-worthy initialism failure: it should have been
And, on evaluating that table… I need to pull about half of it out: too much code.
This morning I… carefully built a 3⨉16 table comparing Rust and Swift syntax. Exciting, right? 🤓
Wrote ~500 words and nailed down a chapter’s structure this morning. Good start to the day!
Wondering what it would take to build the Rust equivalent of Swift Playgrounds (which are like a REPL on steroids).
Playing Harmy’s Unspecialized Star Wars for my girls while I write some more this morning. 💕
I signed a contract today for a neat little writing project broadly related to my ongoing Rust and Swift series. Probably means a bit of a hiatus on the series itself, but there’s a lot of fun ahead. More on that as it develops.
Note to self: don’t forget to use the
--jobs flag when doing builds with Cargo. Parallel = faster when building a bunch of things.
I am trying to fix a bug in a Node.js back end I wrote 18 months ago. And I have never been so tempted in my life to rip out the entire Node back end and replace it with one written in Rust.
Things I did tonight:
So I love the Rust compiler (and it’s improving all the time). But the Elm compiler is a revelation. Just… wow.
Here I am, at the end of the week off, and what am I doing? Writing a Rust RFC. Yep.
Recorded another New Rustacean episode at last; it should be up this afternoon. Rust FTW!
And, me being me, this “news” episode ended up with a description of how the Rust compiler works. 🤓 It’ll post later!
Finally at a spot where I have both the time and the mental energy to pick back up my Rust and Swift series. Initializers, I’m coming for you.
Wrote the first draft of my RustConf 2016 proposal. Because I don’t skip chances to chat about Rust. Not ever. You know that by now.
This blog post on recent compiler work in Rust is incredible: great work, and great technical writing. 💙 Rust.
I 💙 the Rust team. So much.
Well, paper-writing today may have pushed me to the breaking point. An app idea that’s been bubbling for months… I think I’m going to start actually building pieces of it and learning for other bits this week.
I was reading some C++ yesterday, and I can’t put my finger on what it is about the language, but I just find it unbearably ugly. Rust’s syntax isn’t that different, but I don’t have the same visceral reaction. I wonder why that is?
I posted these as a series of tweets.
Fired up and played the demo for Elite Dangerous on my Parallels VM. Made me want to buy it. But of course, I’d prefer to play it natively.
Of course, it’s available for Mac. But my (more than a decade old) joystick doesn’t have any support on OS X. No drivers, full stop.
You can find software out there which recognizes it, of course—but it’s quirky and doesn’t behave well.
Looks like opportunity calling.
I might—might, I say, not will—end up seeing if I can write the requisite pieces in Rust. Because that seems like a good plan.
Spent the last little bit reading about Rust’s type system for the next episode of New Rustacean. Heady stuff.
This is interesting: I’ve read some F♯ before, but it reads a lot more obviously to me now that I’ve read a lot of Rust recently. Why? Because for all that they’re very different languages, both are ML descendants. It shows.
I’m writing a bunch of C that needs to handle error returns. I’m really wishing I had Rust’s
#[must_use] annotation right now. For that matter, I just want Rust’s
Result<T, E> type available.
Tonight, Jaimie said that she thought Rust had turned me into a bit of a fanboy. Don’t tell anyone, but I think she’s basically right…