Baobab - JavaScript persistent and optionally immutable data tree with cursors

Mnemonist - Curated collection of data structures for the JavaScript language

TaffyDB - JavaScript library that provides powerful in-memory database capabilities to both browser and server applications

WatermelonDB - Next-gen database for powerful React and React Native apps that scales to 10,000s of records and remains fast

In response to You-Dont-Need-Lodash-Underscore made by @cht8687, yes some of the methods could be replaced by native methods. This is not the case when things get a bit more complex. According to the Lodash author, @jdalton:

If you're only using a handful of methods on arrays and don't care about nullish guards, object iteration, smoothing over enviro/ES5/ES6 issues, FP goodies, iteratee shorthands, lazy evaluation, or other enhancements then built-ins are the way to go. Folks who use lodash know its 270+ modules work great combo'ed with ES6, enabling cleaner code and empowering beyond built-ins.

There is a plugin

• Users & Groups

  • Add user to group
    sudo usermod -a -G cdrom userName
sudo usermod -aG vboxsf $USER

• Change root password
  sudo passwd root

A simple "1-click" javascript approach to downloading a scanned book from archive.org to read at your leisure on the device of your choosing w/out having to manually screenshot every pages of the book by hand. In short it's a glorified "Save Image As..." approach but consolidated down to "1 click". BTW there may be a much better option than this out there - I just built this as an autistic project to see if it would work.

By using this script you agree to delete all book files/images after your 1 hour or 14 days is up! I don't support using this script for any other use cases. After all, none of us have ever kept a library book past it's return date, right?

I believe the following is the best way to work with Nagle's algorithm / TCP_NODELAY / TCP_CORK.

It is described in this RedHat manual and the verdict is:

• Set TCP_NODELAY = 1, always.
• If you can batch data for sending by creating a buffer manually, or using writev(), prefer that.
• If you cannot (e.g. "when using different libraries that provides abstractions for layers" from the above manual):
  • Set TCP_CORK = 1, then write the data, then set TCP_CORK = 0.
• This builds a packet in kernel space and then flushes it out.