Fossil SCM
Spelling and grammar fixes to javascript.md.
Commit
209f73cbc251f0d25e98b98c5e6934a3990b2dcd78594611b606123701850990
Parent
977ba78fdd2901e…
1 file changed
+3
-4
+3
-4
| --- www/javascript.md | ||
| +++ www/javascript.md | ||
| @@ -46,20 +46,20 @@ | ||
| 46 | 46 | [cg]: ./contribute.wiki |
| 47 | 47 | |
| 48 | 48 | |
| 49 | 49 | ## <a id="debate"></a>Arguments Against JavaScript & Our Rebuttals |
| 50 | 50 | |
| 51 | -There many common arguments against the use of JavaScript. Rather than | |
| 51 | +There are many common arguments against the use of JavaScript. Rather than | |
| 52 | 52 | rehash these same arguments on the [forum][ffor], we distill the common |
| 53 | 53 | ones we’ve heard before and give our stock answers to them here: |
| 54 | 54 | |
| 55 | 55 | 1. “**It increases the size of the page download.**” |
| 56 | 56 | |
| 57 | 57 | The heaviest such pages served by Fossil only have about 8 kB of |
| 58 | 58 | compressed JavaScript. (You have to go out of your way to get Fossil |
| 59 | 59 | to serve uncompressed pages.) This is negligible, even over very |
| 60 | - slow data connnections. If you are still somehow on a 56 kbit/sec | |
| 60 | + slow data connections. If you are still somehow on a 56 kbit/sec | |
| 61 | 61 | analog telephone modem, this extra script code would download in |
| 62 | 62 | about a second. |
| 63 | 63 | |
| 64 | 64 | Most JavaScript-based Fossil pages use less code than that. |
| 65 | 65 | |
| @@ -223,11 +223,10 @@ | ||
| 223 | 223 | The primary difference between these two for our purposes is that |
| 224 | 224 | NoScript lets you select scripts to run on a page on a case-by-case |
| 225 | 225 | basis, whereas uBlock Origin delegates those choices to a group of |
| 226 | 226 | motivated volunteers who maintain allow/block lists to control all |
| 227 | 227 | of this; you can then override UBO’s stock rules as needed. |
| 228 | - | |
| 229 | 228 | |
| 230 | 229 | 10. “**My browser doesn’t even *have* a JavaScript interpreter.**” |
| 231 | 230 | |
| 232 | 231 | The Fossil open source project has no full-time developers, and only |
| 233 | 232 | a few of these part-timers are responsible for the bulk of the code |
| @@ -555,11 +554,11 @@ | ||
| 555 | 554 | |
| 556 | 555 | As of mid-2020, the informal provisional plan is to increase Fossil |
| 557 | 556 | UI's use of JavaScript considerably compared to its historically minimal |
| 558 | 557 | uses. To that end, a framework of Fossil-centric APIs is being developed |
| 559 | 558 | in conjunction with new features to consolidate Fossil's historical |
| 560 | -hodge-podge of JavaScript snippets into a coherent code base. | |
| 559 | +hodgepodge of JavaScript snippets into a coherent code base. | |
| 561 | 560 | |
| 562 | 561 | When deciding which features to port to JavaScript, the rules of thumb |
| 563 | 562 | for this ongoing effort are: |
| 564 | 563 | |
| 565 | 564 | - Pages which primarily display data (e.g. the timeline) will remain |
| 566 | 565 |
| --- www/javascript.md | |
| +++ www/javascript.md | |
| @@ -46,20 +46,20 @@ | |
| 46 | [cg]: ./contribute.wiki |
| 47 | |
| 48 | |
| 49 | ## <a id="debate"></a>Arguments Against JavaScript & Our Rebuttals |
| 50 | |
| 51 | There many common arguments against the use of JavaScript. Rather than |
| 52 | rehash these same arguments on the [forum][ffor], we distill the common |
| 53 | ones we’ve heard before and give our stock answers to them here: |
| 54 | |
| 55 | 1. “**It increases the size of the page download.**” |
| 56 | |
| 57 | The heaviest such pages served by Fossil only have about 8 kB of |
| 58 | compressed JavaScript. (You have to go out of your way to get Fossil |
| 59 | to serve uncompressed pages.) This is negligible, even over very |
| 60 | slow data connnections. If you are still somehow on a 56 kbit/sec |
| 61 | analog telephone modem, this extra script code would download in |
| 62 | about a second. |
| 63 | |
| 64 | Most JavaScript-based Fossil pages use less code than that. |
| 65 | |
| @@ -223,11 +223,10 @@ | |
| 223 | The primary difference between these two for our purposes is that |
| 224 | NoScript lets you select scripts to run on a page on a case-by-case |
| 225 | basis, whereas uBlock Origin delegates those choices to a group of |
| 226 | motivated volunteers who maintain allow/block lists to control all |
| 227 | of this; you can then override UBO’s stock rules as needed. |
| 228 | |
| 229 | |
| 230 | 10. “**My browser doesn’t even *have* a JavaScript interpreter.**” |
| 231 | |
| 232 | The Fossil open source project has no full-time developers, and only |
| 233 | a few of these part-timers are responsible for the bulk of the code |
| @@ -555,11 +554,11 @@ | |
| 555 | |
| 556 | As of mid-2020, the informal provisional plan is to increase Fossil |
| 557 | UI's use of JavaScript considerably compared to its historically minimal |
| 558 | uses. To that end, a framework of Fossil-centric APIs is being developed |
| 559 | in conjunction with new features to consolidate Fossil's historical |
| 560 | hodge-podge of JavaScript snippets into a coherent code base. |
| 561 | |
| 562 | When deciding which features to port to JavaScript, the rules of thumb |
| 563 | for this ongoing effort are: |
| 564 | |
| 565 | - Pages which primarily display data (e.g. the timeline) will remain |
| 566 |
| --- www/javascript.md | |
| +++ www/javascript.md | |
| @@ -46,20 +46,20 @@ | |
| 46 | [cg]: ./contribute.wiki |
| 47 | |
| 48 | |
| 49 | ## <a id="debate"></a>Arguments Against JavaScript & Our Rebuttals |
| 50 | |
| 51 | There are many common arguments against the use of JavaScript. Rather than |
| 52 | rehash these same arguments on the [forum][ffor], we distill the common |
| 53 | ones we’ve heard before and give our stock answers to them here: |
| 54 | |
| 55 | 1. “**It increases the size of the page download.**” |
| 56 | |
| 57 | The heaviest such pages served by Fossil only have about 8 kB of |
| 58 | compressed JavaScript. (You have to go out of your way to get Fossil |
| 59 | to serve uncompressed pages.) This is negligible, even over very |
| 60 | slow data connections. If you are still somehow on a 56 kbit/sec |
| 61 | analog telephone modem, this extra script code would download in |
| 62 | about a second. |
| 63 | |
| 64 | Most JavaScript-based Fossil pages use less code than that. |
| 65 | |
| @@ -223,11 +223,10 @@ | |
| 223 | The primary difference between these two for our purposes is that |
| 224 | NoScript lets you select scripts to run on a page on a case-by-case |
| 225 | basis, whereas uBlock Origin delegates those choices to a group of |
| 226 | motivated volunteers who maintain allow/block lists to control all |
| 227 | of this; you can then override UBO’s stock rules as needed. |
| 228 | |
| 229 | 10. “**My browser doesn’t even *have* a JavaScript interpreter.**” |
| 230 | |
| 231 | The Fossil open source project has no full-time developers, and only |
| 232 | a few of these part-timers are responsible for the bulk of the code |
| @@ -555,11 +554,11 @@ | |
| 554 | |
| 555 | As of mid-2020, the informal provisional plan is to increase Fossil |
| 556 | UI's use of JavaScript considerably compared to its historically minimal |
| 557 | uses. To that end, a framework of Fossil-centric APIs is being developed |
| 558 | in conjunction with new features to consolidate Fossil's historical |
| 559 | hodgepodge of JavaScript snippets into a coherent code base. |
| 560 | |
| 561 | When deciding which features to port to JavaScript, the rules of thumb |
| 562 | for this ongoing effort are: |
| 563 | |
| 564 | - Pages which primarily display data (e.g. the timeline) will remain |
| 565 |