I think this will be the biggest sticking point for many devs. The statement from your readme:
It will have no garbage collector because it is a system programming language but it will be very easy to use so there will be less chance of a memory leak
That seems to be a pretty bold assertion; there's a reason why the most popular programming languages today all use a garbage collector. Even using a garbage collector, I've come across many leaky applications in my career. Proving that your compiler can understand when a free call is "necessary" will be a big lift for you.
That said, I'm rooting for the cause here, and curious to see how it pans out...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I know it is going to be difficult
I think this will be the biggest sticking point for many devs. The statement from your readme:
It will have no garbage collector because it is a system programming language but it will be very easy to use so there will be less chance of a memory leak
That seems to be a pretty bold assertion; there's a reason why the most popular programming languages today all use a garbage collector. Even using a garbage collector, I've come across many leaky applications in my career. Proving that your compiler can understand when a free call is "necessary" will be a big lift for you.
That said, I'm rooting for the cause here, and curious to see how it pans out...