fasterthanlime

9 ms·

91.
by fasterthanlime 5y ago
As others have noted, that's just how I write articles. More specifically, I have an end goal in mind, and to get there I need to establish a scene: make sure that we share a lot of context so that we can consider a problem together fr
92.
by fasterthanlime 5y ago
(Author here) Absolutely! I love TypeScript and refuse to write JavaScript without it (even just in JS-checking mode with jsdoc annotations), but I'm already fighting, like, 4 different battles in that article, I didn't want to br
93.
by fasterthanlime 5y ago
Yes! Any "rich text formatting" in text elements is lost: there's no line wrapping (it adds an ellipsis in some cases?), the sizes are wrong, there's no italics, no bold, no color.. all of that is achieved with HTML mark
94.
by fasterthanlime 5y ago
Hey David, thanks for draw.io/diagrams.net and I hope you liked the article! I've found both of these before attempting any of this (I think you linked them to me on Twitter?), but was happy with neither of them: the point was to
95.
by fasterthanlime 5y ago
Seems like you really need to finish reading the article: hot builds take 3s by the time I find the regression that caused pathological compile times.
96.
by fasterthanlime 5y ago
A very short online search would be enough for you to find out the extent to which you are wrong about that last statement, in case you're interested in facts!
97.
by fasterthanlime 5y ago
Driving right past the snark to point you at https://github.com/dvcrn/markright , whose author recently contacted me, and is going for something really similar to what I've tried to describe in my article. Markrigh
98.
by fasterthanlime 5y ago
Compile/link times are definitely a discussion topic. Here's some quick tips: * Incremental compilation helps locally, not so much in CI, unless you save/restore the whole cache which gets large quickly and evicting the o
99.
by fasterthanlime 5y ago
"Simple" can mean many things. For me Rust is "simple" because it has great tooling / great diagnostics, so when I get something wrong, most of the time it can tell me exactly what it is (and how to fix it!), and on
100.
by fasterthanlime 5y ago
Ok I promise I'm going to stop replying to those comments (because as you pointed out they show up on every post), but! Rust is not the only language with a decent type system out there. I can definitely see some ML/Haskell/S
101.
by fasterthanlime 5y ago
Not to worry, we also spend some time messing with strace and GDB. I see it more as "giving a working knowledge of Rust" than a distraction. Some of these crates/tools are lifechangers, I wouldn't want folks to miss out
102.
by fasterthanlime 5y ago
I've added a link to the PR directly in the article to clear up the confusion!
103.
by fasterthanlime 6y ago
https://caniuse.rs/ is very good.
104.
by fasterthanlime 6y ago
It's sometimes called a type-level boolean. Instead of trying to remember what true or false means, you have explicit variants associated with success or failure. (The underlying representation, including bit width, is the same)
105.
by fasterthanlime 6y ago
Libraries can be (and some actually are) designed with that in mind, with COW (copy on write( types that can be either borrowed or owned. Speaking of performance, kstring (of liquid) goes one step further with inline variants for short stri
106.
by fasterthanlime 6y ago
Since a lot of folks take issue with the article's title, think of it as "If you had only a half hour to learn Rust, here's what I'd tell you". If you have more, do engage in a joust^W friendly collaboration with th
107.
by fasterthanlime 6y ago
I'd argue the exact opposite. Languages that don't have a concept of ownership, and a borrow checker, and don't explicitly say if they want ownership, a reference, or a mutable reference, force you to keep all of these deta
108.
by fasterthanlime 6y ago
Yup, strong similarities there, since the original Rust compiler was implemented in OCaml :)
109.
by fasterthanlime 6y ago
That's one of the things that get me about Rust discourse: it seems that "Rust is pain in exchange for performance" is a common misconception. Rust is discipline in exchange for performance and correctness . A GC lets you be
110.
by fasterthanlime 6y ago
This may answer part of your question — it's focused on strings but draws parallels with C all along: https://fasterthanli.me/articles/working-with-strings-in-rus...
111.
by fasterthanlime 6y ago
The closest I've written is this: https://fasterthanli.me/articles/getting-in-and-out-of-troub... but it explicitly seeks the complicated bits because elucidating those is the whole point of the article. I might w
112.
by fasterthanlime 6y ago
I wrote a piece that tries to explain Rust's memory management strategy, compared to C: https://fasterthanli.me/articles/declarative-memory-manageme... Hope it helps!
113.
by fasterthanlime 6y ago
Sarcasm aside, the Rust compiler has gotten a lot faster (and parallelizes better) over the last year thanks to Nicolas Nethercote and others. Another thing few people realize is that the "incremental" compilation mode that's
114.
by fasterthanlime 6y ago
Yep, code is a lot of "words" which throws off the estimate. I need to address this, but I don't think completely ignoring code blocks is really the solution there.
115.
by fasterthanlime 6y ago
I have a lot of Rust articles[1] that go into a lot more depth. They're mostly adventures though, we learn about ICMP, ELF, file systems etc. Some love that style (the detours, the stream of consciousness) and some can't stand i
116.
by fasterthanlime 6y ago
It's definitely a lot to take in, you have the right idea — the compiler is here to help, the diagnostics are wonderful and improving every week thanks to the work of Esteban Kuber and others. Re macros: try to keep an open mind if you
117.
by fasterthanlime 6y ago
(That's unproven. Has anyone ever seen the both of us in the same room together?)
118.
by fasterthanlime 6y ago
It definitely takes up a good chunk of time, but it's worth it! It's not that bad once you learn the keyboard shortcuts. I thought about going the "declarative / adhoc tool" way but I make lots of different diagram
119.
by fasterthanlime 6y ago
This used to be true — until June 2020, as that website noted. It's all custom now, and closed source, since I want to focus on writing rather than maintaining an OSS project that fits everyone's needs
120.
by fasterthanlime 6y ago
The most recent ones I've found were https://github.com/hjl-tools/x86-psABI/wiki/X86-psABI which have now been moved to GitLab and no longer have pre-built PDFs? It's a hard "standard" to

More ›