566 karma · joined September 4, 2011
louisgarman at gmail dot com
They regularly have an article damning France and its dirigism.
There are plenty of poor thin white young tall people out there strugging like most people in life.
Identity politics is dividing us all.
I can see how he has a case for questioning the statistical basis of someone who is arguing there is an epidemic.
But how does that disprove any such epidemic exists?
`RUN apt-get update` and then an `RUN apt-get install -y pkgX pkgY..pkgN`
I could download each package beforehand, tar em and use docker save, but I'd want the recursive dependency tree of packages too....
I always hear this line about the sheer variety of backgrounds of the drivers, and that an Uber job is a way to collect a bit of extra cash. That they have something going on that is far more preoccupying, and that the Uber job is a mere sideline.
In my experience, 9 out of 10 Uber drivers in London are 25-60 years old, from East Africa or the Middle East, and do the job full time if you include working for other mini cab companies. It's their main occupation.
Might well be different elsewhere and probably is, but I can see why Uber might prefer to push a certain story that doesn't reflect reality.
Seems to be a thing of the west to take elements of yoga, tai chi, daoism et al, and distill them - mindfulness comes to mind - and as devices they're good, but together they amount to so much more than the sum of their parts, hence the eastern penchant for a 'holistic' approach.
You can do all the things you've listed. But you can't build an arbitrarily complex DAG of tasks. Instead, you must order everything into a sequential list of 'stages'. Within a stage you have a list of jobs, which are run in parallel. This might be enough for your needs, but I'd like flexibility to express dependencies for each and every task, Say `t1 -> ((t2,t3),t4 -> t5) -> t6`, etc.
And it's a pain to propagate variables from one task to another, like say setting an environment variable in one task, and getting its value in a downstream task. You end up writing scripts to write them to a file, telling gitlab to make that file an 'artifact', and then reading it downstream.
And then there's the transient errors, all of which are listed on open issues. We're using the hosted gitlab.com, and on some of our CI pipelines, we have a dozen or some stages. The chances of a transient error, .e.g. a runner getting a 503 from gitlab.com, are pretty high.
Other than what you say about older people, it is pure conjecture to say that "most of the time" these are the causes.
The explanatory arguments are more than sufficient: skin colour corresponds to the availability of sunlight - with the exception of dark-skinned Inuits who maintain a fish based diet - which indicates the importance of vitamin D to survival.
Only in the modern era do we now spend more time inside than outside, which could be an explanation for increasing incidence of diseases.
As for this ridiculous quote:
> And as Adrian Martineau, clinical professor of respiratory infection and immunity at Queen Mary University of London, points out, even in the summer, “sunshine isn’t going to be the answer, especially because there is an associated risk of skin cancer.”
No, sunshine is the answer. The risk of skin cancer is elevated if you get sunburnt, if you expose your pale skin suddenly to the sun in the height of summer. Nobody is suggesting you do that. Build up a tan gradually throughout the year, follow common sense.
The OCI doesn't, but the build tool does care about how the image was built, because of reproducibility etc. But build tools will be able to leverage the kind of stuff you're doing, rather than doing it themselves (like Bazel does).
- umoci looks pretty cool, this is how things should have been done in the first place.
In order to ensure reproducibility/determinism, however, Bazel doesn't have an equivalent of the RUN instruction. You have to use other Bazel rules to fetch and produce artefacts and add them to an image, and there aren't always rules for what it is you want to do (I have a spot of bother with installing pip packages, for which there is apparently alpha support).
This is, I think, the thing with Bazel: it has to re-invent everything to ensure this reproducibility and hermetic seal, because it doesn't trust existing build tools to do this, and quite rightly so if this is what you're seeking. But I suspect it's going to be painful doing things outside the mainstream supported stuff.
Of course the crap coming out of Hollywood does say something about reality, that there is no hope left other than wish fulfilment, to hope that a saviour will come and save us all in the form of a superhero; or that the only hope for yourself is to get rich or for fortune to be bestowed upon you; or something else utterly implausible. But I've heard that story a million times, it's dull.
[1] https://en.wikipedia.org/wiki/1953_British_Mount_Everest_exp...
Then what does imply turing completeness?
According to the wikipedia article [1]:
"To show that something is Turing complete, it is enough to show that it can be used to simulate some Turing complete system. For example, an imperative language is Turing complete if it has conditional branching (e.g., "if" and "goto" statements, or a "branch if zero" instruction; see one instruction set computer) and the ability to change an arbitrary amount of memory (e.g., the ability to maintain an arbitrary number of variables). Since this is almost always the case, most if not all imperative languages are Turing complete if the limitations of finite memory are ignored."
Re wildlife, yes they would need to be controlled if trees are to take root. Sheep and trees aren't natural bed fellows. I'm not a making a man vs nature argument here; support is necessary in all manner of ways, in some it means taking a hands-off approach.
As for lack of trees in some areas, that might be for a good reason. Not every bit of land is suitable for woodland. Where it doesn't take root, it's a hint. And where it takes root, I would ask how you come up with a figure of hundreds of years.
It will do the very opposite.
> Let's remember that plants migrate slowly!
You initially get lots of 'green stuff' if you plant it yourself. However, weeds are not as slow to take root as you might expect. If you've ever maintained a garden lawn without pesticides, you'll know that.
This plan smacks of "quick, quick lets make this work, to hell with the consequences of not thinking it through". Which is very much the mantra of today's world.
Haste makes waste.
> In densely populated areas, there is no nature; everything that happens or doesn’t happen gets decided by man.
Nonsense, and besides the point. In the densest of cities there is plenty of nature (beside us). And in any case this planned forest isn't being planted through the middle of manchester and leeds.
Even then, if an acre of urban land is left idle by man it will sprout all manner of weeds and, not before long, trees. Many a distopian sci-fi film will show this.
They might be planting "local, mainly broadleaf tree species", but the principle is still wrong. Why attempt to second guess what will work, when nature will do it better than we ever possibly could, saving a lot of labour, too. I'm sure the resulting woodland would be far more interesting.
Same "retina" resolution, but the matte display makes reading text a pleasure.
DevOps Engineer, 15 years experience.
My most recent projects have involved a combination of AWS, Docker, Terraform, Ansible, and Jenkins.
I'm fluent in Ruby, Python, and more recently, Elixir.
My LinkedIn profile: https://www.linkedin.com/in/louis-garman-418b95/
My blog: https://spacebiter.com/
Email: louisgarman at gmail dot com
Having said that, up til around then, times were grouped by the reigning monarch, at least in Britain: Georgian, Victorian, then Edwardian to cover 1901-WWI.