Been playing around with it very very minimally as someone who has not really coded in 10 years.
I like the syntax in general, it is a straight forward. Their are a surprising number of languages that seem to unnessesarrioll;y stray from the standard C, Java norm for no perceivable benefit.
But it is very very verbose. Most of your code is unwrapping `Option` and `Result`, so you tac `.unwrap()` on every other line basically. Unfortunatly, this can get quite excessive, with many lines containing like 5 internal functions calls all strings into eachother.
Personally, I think they could do something were if you already unwrapped/checked if a result exists, then you could just treat that variable as its unwrapped self from then on in that scope.
I love the concept. And it works fantastically until you hit a use case that the borrow checker does not understand and suddenly you are not allowed to use the elegant efficient solution unless you want to use `unsafe`.
TL;DR: Very very verbose, to the point of unreadability at times. The borrow checker very well might be the single best piece of programming software, if it were perfect, but I am not convinced the downsides out-way the upsides at this point.
As someone who never learned memory management, it is sort of a no brainer.