A few decades ago, the only well-known way to deliver something to a server, to make it accessible over the internet, was moving files via FTP in Total Commander, FileZilla or FAR Manager, manually copying files and folders from the left pane to the right one. The more advanced among us preferred standard UNIX tools like scp or rsync instead, but the process was essentially the same.
...
The quiet revolution happened in 2000. Not on Windows Server, and not yet on Linux — but on FreeBSD, a UNIX-based operating system that was the default choice for IT professionals long before Linux dominated the space.
FreeBSD is worth a brief aside here, because it differs from Linux in a fundamental way. Linux is a kernel. What most people call "Linux" is actually that kernel combined with a GNU userland, a package ecosystem, and a set of choices that vary from distro to distro — Ubuntu, Fedora, and Arch are all running the same kernel but are meaningfully different systems underneath.
FreeBSD ships as a complete, coherent OS — kernel, userland, base tools, and libraries all developed together, versioned together, and tested together as a single unit. That coherence matters. It's part of why FreeBSD solutions tend to be cleaner and why the base system behaves consistently across installations.
The solution FreeBSD built on top of that coherent foundation was called jails. Announced by Poul-Henning Kamp and Robert Watson and shipped as a native kernel feature in FreeBSD 4.0 in March 2000, jails took the chroot idea and completed it — adding full network isolation, process isolation, and proper security boundaries.
...
- complexity is the default condition
- complexity will grow
- entropy will increase
- local decisions will get made will appear to make sense locally will not roll up will clash at the edges
- we we always have the choice to simplify if we can recognize where the complexity is and if we can arm ourselves with techniques that are going to help us do that
- consistency is the key
- consistency is the mechanism by which we can make we can reduce cognitive load we can or make cognitive load appropriate
- some problems are intrinsically hard, that's fine
- they don't need to be any harder than they are
it really shouldn't be this difficult
Cleanup, Speedup, Levelup.
One package at a time.
e18e (Ecosystem Performance) is an initiative to connect the folks and projects working to improve the performance of JS packages.
We'd also like to provide visibility to the efforts of countless open source developers working to cleanup, levelup, and speedup our dependencies.
We invite you to get involved in the different projects linked from these pages, and to connect with other like-minded folks.
As part of the community e18e effort, this project provides a collection of module replacements (i.e. possible alternative packages).
We provide two things:
Manifests (mappings of modules to their possible replacements)
Documentation for more complex replacements
List of JavaScript methods which you can use natively + ESLint Plugin