Fossil SCM
Clarified a few points in the javascript.md doc
Commit
7b51e27f434dfeae4e295a48490ac8ad768ac8aeb0aca4f62c91e862259edf64
Parent
c31d5ba4b9d06f7…
1 file changed
+6
-4
+6
-4
| --- www/javascript.md | ||
| +++ www/javascript.md | ||
| @@ -9,20 +9,22 @@ | ||
| 9 | 9 | it is an enhancement to provided functionality, and there is always |
| 10 | 10 | another way to accomplish a given end without using JavaScript. |
| 11 | 11 | |
| 12 | 12 | This is not to say that Fossil’s fall-backs for such cases are always as |
| 13 | 13 | elegant and functional as a no-JS purist might wish. That is simply |
| 14 | -because [the vast majority of web users run with JavaScript enabled](#stats), | |
| 15 | -and a minority of those run with some kind of [conditional JavaScript | |
| 16 | -blocking](#block) in place. Fossil’s active developers do not deviate from that | |
| 14 | +because [the vast majority of web users leave JavaScript unconditionally | |
| 15 | +enabled](#stats), and of the small minority of those that do not, a | |
| 16 | +large chunk use some kind of [conditional blocking](#block) instead, | |
| 17 | +rather than disable JavaScript entirely. | |
| 18 | +Fossil’s active developers do not deviate from that | |
| 17 | 19 | norm enough that we have many no-JS purists among us, so the no-JS case |
| 18 | 20 | doesn’t get as much attention as some might want. We do [accept code |
| 19 | 21 | contributions][cg], and we are philosophically in favor of graceful |
| 20 | 22 | fall-backs, so you are welcome to appoint yourself the position of no-JS |
| 21 | 23 | czar for the Fossil project! |
| 22 | 24 | |
| 23 | -Evil is in actions, not in nouns: we do not believe JavaScript *can* | |
| 25 | +Evil is in actions, not in objects: we do not believe JavaScript *can* | |
| 24 | 26 | be evil. It is an active technology, but the actions that matter here |
| 25 | 27 | are those of writing the code and checking it into the Fossil project |
| 26 | 28 | repository. None of the JavaScript code in Fossil is evil, a fact we |
| 27 | 29 | enforce by being careful about who we give check-in rights on the |
| 28 | 30 | repository to and by policing what code does get contributed. The Fossil |
| 29 | 31 |
| --- www/javascript.md | |
| +++ www/javascript.md | |
| @@ -9,20 +9,22 @@ | |
| 9 | it is an enhancement to provided functionality, and there is always |
| 10 | another way to accomplish a given end without using JavaScript. |
| 11 | |
| 12 | This is not to say that Fossil’s fall-backs for such cases are always as |
| 13 | elegant and functional as a no-JS purist might wish. That is simply |
| 14 | because [the vast majority of web users run with JavaScript enabled](#stats), |
| 15 | and a minority of those run with some kind of [conditional JavaScript |
| 16 | blocking](#block) in place. Fossil’s active developers do not deviate from that |
| 17 | norm enough that we have many no-JS purists among us, so the no-JS case |
| 18 | doesn’t get as much attention as some might want. We do [accept code |
| 19 | contributions][cg], and we are philosophically in favor of graceful |
| 20 | fall-backs, so you are welcome to appoint yourself the position of no-JS |
| 21 | czar for the Fossil project! |
| 22 | |
| 23 | Evil is in actions, not in nouns: we do not believe JavaScript *can* |
| 24 | be evil. It is an active technology, but the actions that matter here |
| 25 | are those of writing the code and checking it into the Fossil project |
| 26 | repository. None of the JavaScript code in Fossil is evil, a fact we |
| 27 | enforce by being careful about who we give check-in rights on the |
| 28 | repository to and by policing what code does get contributed. The Fossil |
| 29 |
| --- www/javascript.md | |
| +++ www/javascript.md | |
| @@ -9,20 +9,22 @@ | |
| 9 | it is an enhancement to provided functionality, and there is always |
| 10 | another way to accomplish a given end without using JavaScript. |
| 11 | |
| 12 | This is not to say that Fossil’s fall-backs for such cases are always as |
| 13 | elegant and functional as a no-JS purist might wish. That is simply |
| 14 | because [the vast majority of web users leave JavaScript unconditionally |
| 15 | enabled](#stats), and of the small minority of those that do not, a |
| 16 | large chunk use some kind of [conditional blocking](#block) instead, |
| 17 | rather than disable JavaScript entirely. |
| 18 | Fossil’s active developers do not deviate from that |
| 19 | norm enough that we have many no-JS purists among us, so the no-JS case |
| 20 | doesn’t get as much attention as some might want. We do [accept code |
| 21 | contributions][cg], and we are philosophically in favor of graceful |
| 22 | fall-backs, so you are welcome to appoint yourself the position of no-JS |
| 23 | czar for the Fossil project! |
| 24 | |
| 25 | Evil is in actions, not in objects: we do not believe JavaScript *can* |
| 26 | be evil. It is an active technology, but the actions that matter here |
| 27 | are those of writing the code and checking it into the Fossil project |
| 28 | repository. None of the JavaScript code in Fossil is evil, a fact we |
| 29 | enforce by being careful about who we give check-in rights on the |
| 30 | repository to and by policing what code does get contributed. The Fossil |
| 31 |