On 3/4/19, 1:01 AM, "Carlos Rovira" <[email protected]> wrote:
Royale seems to me more like an option for the future, as a technology and
a foundation that you could use for years and years, so you can target JS
now, but WEBASM in the future.
But all of this remains in the success of Royale. Since if we don't attract
talent to make lots of this happen, maybe will not be better than other
options, and even more risky.
Making Royale moving forward and evolving with all the things we all now is
very difficult. We need people interested in make this happen and investing
time in tasks that are not easy to get.
Yep, getting more folks to contribute code is key. One thing I wish we could
get more folks to realize is that the Apache model has a very low bar for
contribution. If you want to write a bead that tweaks one small thing, we'll
accept it. Some of the other more corporate-driven projects may not. That's
one of the reasons for beads. It allows small contributions that should have
little impact on the rest of the framework.
My 2 cents,
-Alex
