sysexit

4 ms·

1.
by sysexit 9y ago
The technology behind this is really cool. It's based on a DAG instead of a blockchain, which should make this a lot more scalable (no block size limits to deal with) and efficient (no miners, no electricity wasted on PoW).
2.
by sysexit 10y ago
I believe this is exactly what's needed..
3.
by sysexit 10y ago
I called it here, right at the initial announcement: https://news.ycombinator.com/item?id=11816951 This is just too hard of a problem to solve frivolously. Kudos to CoreOS for trying, and coming to the inevitable conclusion
4.
by sysexit 10y ago
My day job is not related to containers, but yes, working in the industry has of course biased me (but my opinions are still my own).
5.
by sysexit 10y ago
So 4B for a selling stickers business model?
6.
by sysexit 10y ago
> Kubernetes started out as an extension/modification of Docker, and over time Docker has evolved some of the same features as its kub-based competitors. The result is an uncomfortable integration between partially competing platfor
7.
by sysexit 10y ago
> What is the motivation and benefit for running containers without docker? I believe that Docker bet the company on the wrong business model. Therefore knowing that you can run containers without Docker can be desirable, as it gives you
8.
by sysexit 10y ago
> Does every mention of an Open Source library or project morally require attribution to the original authors or something? No. But in my view had this been written by an independent journalist, they would describe it as "TensorFlow
9.
by sysexit 10y ago
Pretty classless how Jeff describes TensorFlow as an "Open Source library," without atributing it to Google.
10.
by sysexit 10y ago
> Also, the fact that it's a hard problem is what makes it a compelling product offering. You can't make much money solving easy problems. If they can solve the hard problem, yes. Which I believe is unlikely.
11.
by sysexit 10y ago
I love CoreOS and they've done some super impressive engineering. But really, a new storage system? Rewriting in Go and using etcd for central state management makes things easier, but this is still a hard problem. Some things that n
12.
by sysexit 10y ago
Cheap shot by a company doing backup/DR. Zerto, you have great technology, but chasing ambulances is a poor marketing strategy.
13.
RHEL Atomic: Secure, CoreOS-like Docker Host by Red Hat(redhat.com)
6 points by sysexit 12y ago|0 comments
14.
by sysexit 12y ago
Docker on Docker is way cool. The use case we're trying to solve here is a tad different though: it's to provide virtual infrastructure for the "first level" i.e. in the case of Docker the outer container host. For Docke
15.
by sysexit 12y ago
Well, from a customer point of view it's just a regular hypervisor / guest setup. The levels below are required to make an IaaS cloud look more like the datacenter. The underlying assumption is that the bigger flexibility you have
16.
by sysexit 12y ago
I guess you're being sarcastic. What you describe is accurate. In fact, there's one level more because the Linux instance you run is already running as a nested guest. So in your scenario there's 3 hypervisors involved (Amazo
17.
by sysexit 12y ago
Fortunately Rust has unsafe { ... }
18.
by sysexit 12y ago
A release that seems somewhat rushed, and a Red Hat media event tomorrow. I wonder if the two are related.
19.
by sysexit 12y ago
Agreed with some of the other posters that this isn't a bug. It would be pretty hard for a browser to make this not work. To make it not work, the browser would have to check whether there's data available in the local socket bu