Reading this, the return impl complexity seemed insane.
Then, by accident, i programmed on a pet project until 4 in the night, and boom, I’ve had the exact problem they’re solving. Remembered that I usually need an extra lifetime in the impl definition, and boom, it worked. Doesn’t seem so insane anymore.
(Was working on a little Webservice with warp, and returning their filters from a function)
That seems like quite a lot of booms.
Return impl go boom
Gross!
Unprofessional.
This is why no one takes Rust seriously.I have observed people taking Rust seriously. You need to reexamine your assumptions.
We have an evolved capability to short-circuit decisions with a rapid emotional evaluation. It means as a species we didn’t die out early [“that’s a lion; I’m a oerson; lions eat people ergo… Agh!” is not a sustainable strategy] - what’s amazing is that we can also apply it to elarned abstract things like an aestetic sense about programming languages. Such instincts aren’t always perfect, but they’re still worth paying attention to. I don’t see a reason not to express that in a blog post, but you can replace it with “this is unergonomic and in some cases imprecise” if you prefer.
Sorry if I’m missing some sarcasm here, but if this is all you have to contribute, then as a professional software developer, I’d much rather work with the author of the article on a daily basis.
Yep, no one takes the most appreciated language under programmers seriously. The surveys are all constructed to make Rust look better.
At this rate, the US government won’t even consider it as an option! Rust is practically a hippie language.
…and that’s how you drive up metrics.