• 0 Posts
  • 11 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle

  • I have not encountered anything broken, aside from maybe binary app docstring stuff (e.g., automated example testing).

    On the contrary, everything seems precise, reliable, and trustworthy. That’s the thing to really like about Rust – you can be pretty much fearless in it. It’s just difficult. I die a bit in time any time I have a return type that looks like Box<dyn Fn(&str) -> Result<Vec<String>, CustomError>> or some shit . Honestly, the worst thing about Rust is probably that you have to manually specify heap vs stack when the compiler could easily make those determinations itself 99% of the time based on whether something is sized.


  • I like Rust a lot, philosophically and functionally… but it is WAY harder. Undeniably very hard.

    Just try and do anything with, say, a linked list. It’s mind-boggling how hard it is to make basic things work without just cloning tons of values, using obnoxious patterns like .as_mut(), or having incredibly careful and deliberate patterns of take-ing values, Not to mention the endless use of shit like Boxes that just generates frustrating boilerplate.

    I still think it’s a good language and valuable to learn/use, and it’s incredibly easy to create performant applications in it once you mastered the basics, but christ.






  • I used Inbox too, and also liked it.

    But these gmail features aren’t remotely like inbox. They hide the emails behind alternate tabs. Ones you cannot configure yourself. With nearly no indication instead of putting them front and center (but grouped together). They make it harder to see and understand your inbox instead of easier. This post being a perfect example – tons of people didn’t even understand what was going on because of how awful the feature is.

    Inbox was killed and its main features lost with it. They were not folded into gmail.