Svetlitski

12 ms·

91.
by Svetlitski 5y ago
I would argue that "the easy parts" of cp account for a very significant fraction of its usage (i.e. copy some files/directories without any other options). The idea with fcp is to make that common use case very fast, not to
92.
by Svetlitski 5y ago
Sounds super interesting, I'll definitely check out the blog post. Yes, fcp is indeed using blocking io in threads. In an earlier prototype I was using async (i.e. M on N threading), but was running into issues with exhausting file des
93.
by Svetlitski 5y ago
This was definitely an oversight on my part; the benchmarks I ran were all conducted on systems with SSDs (as noted in the README). Especially considering the testing done in some of the comments below this one, I'll update the README
94.
by Svetlitski 5y ago
No, it isn't. My motivation for running on EC2 was that benchmarking on a laptop is somewhat noisy due to thermal constraints [1]. I specifically used a bare-metal EC2 instance in an attempt to have a less noisy environment (since VM p
95.
by Svetlitski 5y ago
The primary reason is that it uses all of your computer's available cores to walk through directories and copy files, effectively speeding things up by a factor directly proportional to how many cores you have. On macOS, this is augmen
96.
by Svetlitski 5y ago
Good question. I've already shut down the EC2 instance I used for testing, but I'll fire up another one later today and get back on this. Great point though, performance characteristics will almost certainly vary quite a bit betwe
97.
by Svetlitski 5y ago
Inspired by many of the amazing new-wave Unix tools that have come about over the past several years (fzf, ripgrep, fd, lsd, etc.), I set out to create a more modern and performant version of the classic Unix cp command. Written in Rust due
98.
Show HN: fcp – A significantly faster alternative to cp(1), written in Rust(github.com)
88 points by Svetlitski 5y ago|86 comments
99.
I Tried to Get My Name Off People-Search Sites. It Was Nearly Impossible(consumerreports.org)
2 points by Svetlitski 6y ago|1 comments
100.
Sympy – A Python library for symbolic mathematics(docs.sympy.org)
3 points by Svetlitski 6y ago|0 comments
101.
by Svetlitski 6y ago
At risk of sounding curmudgeonly, I can't help but feel like `git maintenance` is a bit of unneeded feature creep. Does it sound useful? Sure. But should it part of git itself, when its functionality could be easily achieved instead by
102.
Operation Nifty Package(en.wikipedia.org)
1 points by Svetlitski 6y ago|0 comments
103.
Stackoverflow: Introducing the Outdated Answers Project(meta.stackoverflow.com)
3 points by Svetlitski 6y ago|0 comments
104.
mdn.org(mdn.org)
2 points by Svetlitski 6y ago|0 comments
105.
by Svetlitski 6y ago
Searching for "pink" results in a muddy brown: https://alexbeals.com/projects/colorize/search.php?q=pink
106.
by Svetlitski 6y ago
Once LLVM fixes some bugs with `noalias`, at which point Rust will begin using it again in more circumstances [1], I'd expect to see Rust get even faster in these benchmarks, given that the Rust compiler knows much more about which p
107.
You Fix It (2018)(w0rp.com)
2 points by Svetlitski 6y ago|0 comments
108.
by Svetlitski 6y ago
Sounds interesting in theory, but the results are somewhat bizarre. For example, their published list of the top 200 "most critical" open-source C projects includes Urbit and Stellar, and includes micropython but does not includ
109.
by Svetlitski 6y ago
I can't seem to find mention of the clock frequency of the chip anywhere . Am I missing something or is Apple withholding this information for the time being?
110.
by Svetlitski 6y ago
Considering how long this outage has been going on, I'm very interested in reading the post-mortem on this.
111.
POSIX hcreate(linux.die.net)
1 points by Svetlitski 6y ago|0 comments
112.
Show HN: Merge – combine multiple processes in one terminal window(github.com)
7 points by Svetlitski 7y ago|2 comments
113.
Docker Uses 3+ GB of RAM with No Running Containers(github.com)
1 points by Svetlitski 8y ago|0 comments