Earlier quoted context omitted.
Is it fair to assume the actual task was more complicated than renaming .cha to .txt and you just made it more generic here for example's sake?
No, actually: it really was that simple, and I told my friend it was a super simple thing. I took the fact that it was so simple as an excuse to do the more complicated things alongside a very simple piece of code. That way, it's easy to see what the code does and then think about the implications of being able to run something like it (including something more complicated) cross-platform.
Using Rust for 'Scripting'
121–126 of 126 posts
Re: Using Rust for 'Scripting'
#122Earlier quoted context omitted.
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 including "install Python" and "pip install" for a Python tutorial. The point was to be approachable for anyone . I think it succeeded. - inclusive of the "copy the executable to hand to a friend"…
> It's almost like I was intentionally using this tiny project (which isn't especially interesting in its own right; as many have noted it's a one-liner batch file) to provide a one-stop shop for the basics of getting a cross-compiled setup with Rust. ;) That was my initial thought reading this. Even the most devout Rust enthusiast wouldn't go to this much trouble to avoid executing 'find' one would hope (yes, find d…
Re: Using Rust for 'Scripting'
#123One could probably get this done with one line of powershell code.
Re: Using Rust for 'Scripting'
#124Earlier quoted context omitted.
I am talking about scenario that "a friend" gives you binary to run. It is different from downloading software from a trusted source.
This is not a random friend giving you a binary. This is where you asked a trusted friend to build you a binary, and he delivered it.
Re: Using Rust for 'Scripting'
#125Earlier quoted context omitted.
> It's almost like I was intentionally using this tiny project (which isn't especially interesting in its own right; as many have noted it's a one-liner batch file) to provide a one-stop shop for the basics of getting a cross-compiled setup with Rust. ;) That was my initial thought reading this. Even the most devout Rust enthusiast wouldn't go to this much trouble to avoid executing 'find' one would hope (yes, find d…
Windows, remember? The OP is building a program on his Mac and sending it to his Windows-using friend. Windows has a "find" command, but it's a full-text search thing, unlike on *nix where it does find-by-name. See: http://www.computerhope.com/findhlp.htm
Re: Using Rust for 'Scripting'
#126Earlier quoted context omitted.
Big difference between "run a binary from me " and "run a binary from anyone "
Not really. It rather easy to assume someone's identity online and then make target person to run the binary without thinking twice, especially if such practice is already established.
So you just tell you friend "Only run a binary when I physically come over to your house with a USB drive" or "Only when I call you on the phone"