Live data from Hacker News

Viewing profile — chipx86

chipx86

HN member
Joined
Tue, Mar 12, 2013, 7:52 PM UTC
HN karma
586
Public activity
106 items

About chipx86

Long-time open source and web developer.

I co-created one of the very first code review products, Review Board (https://www.reviewboard.org), and later founded Beanbag (https://www.beanbaginc.com) to manage its development and offer support.

Also, former VMware Workstation/Server/WSX for Linux developer.

You can find me at:

Blog: https://chipx86.blog E-mail: christian@beanbaginc.com. BlueSky: https://bsky.app/profile/chipx86.com Twitter/X: https://x.com/chipx86 Mastodon: https://mastodon.online/@chipx86 LinkedIn: https://www.linkedin.com/in/chipx86/ GitHub: https://github.com/chipx86/

[ my public key: https://keybase.io/chipx86; my proof: https://keybase.io/chipx86/sigs/szviTLtZdOXzRQOtNQgCiiz1tOlrAiTA-y6Hj9KiTvw ]

Recent public activity

  1. comment
    Comment #48538562

    About a year ago, I started working on disassembling the NES game Faxanadu. The goal was to fully understand and document the game, and to produce the most thorough understanding o…

  2. comment
    Comment #48495623

    The author has a number of repositories going back 3 years that seem purely experimental and, to me at least, really fun to look through. https://github.com/icitry?tab=repositories…

  3. comment
    Comment #48276976

    We're still using it for our stuff (via our @beanbag/spina TypeScript wrapper for Backbone that has a few additional niceties), and I feel the same way. We can be as close to the D…

  4. story
  5. comment
    Comment #46158936

    I'm pretty happy to see this, as conditionals can really help keep code manageable when trying to define CSS variables or other properties based on combinations of light mode, dark…

  6. comment
    Comment #45555850

    Love seeing this one. My uncle was co-founder of Quarterdeck, and I grew up in a world of DESQview and QEMM. It was a big influence on me as a child. Got a good family story about …

  7. comment
    Comment #44427047

    This is a great feature for those who want a mix of positional and keyword-only arguments. I should have mentioned originally (and I've since updated my post) that this and the kw_…

  8. comment
    Comment #44420497

    That's annoying for sure. Though a different problem. All the kw_only=True argument for dataclasses does is require that you pass any fields you want to provide as keyword argument…

  9. comment
    Comment #44420434

    Yeah, that's the approach we'll be taking in housekeeping. I didn't want to complicate the example any more than I already did :)

  10. comment
    Comment #44420062

    That's always the challenge when iterating on interfaces that other people depend on. What we do is go through a deprecation phase. Our process is: * We provide compatibility with …

  11. comment
    Comment #44178538

    I'm really glad it was useful for you and your teams! :) Hearing that kind of thing always brightens my day. I've felt very lucky getting to work on this as my job all these years.…

  12. comment
    Comment #44178436

    Yep! We spent 20 years dealing with these problems and in those 20 years nobody really solved these pain points. So we talked to some SCM vendors, bounced ideas around, built a spe…

  13. comment
    Comment #44178347

    Generally-speaking, you probably shouldn't have to deal with these problems unless you're writing a tool that has to interface with certain SCMs or SCMs used in certain environment…

  14. comment
    Comment #44178146

    If wishing made it so... I have so many stories I could tell at this point.

  15. comment
    Comment #44178090

    Yeah the nomenclature sucks. When talking about the file, the two terms are often used interchangeably (and are usually a .diff or a .patch extension). For fun, the GNU Patch manpa…

  16. comment
    Comment #44178046

    We build a code review product that interfaces with over a dozen SCMs. In about 20 years of writing diff parsers, we've encountered all kinds of problems and limitations in SCM-gen…

  17. comment
    Comment #44178013

    difftastic is great! This isn't a tool for viewing changes to files or to ASTs. This is a way of being able to generate a single diff file for processing or patching that addresses…

  18. comment
    Comment #44177948

    Created by the Git team for Git's purposes, rather than something documented or proposed for wider adoption. Other SCMs can and do use a Git-style diff format, but as there's no de…

  19. comment
    Comment #44177911

    In the early drafts, we played with a number of approaches for the structure. Things like "commit-meta", etc. In the end, we broke it down into `# `, just to simplify the parsing r…

  20. comment
    Comment #44177846

    Git is using a proprietary variant on top of Unified Diffs. Unified Diffs themselves convey very little information about the file being modified, focusing solely on the line-based…

  21. comment
    Comment #44177803

    Absolutely agree. I think there's a lot of avenues to explore for better diff representations for structured data (which would also be great for ASTs, something we've been thinking…

  22. comment
    Comment #44177770

    I have a much-too-long-for-one-comment write-up about this, but it's basically for those who build SCMs or tools that need to work with SCMs. End users shouldn't have to care about…

  23. comment
    Comment #44177758

    The repository metadata absolutely should own the commit information. Diff files are there to represent a delta state of the repository, a difference between a range of changes. Th…

  24. comment
    Comment #44177730

    `git format-patch` and `git am` are great! Not all SCMs have something like that (many don't even have a diff format with enough information to reliably look up a file or apply all…

  25. comment
    Comment #44177711

    It is. However, first the tools need to be able to grab the necessary information from the diff to, say, locate that file or its metadata in a repository. Git's diff format contain…