5 ms·
I won't win this argument (and I won't try), but, I appreciate the time you took to write me a response! 1. I'm working on this and the feature was an attempt
by saddington 12y ago
I won't win this argument (and I won't try), but, I appreciate the time you took to write me a response!
1. I'm working on this and the feature was an attempt to combine both WYSIWYG and Markdown into one formatting experience. This ended up being a gamble and one that I lost and the newest updates will address this. It sucks, i failed, i got it wrong.
2. A lot? sure. i guess. there are tons of great alternatives, for sure!
"More coding"...? #facepalm ...
really?
- je42 12y agoRe.: 2. Don't worry about the price point atm. He might be right that it is not worth currently for him, but it looks like that a lot of other people value it. If you continue adding features and continue making the product as a whole better and more valuable for a larger and larger audience. So eventually he should be happy as well. That requires obviously, that you mostly add features. i.e. you don't re-invent features or redesign features without adding value (just to make prettier), I have seen a lot of teams/people doing that kind of mistake.
- saddington 12y agoa great reminder. i'm keen on keeping it simple... and focused. i don't need to be the next microsoft word... i'd rather not actually. i think one of the most important things any developer or business does is decide who their customer is... and who their customer isn't.