_xrjp

I found it, Greg's chapter `The Linux Kernel Driver Model: The Benefits of Working Together` on page 267

- https://www.oreilly.com/library/view/beautiful-code/97805965...

- https://github.com/stormtrooper96/books/blob/master/software...

So I'll definitely give it a read. Thanks!

My first time seeing Nix, very promising https://nixos.org/#asciinema-demo-cover

Definitely Nix deserves a try.

From my modest experience with Kotlin few months ago in a small Android project for learning purposes. I can just say that the language resulted very expressive, concise and easy to use for me. Coming from other languages (Go, Rust, C#, JS, PHP among others) but doing almost no Java in the past, I was able to getting started with that Android project few weeks later after have been passed across Kotlin's docs https://kotlinlang.org/docs/home.html

So basically I can confirm "Android’s Kotlin-first approach" https://developer.android.com/kotlin/first

+2

Yes! Using `sans-async` must NOT diminish our productivity in comparison with `async` counterpart.

> at some point, coding event loops became very natural/comfortable for me

In fact it is, I'm very happy with it too.

> one nice thing about rust's async/await is, you don't have to use it, and if you don't, you don't pay for it in any way.

You've said it!

Like Jay says https://www.youtube.com/watch?v=ytfohob38vM It really depends on what do you want to run on and including also how often you plan to upgrade dependencies. But being honest, Arch upgrades are transparent. For example I never got crashes or similar issues upgrading from Arch OS/Kernel dependencies in my daily basis desktop. The issues that I have only faced were with few dependencies coming from the AUR channel that I have installed on demand. So it's not a "crazy" idea to consider to give a try ArchLinux for server-side stuff. Not in 2020.

> I very much like the process of steadily keeping up to date bit by bit, instead of stagnating on a stable base and doing a big bang update every few years. I also like the fact that I don't need to know which version of which release am I going to get, it's always the latest one and it's the one that upstream released.

Yeah, that's also the motivation of this thread from my side. In fact, moving between majors for example has also "risks" to tackle (E.g CentOS 6 to 7 to 8). You know, things that you need to take time to evaluate and test. But in the other hand, having rolling release upgrades makes that headache disappears.

So IMO I believe the Arch rolling release approach will be the next way to upgrade our software on a non-distant future. It's time to try out and test ArchLinux on hot places like servers.

For our modest cloud infra, InfluxData TICK (InfluxDB, Kapacitor, Chronograf and Telegraf) stack has fitted exactly with our needs. We really like its folding building-blocks, interoperability and yeah... easy discoverability and configuration. But also its very convenient InfluxQL which lets us customize reports with ease on InfluxDB.

Basically because of:

> Rust is blazingly fast and memory-efficient: with no runtime or garbage collector, it can power performance-critical services, run on embedded devices, and easily integrate with other languages.