chipx86

7 ms·

1.
by chipx86 8d ago
No single root cause, but I'd say a combination of rapid growth, a changing market with no obvious (at-the-time) answers, some resource issues, and some missteps by some people. The company began to grow fast in the years after I joine
2.
by chipx86 9d ago
Another ex-VMware here (9 years on the Workstation team). It's so very sad to see... I grew up there from a career standpoint and I was proud to be there, loved being there, and I just don't recognize it anymore. I agree with yo
3.
by chipx86 3mo ago
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 of the game yet. It's been fascinating. The game has a t
4.
by chipx86 3mo ago
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 And he has a YouTube channel linked to his
5.
by chipx86 4mo ago
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 DOM as we need (or let something manage it for our
6.
Modernize Your Punch Card Review with Review Board(reviewboard.org)
5 points by chipx86 6mo ago|1 comments
7.
by chipx86 10mo ago
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 mode, high-contrast, contextual state in a document or
8.
by chipx86 11mo ago
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 that whole acquisition attempt, but I don't want to spe
9.
by chipx86 1y ago
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_only= flag both require Python 3.10 and higher, so code
10.
by chipx86 1y ago
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 arguments instead of positional arguments when instantiating a
11.
by chipx86 1y ago
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 :)
12.
by chipx86 1y ago
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 the old signature for 2 major releases. * We document t
13.
by chipx86 1y ago
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. It'd have been amazing having something like
14.
by chipx86 1y ago
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 spec, got feedback from them, repeated off-and-on for a couple
15.
by chipx86 1y ago
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 environments. I'll give you some examples for each of th
16.
by chipx86 1y ago
If wishing made it so... I have so many stories I could tell at this point.
17.
by chipx86 1y ago
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 manpage says: "NAME: patch - apply a diff file to an origina
18.
by chipx86 1y ago
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-generated diff files (which we have to process) that we wo
19.
by chipx86 1y ago
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 the kinds of problems we've encountered in over 2
20.
by chipx86 1y ago
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 defined grammar, there are sometimes important diffe
21.
by chipx86 1y ago
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 `#<section_level><section_type>`, just to simplify the parsing requirement
22.
by chipx86 1y ago
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 contents of text files and allowing vendors to provide thei
23.
by chipx86 1y ago
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 about). This format is meant to be an extension o
24.
by chipx86 1y ago
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 this. There's not one patch/diff format
25.
by chipx86 1y ago
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. Those may be one or more commits, or one more changes across i
26.
by chipx86 1y ago
`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 of its changes). Having the whole state of a series of
27.
by chipx86 1y ago
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 contains enough information to do this, but many don't. W
28.
by chipx86 1y ago
Exactly that. They all do things so differently that you end up creating and maintaining a separate parser for every SCM's diff format, and sometimes doing a lot of normalization of content or modification to include information the fo
29.
by chipx86 1y ago
I should also mention, we didn't want to invent a brand-new diff format that required all-new tooling (a replacement for GNU patch, for instance). We want this to be able to work with existing tools that understand Unified Diffs and re
30.
by chipx86 1y ago
Sorry for the absolute wall of text (I tried nesting things under bullet points but that didn't work out well). Hopefully some of that is useful. Key point: Much of this is about solving issues with tools that work with the varying fil

More ›