chriskrycho

30 ms·

241.
by chriskrycho 10y ago
For the "right tool for the problem", you're right; really, see up-thread where someone posted the one-liner. For MSVC over MinGW/Clang: part of my point here was to first learn and then document for the community how yo
242.
by chriskrycho 10y ago
Or, you figure out the cross-compilation steps and document them for the whole Rust community , because there isn't yet a readily searchable resource on it. I actually knew exactly what I was doing with this, and it wasn't just
243.
by chriskrycho 10y ago
I've done a lot in those kinds of things, actually; they're awesome . I don't feel obliged to mention every possible alternative in every blog post; that would be absurdly tiring to do, and probably wouldn't add much va
244.
by chriskrycho 10y ago
It was an excuse to figure out the cross-compilation story with a tiny tool; he got his tool, I got my experience with a part of the Rust ecosystem I hadn't interacted with before. It was a win all around. (Note as well that I said exp
245.
by chriskrycho 10y ago
The author here: I agree with your assessment. Apparently the scare quotes didn't convey my intent: it's easy to do something (including cross-platform) where I normally would have used a traditional scripting language, and the po
246.
by chriskrycho 10y ago
My friend actually has the source code, so yes, he could do all of this. :) Also, worth note that these "twelve steps" are: - inclusive of literally everything including installing Rust and adding dependencies; this is like includ
247.
by chriskrycho 10y ago
For the record, as the author of the linked post… this is exactly what one "should" do for convenience in this situation. Compiling Python to exe from Mac to run on Windows is actually a lot of work, though it's doable (I&#
248.
by chriskrycho 10y ago
1. Of course it's over-engineered. 2. It wouldn't be a bash script; it would have to be batch or PowerShell, neither of which I know well, and neither of which I like. 3. It was fun.
249.
by chriskrycho 10y ago
Totally fair. I summed up that way because this is the kind of thing I'd have done with Python historically, and it struck me as neat that it's so easy to do with Rust. As someone pointed out on Reddit: this isn't really &quo
250.
New Rustacean Interview: Carol Goulding–first Rust Consultancy, TRPL Co-Author(newrustacean.com)
3 points by chriskrycho 10y ago|0 comments
251.
New Rustacean Bonus 7: Katas–or, learning by doing(newrustacean.com)
1 points by chriskrycho 10y ago|0 comments
252.
It doesn't have to be sexy: valuing things besides the compiler in Rust(newrustacean.com)
1 points by chriskrycho 10y ago|0 comments
253.
New Rustacean e017: Point me where I need to go(newrustacean.com)
1 points by chriskrycho 10y ago|0 comments
254.
by chriskrycho 10y ago
Do you combine and minify your code? If so, how—presumably a command-line tool? It's totally fine to say that you'd prefer to keep your dependencies fairly minimal, but pinning that on whether you use a CLI or not seems a false di
255.
RefCell and code smells–the Cell and RefCell types in Rust(newrustacean.com)
1 points by chriskrycho 10y ago|0 comments
256.
Interview with Raph Levien about Xi, Rust, data structures, and hacking history(newrustacean.com)
79 points by chriskrycho 10y ago|0 comments
257.
by chriskrycho 10y ago
Shameless plug that is directly related to the question: if you want a fairly detailed look at the two side by side, I've been comparing them as I work through learning both over the last 10 months. http://www.chriskrycho.
258.
One year and counting of Rust 1.x–including discussion of MIR compiler changes(newrustacean.com)
5 points by chriskrycho 10y ago|0 comments
259.
More important than open source contributions (New Rustacean Bonus 5)(newrustacean.com)
7 points by chriskrycho 10y ago|0 comments