You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
-
67Despite the abrasive tone, I'm having a hard time disagreeing with the reasoning. It very much does not feel like the community is being listened to, in any sense.fbueckert– fbueckert2018-08-13 21:11:32 +00:00Commented Aug 13, 2018 at 21:11
-
1"Folks, we don't have yet a mechanism for custom arrows. So be prepared for some regression." If they had said that, people would be asking "why not" and saying "SO developers are stupid for not implementing it". Nothing would change.Nicol Bolas– Nicol Bolas2018-08-14 17:55:22 +00:00Commented Aug 14, 2018 at 17:55
-
11@NicolBolas No, they would not. Regressions are a part of a programmer's life. Any programmer who thinks that causing a regression makes someone stupid has never actually worked on a big project. But simply saying "we're removing this, deal with it"? That's just in poor taste.forest distrusts StackExchange– forest distrusts StackExchange2018-08-19 09:50:32 +00:00Commented Aug 19, 2018 at 9:50
-
6@forest: "Regressions are a part of a programmer's life." 1: Not every SE user is a programmer. 2: Not every SE user is a professional programmer. 3: Even among those who are, there would still be many who say that they should.Nicol Bolas– Nicol Bolas2018-08-19 13:28:04 +00:00Commented Aug 19, 2018 at 13:28
-
1@NicolBolas That's true. I was talking more about SO users, not SE users in general. My point is that the overlap between those who have enough understanding to judge a regression and those who believe regressions imply stupidity is effectively zero.forest distrusts StackExchange– forest distrusts StackExchange2018-08-29 01:12:52 +00:00Commented Aug 29, 2018 at 1:12
Add a comment
|
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. stack-overflow), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you