Yes the compensation sounds fair, but I’m also looking forward to higher priority for RO C# and cross-platform capability issues:
-
I know Silver is immature but free so there are many new users and feedbacks, which is your current focus. But RO C# is not free (I bet if it’s free, it won’t be less popular than Silver) and targets high-quality users that may contribute more valuable feedbacks in their serious development and demonstrate the potential of Elements in their business products.
Now I don’t make any complaint about the Elements VS plugin (like CC, formatter issues etc), because althought it’s actually terrible (many error prompts when I do simple coding in VS daily), I think it’s trivial (I almost do all coding work related to Elements in SublimeText). I won’t report issues about EUnit, because I’ve built my own cross-platform unit test library to replace it after EUnit was broken for iOS months ago. The only things I care are compiler and debugger.
I think I’m one of the typical users who are truely willing to pay money to buy Elements instead of just playing it freely. -
Elements is really potential and distinguishing from other cross-platform solutions. That’s why I don’t give Xamarin/RoboVM things a chance. But I’m also sure that there’s no enough practice in complex business product for Elements.
I choose Elements to implement a cross-platform framework, under which I can write same clean codes for different platforms even including UI. I think my objective is also the ultimate objective of Elements. Then I’ve found many practical issues that can’t be ignored:
2.1) __weak for ARC can’t be ignored for GC platform by default, which is really easy to do for compiler I think. The Cross-platform compatibility you recommended will bring many strange warnings and known and unknown side-effects which is too risky for me.
Are Cocoa Storage Modifiers ignorable on other platforms?)
2.2) Element’s ARC still can’t perform the same optimization as Objc’s compiler for iOS. Cross-platform codes can’t depend on explicit ARP to improve the performance, which will make your codes awkful.
Question about Element’s ARC)
2.3) There’s no elegant solution for value types in generic programming by default. Just try to write a reusable comparer function to sort your cross-platform List<int>, and you will get my point.
Mapped class to wrapped value types can’t work as expected)
These cross-platform capability issues are generic for all users and unable to avoid in serious cross-platform development, so they are more urgent to be fixed than minor bugs in specific language.