Why RNX?
sudhirvkumar opened this issue · 0 comments
Philosophy
Inspired by the PonyLang philosophy
Get Stuff Done
-
Correctness. Incorrectness is simply not allowed. It's pointless to try to get stuff done if you can't guarantee the result is correct.
-
Performance. Runtime speed is more important than everything except correctness. If performance must be sacrificed for correctness, try to come up with a new way to do things. The faster the program can get stuff done, the better. This is more important than anything except a correct result.
-
Simplicity. Simplicity can be sacrificed for performance. It is more important for the interface to be simple than the implementation. The faster the programmer can get stuff done, the better. It's ok to make things a bit harder on the programmer to improve performance, but it's more important to make things easier on the programmer than it is to make things easier on the library/runtime.
-
Consistency. Consistency can be sacrificed for simplicity or performance. Don't let excessive consistency get in the way of getting stuff done.
-
Completeness. It's nice to cover as many things as possible, but completeness can be sacrificed for anything else. It's better to get some stuff done now than wait until everything can get done later.
- Reduce time spent debugging code to 0 (Zero) Seconds.
- Beginner friendly.
- Upgrade dependencies easily.
- Simple import
import RNX
no need to hunt for libraries on the internet to use them. - If there are any issues with external dependencies then appropriate error message should be thrown immediately in development.