> This particular upper bound is untested since the developers do not have access to hardware capable of reaching this limit.
> However, tests do verify that SQLite behaves correctly and sanely when a database reaches the maximum file size of the underlying filesystem (which is usually much less than the maximum theoretical database size) and when a database is unable to grow due to disk space exhaustion.
Thanks for the link! I read it earlier today and, wow, she was hard sci-fi, as of the early 1900s. I want to call out two things (water harvesting, energy use), but further details will be spoilers.
I reckon she also presaged some of the demographic / cultural re-workings we are experiencing in the 21st century. Hers was a time of radical social reform and political turmoil in the Indian subcontinent, as well as the world. I suppose many urban intellectuals as well as revolutionaries in the hinterland felt a palpable sense of "hang on, this <insert huge transformation> could actually happen, and we could make it happen".
Fertile ground for all sorts of literary imagination.
Ditto... several titles they listed were alien to me! And I had no idea about Rokeya.
Alas, these will have to wait a bit until my next book-funding cycle... I accidentally overdid some Diwali discount book shopping and have a slushpile of about forty scifi titles to work through, and a fiscal deficit to repair :sweat-smile: :D
That said, my extant slushpile has Sci-Fi by contemporary Indian / Indian-origin authors...
Lavanya Lakshminarayan's Interstellar Megachef (next up in the reading Q, along with the Strugatsky brothers).
And SB Divya's books:
Read and enjoyed and will recommend:
- Meru (very cool embodiment of beings, mythologically-inspired)
To-read:
- Loka
- Machinehood
- Contingency plans for the apocalypse
The articles references articles she has written on science fiction, but if one is interested in SFF more broadly, Monidipa "Mimi" Mondal is India's first Hugo nominee, as he co-editor of Luminescent Threads: Connections to Octavia E. Butler, an anthology of letters and essays. This won a Locus award.
Her fantasy novella, "His Footsteps, Through Darkness and Light" was nominated for a Nebula. She also contributed a DnD adventure to "Journeys through the Radiant Citadel"
Every great culture, over the millennia has imagined great weapons and unlimited godlike destructive power. You could, as you are doing now, retrofit our narrative on any of those if you wish. Make your own sci-fi fantasy. Those texts are not.
Nice... I made "Bulk Git Ops" Bash functions to source into shell and tab-complete to invoke. (nb. I organise my sources like this: ~/src/{github,gitlab,bitbucket}/{usernames..}/{reponames..}).
Examples assume that repos you contribute to are spread across
remote hosts, and (hopefully) namespaced sanely. I organise my
sources as follows.
~/src/{github,gitlab,bitbucket}/{usernames..}/{reponames..}
QUERY: Count repos that are stale:
ls_git_projects ~/src/ | take_stale | count_repos_by_remote
QUERY: Count repos that are active (within 12 hours by default):
ls_git_projects ~/src/ | take_active | count_repos_by_remote
EXECUTE! Use 'xgit' to apply simple git commands to the given repos, with logs to STDERR/stty
ls_git_projects ~/src/bitbucket | xgit fetch # bitbucket-hosted repos
EXECUTE! Use 'proc_repos' to apply custom functions to, with logs to STDERR/stty
ls_git_projects ~/src/bitbucket | proc_repos git_fetch # all repos
ls_git_projects ~/src/bitbucket | take_stale | proc_repos git_fetch # only stale repos
ls_git_projects ~/src/bitbucket | take_active | proc_repos git_fetch # only active repos
EXECUTE! What's the current branch? Logs to STDERR/stty
ls_git_projects ~/src/bitbucket | proc_repos git_branch_current # all repos
EXECUTE! With logs redirected to hidden dir for logging (you must create it by hand first)
mkdir -p "${logdir}"
ls_git_projects ~/src/bitbucket | proc_repos git_branch_current 2>> "${logdir}/bulkops.log"
tail "${logdir}/bulkops.log"
Post author here. I'm following the global #AWS outage. #HugOps to the people there, and everywhere restoring service.
Complexity is what it is...
However, I feel we as software people---executive, product, design, engineering, the whole nine yards---ought to think systematically in terms of Software Debt, as software organisations.
;; Clojure source code for `comp` (since Clojure v1.0)
(defn comp
"Takes a set of functions and returns a fn that is the composition
of those fns. The returned fn takes a variable number of args,
applies the rightmost of fns to the args, the next
fn (right-to-left) to the result, etc."
{:added "1.0"
:static true}
([] identity)
([f] f)
([f g]
(fn
([] (f (g)))
([x] (f (g x)))
([x y] (f (g x y)))
([x y z] (f (g x y z)))
([x y z & args] (f (apply g x y z args)))))
([f g & fs]
(reduce1 comp (list* f g fs))))
> This particular upper bound is untested since the developers do not have access to hardware capable of reaching this limit.
> However, tests do verify that SQLite behaves correctly and sanely when a database reaches the maximum file size of the underlying filesystem (which is usually much less than the maximum theoretical database size) and when a database is unable to grow due to disk space exhaustion.
reply