Because it solves real problems (it's very easy to use, and I use a lot). It works similar with HD wallet in bitcoin or ethereum. In HD wallet, you can derive accounts for many crypto currencies from one seed password which is what master password in lesspass does.

The counters in lesspass, can be used to derive another password for the same website, if one want to change the password for the website.

HD wallet also has the similar functionality. If you want to change the bitcoin address, just derive another account from the seed password.

And the solution to keep the seed password of HD wallet safe can also work with lesspass. such as [OpenSK][1].

[1]:https://github.com/google/OpenSK

Yes. the title was changed which I wasn't aware of.

Origin title: `The missing part of actor-model programming in rust`.

It's a library in rust for actor-model programming like erlang does.

Yes, the msg!() macro is a little painful to write. I think it can be refactored into the pattern like `impl Handler<Msg>`. But beyond that, it supports async/await naturally. :)

Very appreciate the work on bastion, which really gets the spirit of erlang actor programming with the supervisor-ing strategy! The code is clean and well documented, and I cannot believe the project is not well-known by rust communities.

BTW: They are working on Hot-Code Swap.

Read through the code just now.Thanks for the small but powerful project,I have tried to make something similar, but failed. The lib is very close to what I want to do actor-based programming in Rust. It would be great if actor can send message to itself.

Ruby is the first language I really like. The core concept of the language is small, just not easy to get, but the change on how to programming is significant. Sadly, Ruby is not the language for the multi-core world, and many advantages of using it is disappearing. Although Ruby is changing, 2.3, 2.4, maybe 3.0, but what's the difference?

First of all, Ruby has a very ambitious goal for version 3.0, which most likely involves some kind of thread parallelisation.

Second, I would not say Ruby is not a language for the multi-core world. There are tens of thousands Ruby production environments over the world that make excellent use of multi-core machines. They run Ruby on problems that are embarassingly parallel such as web applications using process managing application servers such as Phusion Passenger or Unicorn. This is the way many modern web application platforms parallelize, including Node.JS and Python.

Third lack of paralellization is not a language feature. Both JRuby and Rubininus support threads without a GIL. Projects like Celluloid and Concurrent-Ruby make use of this.

1. Ruby will support parallelization, it’s just a matter of time.

2.Passenger and Unicorn are multi-process, which due to developers can make use of nearly nothing in Ruby, and that's why gems like https://github.com/grosser/parallel come out.

3. The language implementation detail matters a lot. Too many gems are not thread-safe. JRuby is an option, but not that good, as there're too many other options under JVM platform. Rubininus is awesome, I wish it comes out earlier.

You should check out Elixir. It is heavily inspired by the Ruby language yet makes concurrency easier than many other languages.

yeah, Elixir is a good option, indeed.

> Sadly, Ruby is not the language for the multi-core world

MRI isn't the implementation for the multi-core world, but MRI isn't the only Ruby implementation; on language features, JRuby, particularly, isn't particularly far behind (the current version runs Ruby 2.3 code; I wouldn't expect 2.4 support to be that far behind), and fully supports thread-based parallelism.

Have you used concurrent-ruby?

https://github.com/ruby-concurrency/concurrent-ruby

Yes, from the beginning, and there exists celluloid which try to implement actor model. The fact that concurrent-ruby cannot be truly parallelized just disappoints me. The same idea of Future,Promise applied to Ruby doesn't gain the benefit. At last, it's just a method of writing 'better' code, not getting better solution.

Does this fix the issue that is the GIL?

> Ruby is not the language for the multi-core world, and many advantages of using it is disappearing

Not really; it depends on the audience. The Ruby audience is still mainly Rails development, whose paradigm is multi-process.

Rails is an excellent framework, but it isn't a feature of Ruby. When some other frameworks are rising, Ruby can lose quickly.

maybe you should try crystal.

It's definitely worth trying! I have used akka-stream once, and always expect something like that in erlang world. Finally, here it is. Thanks for the Elixir team.

Thanks for the link. Very helpful.

I think this should be post here: https://dockyard.com/blog/2015/11/18/phoenix-is-not-rails

It's very interesting to see such different philosophies.