“The root of the problem” is a more usual usage, but is just as readily applied (ha get it) as “the root of the solution”, especially when a dental pun can be bonded (puns are swell) to the headline (I can’t think of a way to pun on gumline here).
I found the phrasing really difficult to read and understand, even though I got the pun, so you’re not alone in that.
This isn't about conflict, it's about how humans read it.
Let's say I have two modules, "telnet" and "ssh", and both have a "connect" function. When I read "import connect, (long list of other imports here)" I don't know which connect it is, and I might form the wrong mental connection, which I then have to revise when I start to read the module name.
There's a youtube video from one of the paper's authors and interstellar is probably a stretch but 1000+ AU is far beyond what we can achieve today so not bad.
(other people's) previous guesstimates were 500k - 1M. It does look like you can order it partially provisioned (compute wise I'm guessing) and expand later.
Just today I saw a post (on Reddit) 'Mauling' over whether to get a Framework 16 or not (I assume that English was not their native tongue). Me? I would have just let the bear have it ;-p
Skate author here: please try it out! I haven’t gotten round to diving deep into uncloud yet, but I think maybe the two projects differ in that skate has no control plane; the cli is the control plane.
I built skate out of that exact desire to have a dokku like experience that was multi host and used a standard deployment configuration syntax ( k8s manifests ).
reply