HN user
bradmwalker
The future of Docker, Inc. is being an Oracle acquisition.
Encapsulation can be useful.
Git log -p -S <function name>
An undersold benefit of GraphQL is minimizing JavaScript footprint on domain logic. This can be hidden in the API by precomputing many things, and client-side logic can be reduced to presentation and event handling. Hand-rolled data munging and client-side caching are n't necessary, and there's a clean separation between the browser and the backed.
Syntax (and to some extent, expressiveness/conciseness) is superficial. How the code feels under change matters more.
Another red flag on redux: recommended practice--query JSON over HTTP (likely backed by an RDBMS), renormalize the hierarchical data, and then reshape the renormalized data before passing to components.
What stops hiring managers and potential colleagues?
I've been shopping for a future proof workstation (10Gbps Ethernet 8x + 2 16x video cards) that couldn't quite fit on a Xeon E3.
10x developers outsource production to Do(ker.
Try CREATE TABLE UNLOGGED with postgres. The diversity of RDBMS and SQL dialects defeats the point of integration testing the persistence layer with SQLite.
Systemd works inside LXC and systemd-nspawn.
How much energy will be spent thrusting this regressive pig?
Aren't unicorn valuations based on the likelihood of winning a winner-take-all race?
REST: JSON CRUD over HTTP https://youtube.com/watch?v=oVE6OF-d1oQ#t=02m02s
SQL needs marketing. Become obsolete unless you understand this durable persistence and functional, high-leverage reporting service!
Redux uses Event Sourcing. ES's trade-offs apply.
Recent versions of systemd-nspawn can directly download a docker image and run it in a service unit.
For single-node applications, I develop on a LXC setup with a base template of the distribution that will run a production VM. This combination provides maximum dev/prod parity, the benefits of lightweight virtualization for development, and a boring, battle-tested production environment. The setup and deployment is written once for the choice distribution.
What about LXC system containers? Differences between hardware and OS virtualization still exist, e.g. immutable system clock, but it's otherwise like running a regular Linux box. An init process that can simulate rebooting, mature system package management, no process isolation that's often gratuitous, etc.