WillAbides
Joined 11 years ago
Karma
1,012
Submissions
77
Member since
Oct 8
Recent submissions
Comment · 3 years ago
I also blogged about my motivations for writing Release Train here: https://willabides.com/posts/release-train-continuous-releas...
Comment · 3 years ago
Release Train will automatically create a new GitHub release every time you merge a
pull request into main or whatever release branches you set up. It's inspired by
semantic-release[1] but takes a different approach. Instead of using commit messages
it uses PR labels to determine the type of release. This makes it easier to use.
It's also a single binary so it doesn't require npm or any other package manager.
It comes in the forms of both cli and GitHub Action.
The downside of this approach is that it ties you to GitHub. It could be extended or forked to support any platform that has something like a pull request with labels. I'm comfortable adding that to the technical debt I will incur migrating away from GitHub.
I would love to get notes from the hn community on this.
Comment · 3 years ago
You’ve got me beat. https://willabides.com. I haven’t posted anything yet.
Comment · 5 years ago
related blog post: https://github.blog/2021-06-23-introducing-new-github-issues...
Comment · 5 years ago
For anybody who stumbles across this and is interested, this conversation is continued on reddit.
https://old.reddit.com/r/golang/comments/mlhvx0/i_wrote_yet_...
Comment · 5 years ago
I apparently had a fundamental misunderstanding of the meaning of branchless. That's embarrassing.
As for simdjson-go, I did benchmark it. rjson outperformed simdjson-go in most benchmarks, but simdjson-go was about 3% faster reading citm_catalog.json.
https://github.com/WillAbides/rjson#simdjson
Edit:
I see on your bio that you are one of the simdjson authors. I hope you will indulge a question about it. I am generally more interested parsing a large volume of json documents efficiently than I am in doing it quickly. Since simdjson uses parallel instructions, would that mean that the speedup comes at the expense of being able to process more documents in parallel on the same hardware?
Comment · 5 years ago
I wrote a mostly branchless json parser in go using ragel to generate most of the code.
https://github.com/WillAbides/rjson
The generated code isn't much to look at, but it is certainly fast.
https://github.com/WillAbides/rjson/blob/main/object_handler...
Comment · 8 years ago
I’m not involved in this project, but I would guess that it’s because it validates both issues and PRs, but only PRs have statuses on GitHub, More precisely, only commits have statuses, and issues aren’t associated with commits.
Comment · 8 years ago
“avatar_url” is the only part of that endpoint in preview, so that warning only applies to that field. I can see how the notification isn’t clear on that point, and I will bring that up.
Comment · 8 years ago
I don't think they store all their data on twitter. If they did, they probably wouldn't have this file in their repo: https://github.com/edent/openbenches/blob/master/database/da...
Comment · 8 years ago
I didn’t spend hundreds of dollars on a mechanical keyboard with custom caps and switches to “click”.
hnchat:eWY4KMH4MUJK6UDQDnq7