I tried to re-learn from Vim to Helix but failed. No sure if this is a muscle memory problem or perhaps article is right about the cons Kakoune-like approach for me. Even adapting with something like https://github.com/LGUG2Z/helix-vim did not work. So if you like Helix it probably a good thing that you did not learn the vim at the time.

I am in doubts about async too. For better understanding I have implemented my own executor and io library (even with some tricky async destruction) and I am not quite happy with it. The problem is that in rust there are no other good methods to write safe async code, are there? My impression that borrow checker forbids lots of patterns I know from other language.

I actually found some, but this is Japanese models. The one I have got is Sharp Aquos R2 compact.

I am considering starting a project, and I am finding myself to be more likely choosing C++ over Rust. Lot of libraries like platform SDK, libs like skia, openssl, etc are c++ based. So by choosing the C++ I am having the consistent source code environment, that makes benefits in things like building, code editing and debugging.

As far as I know they offer kubernetes environment in their cloud hosting services, so they may make some actual money out of it

We still build some stuff with VS2005 and it feels very fast and responsive while having everything I usually need in ide. The only thing it missing is modern C++ compiler.

As far as I know in libuv it is not possible to share socket in different event loops. But the point is while it might be possible to build an abstraction to fix the broken API, is not it would be better to have fixed API instead

Also a bad move for company IMO. These funny videos makes some positive feelings on this Note 7 failure, so Samsung would be better to publish more of these instead.

$ grep -r unsafe | wc -l

292

Sure. Hardware is inherently not safe; the key is to build up safe abstractions around it by using the type system.