fathead_glacier

Managing state is hard and always has been regardless of the underlying technology.

I have been using Kubernetes for a few years now and whenever I see people putting manual steps they should instead be using an operator. What the author is describing as a problem has a solution (they even added it to their own operator).

Kubernetes has a steep learning curve but if you want to do nontrivial thing like have state than you need to learn nontrivial things like operators.

The default controllers that come with Kubernetes do not cover everything under the sun and they do require extensions via the operator pattern for some tasks.

Just my two cents.

Comparing different metrics is not valid across all use cases. Counting startup time but excluding development time is disingenuous. Having used both Fortan and Julia the difference between development time is staggering.

Different tools for different uses cases is the best way to put it.

The point is when you have a connection with limited bandwidth. In such cases you can host browsh in the cloud and connect to it with ssh/mosh. You get a much better experience than text based browsers at a limited bandwidth.

It's great for such cases - I use it when hiking / working away from good internet.

The article misses an often overlook but important point: burning hydrogen in air produces NOX which can be a more potent greenhouse gas than CO2. The solution to reduce the amount of generated NOX exists but the resultant engine is larger and consumes more fuel for the same power output.

Further, as stated hydrogen is typically produced by steam reforming which generates greenhouse gases. The alternative of using electrolysis requires electricity generated from carbon neutral sources.

Taking all this into account:

- making steel requires electricity, the carbon neutral source can be used here directly;

- land vehicles already have a proven alternative with electric engines;

- naval vehicles do not have the luxury of easily recharging electric batteries.

As a summary I think the solution already exists for steel making and land based transport the problem is widespread adoption and politics rather than technology. Naval based transport can benefit from hydrogen as a fuel source but it comes at the engineering challenge of transport/storage and the associated safety concerns.

The subscription model gives you access to the drafts of the chapters and full book access at 8 months. For $9 at the lowest subscription grade this is $9x8 = $72 which seems like a fair deal to me when going through amazon for similar subject titles.

My experience of speaking with authors who have published books is that most of the money stays with the publisher and not the author which is a real pity. The net effect is the discouragement to write books which is counter to progress.

The subscription model is really interesting to me and I hope it makes a difference to the book publishing paradigm.

One of my lecturers once gave an anecdotal reductio ad absurdum argument of why it is difficult to reduce our carbon footprint: people are not willing to walk from the UK to France for a piece of cheese when they can just drive a few minutes to the store.

It is a difficult problem to solve for a reason.

The example is fundamentally different as physics simulations have closed form solutions or can be numerically approximated for various initial and boundary conditions. Therefore, by definition the generation is not synthetic.

Other examples I could think of fall in the category the top comment is referring to.

Org-mode. Once you get hooked and comfortable there is hardly going back.

Org-mode support todo lists, agendas, scheduling, recording time per task, latex export, references (with org-tef) and executing code in the document (with babel) and more.

To give you an idea of what the workflow is while I am working on my PhD thesis. I write text with references in sections with todo tags, add my python code, execute it and export to latex. Now I can track how much work I did today in what section and I can also see other files in a common agenda. All of this is in plain text files so git work as well and if you decide to migrate a python script can parse it.

All of this in a free and open source solution if you are happy to work with Emacs. In my opinion it is worth it even if you keep a running Emacs version only for this.

Experience can differ between companies and languages. I have been involved over the past year with Julia which is mainly ran and developed by the company Julia Computing. One might say that it is the equivalent operating scheme as the companies you mentioned. However, my experience with the community has been vastly different. If you go over the development issues list it is extremely satisfying to see how many are raised by the community and adopted into the language. In contrast to the omnipotent response of Google with the Go community. Having such differences implies that a company ran open source language can indeed be influenced by the community.

Having said that, just because it exists in Julia does not mean it can exist in Go. I just wanted to mention that there are exceptions to the rule which begs the question if it is a rule in the first place.

I think it will also involve selecting seeds only from "better" performing trees from the city tree gene pool. This will then ensure that beneficial mutations / changes survive. An unfortunate requirement of evolution to force progress.

In a way it will be survival of the fittest for trees. Unfortunately it might take considerable work from urban planners which I cannot see happening on a large scale any time soon.

Maybe a better idea will be to selectively breed species in hard environments and then distribute the seeds to cities that need them. With genetic modifications becoming prevalent in the food industry this might be not far away from happening.

This sounds so good! I just read that Latex support is also included. If there is also an extension to handle references I can move out of emacs / org-mode / orgref because the maintenance cost is too high.

Cannot wait to give it a try.