From d5795ea791bd49a8ef30f1c00c811f3f4975770e Mon Sep 17 00:00:00 2001 From: EuAndreh Date: Tue, 1 Apr 2025 06:09:08 -0300 Subject: src/content/: Tweak asciidoc leftovers --- src/content/blog/2020/11/08/paradigm-shift-review.adoc | 4 ++-- src/content/blog/2020/11/12/database-parsers-trees.adoc | 2 +- src/content/blog/2020/11/14/local-first-review.adoc | 14 +++++++------- 3 files changed, 10 insertions(+), 10 deletions(-) (limited to 'src/content/blog/2020/11') diff --git a/src/content/blog/2020/11/08/paradigm-shift-review.adoc b/src/content/blog/2020/11/08/paradigm-shift-review.adoc index dd31f87..7dd4f78 100644 --- a/src/content/blog/2020/11/08/paradigm-shift-review.adoc +++ b/src/content/blog/2020/11/08/paradigm-shift-review.adoc @@ -148,6 +148,6 @@ Rich Hickey makes a great case for single-process FP on his famous talk //// I find this conclusion too short, and it doesn't revisits the main points -presented on the body of the article. I won't rewrite it now, but it would be an -improvement to extend it to do so. +presented on the body of the article. I won't rewrite it now, but it would be +an improvement to extend it to do so. //// diff --git a/src/content/blog/2020/11/12/database-parsers-trees.adoc b/src/content/blog/2020/11/12/database-parsers-trees.adoc index eed785b..1d5770c 100644 --- a/src/content/blog/2020/11/12/database-parsers-trees.adoc +++ b/src/content/blog/2020/11/12/database-parsers-trees.adoc @@ -181,7 +181,7 @@ I think the best way to get there is by taking the existing code for cbindgen, which uses the {syn-crate}[syn] crate to parse the Rust code{empty}footnote:rust-syn[ The fact that syn is an external crate to the Rust compiler points to a big - warning: procedural macros are not first class in Rust. They are just like + warning: procedural macros are not first class in Rust. They are just like Babel plugins in JavaScript land, with the extra shortcoming that there is no specification for the Rust syntax, unlike JavaScript. FIXME diff --git a/src/content/blog/2020/11/14/local-first-review.adoc b/src/content/blog/2020/11/14/local-first-review.adoc index 0dd3bea..420c886 100644 --- a/src/content/blog/2020/11/14/local-first-review.adoc +++ b/src/content/blog/2020/11/14/local-first-review.adoc @@ -1,4 +1,4 @@ -= Local-First Software: You Own Your Data, in spite of the Cloud - article review += Local-First Software: article review :empty: :presentation: link:../../../../slides/2020/11/14/local-first.html @@ -78,8 +78,8 @@ license expiration allowed. Sure you could change the clock on the computer, but there are many other ways that this type of intentional restriction is in conflict with that ideal. -However, what about unintentional restrictions? What if a software had an equal -or similar restriction, and stopped working after days pass? Or what if the +However, what about unintentional restrictions? What if a software had an equal +or similar restriction, and stopped working after days pass? Or what if the programmer added a constant to make the development simpler, and this led to unintentionally restricting the user? @@ -152,8 +152,8 @@ local-first solutions that already exist. Say the automerge CRDT proves to be even more useful than what everybody imagined. Say someone builds a local-first repository service using it. How -will it change anything of the Git/GitHub model? What is different about it that -prevents people in the future writing a paper saying: +will it change anything of the Git/GitHub model? What is different about it +that prevents people in the future writing a paper saying: ____ In principle it is possible to collaborate without a repository service, e.g. by @@ -197,8 +197,8 @@ Well, I disagree. The problem isn't inherit to the web platform, but instead how people use it. -I have myself built offline-first applications, leveraging IndexedDB, App Cache, _etc_. I wanted to build an offline-first application on the web, and so I -did. +I have myself built offline-first applications, leveraging IndexedDB, App Cache, +_etc_. I wanted to build an offline-first application on the web, and so I did. In fact, many people choose {pouchdb}[PouchDB] _because_ of that, since it is a good tool for offline-first web applications. The problem isn't really the -- cgit v1.2.3