Skip to content

Commit

Permalink
docs: Add a Testmonials page.
Browse files Browse the repository at this point in the history
Show our positive reviews to the world. It's also not completly serious, in a similar fashion to
Phabricator.
  • Loading branch information
PhilipMetzger authored and thoughtpolice committed Feb 9, 2024
1 parent 6c1aeff commit f151d2a
Show file tree
Hide file tree
Showing 2 changed files with 120 additions and 0 deletions.
118 changes: 118 additions & 0 deletions docs/testimonials.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,118 @@
# Testimonials

You might not be ready to make the jump to Jujutsu yet. It's understandable; new
tools come with new lessons, failures, and ideas to absorb. They require
practice. In order to provide some motivation, we've collected a number of real,
100% authentic testimonials — from our loving users, our silly developers
— all to tip the scales and get you on our side!

## What the users have to say

> I've spent many years of my career working on version control. What I like
> most about Jujutsu is how it has non-obvious solutions to UX problems that
> we've run into in the past. What most people may not realize is that there are
> many novel features which all interlock to make it easy to use.
>
> For example, consider Jujutsu's support for automatically rebasing descendants
> of amended revisions. When we implemented that in Mercurial, we ran into an
> issue: what if there's a merge conflict? Our solution was to warn users and
> just not perform the auto-rebase. Now, suddenly, users have to understand that
> there can be old versions of the same revision visible in their log, and learn
> how to fix this state.
>
> In contrast, Jujutsu's solution is to simply make merge conflicts first-class.
> This is not just an improvement in general, it is also specifically an
> improvement for auto-rebase — users no longer have to learn about old
> versions of a revision unless they want to look at the obslog.
>
> Over and over, I'm struck by how well Jujutsu demonstrates this kind of
> evolved thinking, which as an experienced version control developer I deeply
> appreciate.
— Rain, engineer at Oxide Computer Company, former VCS developer

> Jujutsu is amazing... I couldn't have come up with anything remotely as
> elegant.
>
> It's so rare that a solution attacks the innermost core of a problem so
> thoroughly, I genuinely feel blessed to be in its presence. And also a bit
> vindicated in not even trying to learn to use any of the tools that felt like
> more crutches stacked upon a sand castle
— Anonymous user, speaking from the shadows

> It's the easiest time I've ever had learning a tool this deeply this quickly,
> because of the ability to experiment and undo, instead of triple-checking
> before trying a new scary command.
— Scott Olson, advanced Git user and now a Jujutsu user

> I've started using jj for personal repos and it has quickly gone from "neat,
> let's try this more" to "very neat, added to my permanent config and
> automatically installed for new machines".
— Poliorcetics, on GitHub

> when I worked on the rust compiler, my job was to chain together a bunch of
> strange and cursed tools that broke often. jujutsu breaks about half as
> much, so that's pretty good i guess
— jyn514, Rust contributor

> Jujutsu is pretty cool, you can even keep most of your existing workflows
— Ben, who doesn't want you keeping your existing workflow

> Wait, it's not called Jujitsu?
— Phil, Mercurial contributor (who doesn't have to learn Git, now that
Jujutsu exists)

## What the developers have to say

> I've been a FOSS contributor using Git for over 16 years, and Jujutsu
> continues to amaze me every day. It has that sweet simplicity I was fond of in
> Darcs, but it boils down all my most core and fundamental workflows —
> developed over years of experience — into a simple set of primitives.
> The internal design is simple and beautiful; it looks like a database, making
> the implementation elegant, safe, and extensible. All this, using the same Git
> repositories my coworkers use.
>
> It's like if you found out one day that you built your entire home on a vein
> of rich gold. Every day I seem to find new and beautiful emergent behaviors,
> all adding up to a tool that is greater than the sum of its parts.
— Austin Seipp, "No 1. Jujutsu Fan"

> Honestly, I implemented signing support mostly for that sweet dopamine hit
> that you get from the green checkmark on GitHub. Yeah.
— Anton Bulakh, contributor and dopamine enthusiast

> I'm sometimes still surprised that navigating with `next` and `prev` works.
— Philip Metzger, author of `jj next` and `jj prev`

> I'm completely unbiased, but I think it's pretty cool.
— Martin von Zweigbergk, project creator and leader

## Spread the word yourself

Are you satisfied with Jujutsu? Ready to recommend it to a Jujillion of your
friends and coworkers? Great! The easiest way to help the project grow is word
of mouth. So make sure to talk to them about it and show off your hip new tool.
Maybe post a link to it on your other favorite tool that you love using, Slack?

If you're not sure what to say, we hired the cheapest marketing team we could
find to design a list of Pre-Approved Endorsements in their laboratory. Just
copy and paste these right into a text box! Shilling for an open source project
has never been easier than this.

> Jujutsu is an alright tool. I guess.
> Jujutsu is my favorite software tool of all time. I am saying this for no
> particular reason, definitely not because I was paid to.
> I love Jujutsu. I love Jujutsu. I love Jujutsu. I love Jujutsu. I love
> Jujutsu. I love Jujutsu. I love Jujutsu. I love Jujutsu.
2 changes: 2 additions & 0 deletions mkdocs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -84,6 +84,8 @@ nav:

- "CLI Reference": 'cli-reference.md'

- Testimonials: 'testimonials.md'

- Concepts:
- 'Working Copy': 'working-copy.md'
- 'Branches': 'branches.md'
Expand Down

0 comments on commit f151d2a

Please sign in to comment.