summaryrefslogtreecommitdiff
path: root/wiki
Commit message (Collapse)AuthorAge
* A coda on accountabilityOwen Jacobson2020-01-27
|
* Syntax highlightingRichard Metzler2018-12-23
| | | | | | | | | | | | | | | | | | | | Also I think Go has the better error handling. Because it is only one and it is supposed to be next to the fallible Operation. Last time I counted there were at least these methods to signal an error in JavaScript: - a return value indicating the error, sometimes as magic number (null or -1) - throw an Exception - an error callback function, which is totally dependent on the framework you use You didn't handle any errors in your JavaScript example, because you aren't forced to. In Java, there are Exceptions, but calling code isn't forced to handle unchecked RuntimeExceptions and Errors. And if you handle Exceptions wrong - and there are so many ways to do this, like swallowing or rethrowing without the root cause, you'll need much time to look into your production issues. Go code is explicit and requires the programmer of the calling code to recognize the possibility something might be slightly wrong in some computer sometime. You're still allowed to ignore this warning by using `_` in `a, _ := fallibleOperationA()`, but it is much better and also cheap if your editor has snippet support to just type `ife`and hit tab and atom is expanding it to: ```go if err != nil { return } ```
* Some notes towards a chat serviceOwen Jacobson2018-03-09
|
* Fix argument typo (thanks, Christophe Junke!)Owen Jacobson2018-02-27
|
* Two trivial typos ("repsect", "disasterous")Ben Zanin2018-02-22
|
* I do not like Go.Owen Jacobson2018-02-21
|
* Fix spelling errorOwen Jacobson2017-09-06
|
* Add links to recommended papersKit La Touche2017-08-17
|
* papers pleaseOwen Jacobson2017-08-17
|
* Some notes towards a social network cooperativeOwen Jacobson2017-02-24
|
* Fixed dead sql_mode link (thanks, Will Sheppard!)Owen Jacobson2017-02-08
|
* Update GPG keys.Owen Jacobson2016-12-16
|
* More Dark SoulsOwen Jacobson2016-11-16
|
* A thing about dark soulsOwen Jacobson2016-11-16
|
* Fix formatting of variable "n" in rules. (Thanks, @wlonk!)Owen Jacobson2016-11-14
|
* Some typo fixes in the initial rules.Owen Jacobson2016-11-13
|
* Use negative numbers, rather than Roman numerals, for starting rules ↵Owen Jacobson2016-11-09
| | | | | | | | | | | | | | (thanks, @wlonk!) Kit pointed out a defect in my modifications: > Rule xxvi defines precedence within the immutable or mutable sets as being defined by the lower ordinal number. > > Rule viii gives new rules numbers assigned by GitHub. > > Within the first few turns, a rule can be transmuted from mutable to immutable, or vice versa, and there can be non-unique numbering within a set. So we could end up with rule 6 and Rule vi both being, say, immutable, and no precedence being defined for them. Rather than make a more intrusive change, I've instead renumbered the rules to negative indices.
* Clarify paragraph breakOwen Jacobson2016-11-08
|
* Consistency in wording.Owen Jacobson2016-11-08
|
* Two == threeOwen Jacobson2016-11-08
|
* Minor link formatting fixOwen Jacobson2016-11-08
|
* Some notes towards a Github nomicOwen Jacobson2016-11-08
|
* Some notes about nominal inclusiveness and media response.Owen Jacobson2016-07-28
|
* A note about recordsPath, care of @TheLarkInnOwen Jacobson2016-07-15
|
* Typo.Owen Jacobson2016-07-15
|
* Some revision to my Webpack primer. I made mistakes!Owen Jacobson2016-07-15
|
* 3,000 words about Webpack.Owen Jacobson2016-06-15
|
* More clarification around secrets & risksOwen Jacobson2016-06-05
|
* Add note on secrets, fix indentation.Kit La Touche2016-06-05
|
* Some thoughts on browser app config.Owen Jacobson2016-06-04
|
* fragmentary notes on IF and MUD proseOwen Jacobson2016-04-07
|
* Fixed over-indented lists.Kit La Touche2015-12-11
| | | | | Markdown'll bite you if you're not careful. Four leading spaces is a <pre> block.
* detached-sigs: Use printf(1) to output null byteJakub Wilk2015-12-09
|
* Added notes on bootstrapping grimoire.caOwen Jacobson2015-11-15
|
* Revert to straight-quote apostrophes for now.Owen Jacobson2015-11-01
|
* Some editorial fixes.Owen Jacobson2015-10-21
|
* The GPL as collective actionOwen Jacobson2015-10-21
|
* Notes towards public compensation.Owen Jacobson2015-08-05
|
* Fixup image links for Dokku-based version of site.Owen Jacobson2015-07-17
|
* Backpressure and eviction (thanks, @idcmp!)Owen Jacobson2015-05-25
|
* Observations on buffering.Owen Jacobson2015-05-25
|
* Entry points, with contributions from @aeleitch and @wlonk.Owen Jacobson2015-05-13
|
* Why a camera?Owen Jacobson2015-04-22
|
* More words.Owen Jacobson2015-04-22
|
* An assignment on police power.Owen Jacobson2015-04-22
|
* Typo fix (thanks, @ashok!)Owen Jacobson2015-04-13
|
* Some minor gruntles about `Class.forName`.Owen Jacobson2015-02-13
|
* TinyFugue works on Yosemite.Owen Jacobson2015-02-13
|
* Typo.Owen Jacobson2015-02-02
|
* Stop freaking using Class.forName to load JDBC drivers.Owen Jacobson2015-02-02
|