Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve copy on homepage, consider removing "fuck" #14

Closed
felixge opened this issue Apr 17, 2013 · 5 comments
Closed

Improve copy on homepage, consider removing "fuck" #14

felixge opened this issue Apr 17, 2013 · 5 comments
Labels

Comments

@felixge
Copy link
Contributor

felixge commented Apr 17, 2013

see https://news.ycombinator.com/item?id=5563569

@tim-kos
Copy link
Member

tim-kos commented Apr 17, 2013

Like I said from the start - it's inappropriate, and not necessary. There are other words that get the message across the same way (or better) without potentially offending people. I think we should also consider replacing "hard" with "difficult".

Some ideas:
darn difficult, damn difficult, ultra difficult, freaking difficult, horribly difficult, terribly difficult, more difficult than necessary, insanely difficult

My personal favorite: insanely difficult

@felixge
Copy link
Contributor Author

felixge commented Apr 17, 2013

Sending a rocket into space is insanely difficult, let's not be too ridiculous : )

@tim-kos
Copy link
Member

tim-kos commented Apr 17, 2013

Well if you look at it from that point, then it's not fucking hard either. ; ) But I see your point.

"really difficult" then

@hintjens
Copy link

You can understate it. Your target audience don't need to be sold on the problem, which is well known, only your solution to it. Just describe it as "hard, complex, and costly", and set your mission to make it "easy, simple, and cheap". Then explain how you intend to make it easy (stacks you can plug in), simple (your expertise) and cheap (open source and open standards).

Point out that this is the first attempt to build an open standard in this area. You may want to explain how to contribute to the standard since it's unclear (do you accept pull requests, or comments? Is there one editor? Who gets to decides what is the standard? How does someone make a fork of it? Etc.)

@felixge
Copy link
Contributor Author

felixge commented Apr 17, 2013

@hintjens thank you so much for the feedback! The commit above is hopefully a good stop-gap improvement. But I want to incorporate more of your advise so I created #16 for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants