dln_eintr

5 ms·

1.
by dln_eintr 5y ago
I thought we were arguing for rapid iteration and continuous integration? Why would I NOT live as I preach? How can I teach others if I'm not learning bugs, quirks and workaround BEFORE those I work with?
2.
by dln_eintr 5y ago
Maybe using Windows + associated ecosystem for critical, embedded and control systems isn't and has never been a particularly stellar idea.
3.
by dln_eintr 5y ago
Most hierarchies are shallow in practice. Keep it simple.
4.
by dln_eintr 9y ago
By ensuring the proprietary builds are NOT the same.
5.
by dln_eintr 9y ago
These guys have been making some pretty neat controllers for a while now: http://xkeys.com/XkeysKeyboards/
6.
by dln_eintr 9y ago
That would be https://quay.io/ , but also the internet. Since rkt (or appc discovery rather) just relies on DNS/URL hierarchy to refer to images. Any web server can be a "registry". OCI doesn't have an e
7.
by dln_eintr 10y ago
The name doesn't really work in this project's favor. UNIX pipes are stream interfaces, whereas this looks to be message based - that's a fundamental difference. Named pipes are uniquely identified in a well-defined local nam
8.
by dln_eintr 10y ago
rkt actually uses systemd-nspawn to run and namespace the container. What rkt "adds" before that is downloading, verifying managing the container image and setting up the cgroup for resource limitation. https://github.c
9.
by dln_eintr 12y ago
sIFR 2.0?
10.
by dln_eintr 12y ago
Kubernetes also fits very well with Mesos for scheduling. Check out https://github.com/mesosphere/kubernetes-mesos