3 ms·
I don't think I followed any of these for my side project (www.diff.so) because, well, it's a side project! It's a prototype, something I did for fun. This is a
by jkaptur 11y ago
I don't think I followed any of these for my side project (www.diff.so) because, well, it's a side project! It's a prototype, something I did for fun. This is a great list of things to do before I expect someone to use it seriously, not a pre-launch checklist.
To go a bit off-topic, I actually tried to follow the "don't use color alone to provide information" for the static diff on diff.so/about, but I couldn't find a way to get ChromeVox to read text on one side of the diff any differently than text on the other. I'd be really interested in any advice on that - it seems like some screenreader users could use something a little more user-friendly than emacs.
- userium 11y ago"It's a prototype, something I did for fun." The goal of your side project makes a difference I suppose. People build side projects, either as creative hobbies, or some in the hopes of turning them into startups. Nice site btw.! :)
- cableshaft 11y agoOh wow, your site is exactly what I needed. I've got diff programs, but they focus more on differences over a full line, instead of word by word. But I write stories and have a bunch of ooooold versions that I always wanted to compare on a word by word basis, and your website should save me some significant time comparing those.
- jkaptur 11y agoOh cool! I'm glad to hear it. Let me know if there's any way I can make it better for you (although, like I said, it's a thing on the side).