Security above all.. ok in that case I'll put no undefined behavior ahead of allowing coders to skip the occasional if statement for slightly more speed.
@NotATether Not planning on getting old coins to rewrite their code bases from scratch, more like write a second miner for improved security and performance. But even more so targeting the smaller startups in the crypto space to help deliver them a language that gives them the security and performance they need while getting their projects up and running quickly. Not to mention being able to iterate faster and add new features faster. Actually already have the first two future clients once I get this thing running.
@Syke Rust is actually what inspired this language.. it's got great ideas but the ownership and borrowing is a pain and I've come up with a much easier solution to the problem while achieving similar performance and security.. partly a matter of the compiler doing the ownership part for you, though there are a few cases where it isn't capable of it. It's sort of like the C to Rust's C++.. capable of anything Rust can do but much simpler. And I've both simplified a lot of things languages have taken for granted because the last language did it that way while providing a lot of flexibility and a nice set of core features. The goal is to make the language as intuitive and easy to work with as possible while maintaining peak performance.
Regarding the features you like:
#1 Rust ownership.. like I said I've automated this away so it'll have the performance of Rust, but be roughly as simple as garbage collected languages. Every once you'll need to worry about strong vs weak references but that's rare. Basically you don't need to think about it unless the compiler/IDE has a problem with the occasional edge case and there will be extra checks to make sure you didn't make a mistake in those cases.
#2 Type inference.. planning on it. Initially static and have to fill in the types but one of the first things the IDE will do is fill them in for you so it's as simple to write as dynamic typing but you can see the explicit types should you need them

#3 I agree.. Rust compiler errors/warning are a wonderful example for writing our own.
Regarding beating the Rust ecosystem.. if I can provide an easy way to wrap libraries made in other languages, I can allow integrating their libraries. So I don't need to beat them. It can be like Python that uses lots of C libraries under the covers, though over time there will be incentives to move to pure Flogram. Namely better performance and security as we can reason about native Flogram code better as the language was designed with that in mind.
Thank you for feedback!