To be fair, Japan is westernized

This is an interesting concept but unfortunately the article seems like an ad instead of an explanation.

I'd love to see some case studies of this being used in production systems

What are those details?

It generally boils down to three things: 1) How much resource a service need to run well, 2) How much the service wants to consume if left unchecked, 3) How performant you want your service to be.

After understanding these parameters, you can limit the resources of your application by running it under a cgroup. Doing this won't allow a service to surpass the limits you've put onto it, and cgroup will pressure your service when it nears its resource limits.

Also, sharing resources is good. Instead of having 10 web server containers, you can host all of them under a single one with virtual hosts, most of the time. This allows good resource sharing and doing more with less processes.

On the extreme case, I'm running a home server (DNS server, torrent client, synching client, a small HTTP server and an FTP server with some other services) under a 512MB OrangePi Zero. The guy works well, and never locks up. It has plenty of free RAM, and none of the services are choking.

I agree but at the same time: Inter-process communication is also faster when a process is allowed to write to or read from another process's memory. Doesn't make it a good idea, though.

The way I deploy them doesn't mean "compromise one, compromise all". For example, I generally leave SELinux intact. So they're properly isolated.

if I hear the expression "it takes a village" on more fucking time I will quit my job and become a baker

It takes a village to support a successful bakery.

It takes a village to bake a cake! Farmers gotta harvest the wheat, millers grind it to flower, Aunt Mae's chickens gotta provide the eggs, etc....

The only thing I know about you is that you said this. I'm fully convinced that you'd make an excellent baker.

Well, I didn't say "it takes a village". I merely used the word "village".

Yea but I agree with the sentiment of the commenter you're replying to.

It's unfortunately a loaded word now.

that's like 1000€

The book isn't about motivation, it's about steps that you can take that make creating new habits easier. In fact, the book tells you that motivation wanes quickly and we need to force ourselves to create determination instead

Thanks. That sort-of makes sense to me-not 100% but enough for me to get the book.

does that actually work though?

It works but it can be limited in how useful it is and what information you can store. Great if you want to recall larger numbers of ordered or unordered simple items, not as much if you want to use it for remembering notes on every useful book or article you read.

Why do you want to code in the repl when you can code in the editor and eval in the repl?

Because I gain nothing when writing in the editor window - because in _Emacs_ the REPL window works (almost) the same as the editor.

A REPL with Paredit, autocompletion and 'normal' editing capabilities is what I want. That's why I often program other languages (that have a REPL, but no way to comfortably edit using it, like Haskell, PureScript, Elixir, OCaml und Rust) using Jupyter notebooks, which is the same as evaluating inline - that's better than the 'normal' way (only seeing errors/warnings/... inline) but it's not the same experience.

This is really great. I'm not willing to move from IntelliJ but the exceptions and inline evaluation are something I would love to have in Cursive

Inline evaluation is overwhelmingly what I miss from vim-fireplace when I moved to Cursive. Having said that, the code navigation tools are so much better.

Did you get tests to confirm that all of those cases were covid?