Top all-time · #7960
Ed's Home Page
Personal blog · epage.github.io/blogprogramming
Ed's Home Page is a personal blog at epage.github.io about programming. Since 2019, 10 different Hacker News readers have linked it 26 times, most often “Improving Learnability of Rust”. It is still writing: the last post was on 2026-08-05, and you can follow it by feed.
Most-linked posts?
- Improving Learnability of Rust3 people · 5 mentions · first linked 2021-09-16
- A Vision for Cargo3 people · 3 mentions · first linked 2026-08-05
- Iterating on Testing in Rust2 people · 2 mentions · first linked 2023-06-10
- Minor Semver Issue2 people · 2 mentions · first linked 2022-02-05
What Hacker News says?
> The one goal of the port we did not succeed in was removing CMake. > That’s because, while cargo is great at building things, it is very simplistic at installing them. Cargo wants everything in a few neat binaries, and that isn’t our use case. Fish has about 1200 .fish scripts (961 completions, 217 associated functions), as well as about 130 pages of documentation (as html and man pages), and the web-config tool a…
Comment linking /blog/2023/08/are-we-gui-build-yet/
on “Fish 4.0: The Fish of Theseus”Submitted Clap 3.0, a Rust CLI argument parser as a story · 38 points
HN discussionI think a low effort, high value step in the usability direction of a REPL is cargo-script I've written some on it [0] and there was a recent reddit thread discussing it [1] [0] https://epage.github.io/blog/2021/09/learning-rust/ [1] https://www.reddit.com/r/rust/comments/rddokp/media_most_up_...
Comment linking /blog/2021/09/learning-rust/
on “Tokio Console”Submitted Iterating on Testing in Rust as a story · 21 points
HN discussionFor me, its the explicitness in Python that is killer. I can see a name and match that to an import and match that to a package. Grabbing a function pointer works exactly as I would expect. Stealing from Krister Stendahl's laws for religious discourse, Ruby's composable iteration is one area I have holy envy, particularly after I got used to it in Rust. I've used Python's generators many times just to have to switch…
Comment linking /blog/2021/07/pushgen-experiment/
on “Ruby vs. Python comes down to the for loop”Submitted Minor Semver Issue as a story · 17 points
HN discussionThis reminds me of some the trade-offs I've looked at with monorepos: https://epage.github.io/dev/monorepos/
Comment linking /dev/monorepos/
on “Monorepo is great if you're really good”Submitted TOML v0.9 as a story · 3 points
HN discussionAs a prolific PR author, I've found how I communicate has a major factor on how well and quickly people respond to PRs. I've recorded my lessons at https://epage.github.io/dev/pr-style/ .
Comment linking /dev/pr-style/
on “If you are asking for human attention, demonstrate human effort”Submitted Anstream: Simplifying Terminal Styling as a story · 2 points
HN discussionExcited to see more stuff in this space. I've previously done some investigation into the various options [0] Questions: - Why have your own pre-conditions rather than relying on Github's built-in conditions and Status? Ideas - Autosquash fixup commits. I like to have multi-commit PRs that get merged into main. I'd like to leave my fixup commits up to make it easier for reviewers to see fixes and then have the tool…
Comment linking /dev/submit-queue/
on “Launch HN: MergeQueue (YC S21) – Automate rebasing and merging for your codebase”Submitted Improving Learnability of Rust as a story · 2 points
HN discussionWhile tools like Github check for patch conflicts, they don't check for semantic conflicts (e.g. one PR adds a new use of a function another PR removes). This is where merge queues come into play which have a variety of names (merge queue, submit queue, merge train, etc) I have a write up on merge queues [0] that goes into other benefits (e.g. speeding up PR builds), design considerations and their trade offs, and a…
Comment linking /dev/submit-queue/
on “Ask HN: How are pull requests integrated in a repo with high commit frequency?”Submitted A Vision for Cargo as a story · 1 points
HN discussionBefore CI became prevalent, I was against checked-in code generation and it took me a while to unprogram that bias and re-evaluate. Its been a big help in keeping runtimes fast with a python program at a previous job and at keeping build-times fast in an open source project of mine [0] I wish there was a simple way in Rust to make proc macros optionally generate code that gets checked in, allowing for most of the ma…
Comment linking /blog/2019/10/speeding-up-rust-builds-code-gen-edition/
on “Self Modifying Code as an alternative to macros”Submitted A Vision for Cargo as a story · 1 points
HN discussion> A) is easy to write one off scripts that do a job fast, with minimal thinking and effort. I am thinking of Python and Ruby. For me I can write code with high velocity in these languages. Once I wrap up some other projects, I plan to explore this space a little bit within Rust. imo the biggest bang for the buck is just having good `#!` support. Probably mid-year I expect to have a Pre-RFC up for single-file cargo p…
Comment linking /blog/2021/09/learning-rust/
on “Rust went from side project to world’s fastest growing language”Submitted A Vision for Cargo as a story · 1 points
HN discussionFor now, it looks like they are using Gitlab's model where they are speculatively executing items in the merge queue which will push up against max concurrent runner counts (cloud) and run up bills (self-hosted). I hope they add bors-like batching soon. Unfortunately, I don't see anything in the docs allowing you to detect a merge-queue run compared to a regular run. If they are treated as master pushes, then that h…
Comment linking /dev/submit-queue/
on “Pull Request Merge Queue Limited Beta”Submitted Guideline: Rust Style as a story · 1 points
HN discussionSubmitted Winnow 0.5: The Fastest Rust Parser-Combinator Library? as a story · 1 points
HN discussionSubmitted Iterating on Testing in Rust as a story · 1 points
HN discussionSubmitted Clap 4.0, a Rust CLI argument parser as a story · 1 points
HN discussionSubmitted Minor Semver Issue as a story · 1 points
HN discussionSubmitted Learnability of Rust as a story · 1 points
HN discussionSubmitted Learnability of Rust as a story · 1 points
HN discussion
