As long as you call .collect() on it at the end, don’t need to write the entire type as it is a method with a generic parameter, and returns that generic.

The intermediate iterators though, those are hell. Especially if you pass it to a lambda and for some reason rust can’t infer the type.

I once came across a parsing library that did the parsing with basically just the type system. It was absolute hell to debug and build. Types of parsers would be hundreds of characters long. It would take tens of minutes to build a simple parser.

I don’t know much much time it would take to build a complex parser, since it was unable to. it reached the max type generic depth of the rust compiler, and would just refuse to compile.

I believe it was called Chomsky or Chumsky or something like that. Discovering nom was a blessing.

fully qualified type names make any language awful.

Here’s the same example in rust:

let a = std::rc::Rc::new(std::vec::Vec<u8, MyAllocator>::new());

I believe u8 also comes from a module, so it would be something like std::u8::u8, but I’m not sure.

I don’t know typescript. But if that’s the case, this meme doesn’t make much sense.

Who writes the types of variables in a language with type inference unless forced by the compiler?

It’s also valid rust syntax.

But if it were rust, this meme would not make sense, since you would just type let a and type inference would do its thing. Which is much more ergonomic.

JavaScript (Typescript for the type part) and python, the most popular scripting languages, use the same order as PHP.

It’s usually compiled languages that do the other one.

Take into account that in order to make PRs to a repository you don’t have access to, you have to make a fork of the repo. Which means another repo.

I don’t think there’s a clear definition of either. I’d say if it has no UI, it’s a program. And if it has a UI, I don’t know if it’s a program or an app.

Completely missed my point.

Asynchronous communication means that I send you a message whenever I want and you respond whenever you want.

If I wanted to talk in the moment I would walk to your office or call you.

Messaging makes no sense if I have to remember every message I want to send and send them when the receiver is available. That’s not how it works.

It’s the receiver’s responsibility to read that message when they have to.

I believe this is the same people that will respond “not now, I’m in a meeting”. I know you’re in a meeting. It’s called asynchronous communication. I can message you whenever I want, and you can read and reply whenever you want. The messages won’t go away.

Or even worse “I have not arrived at the office yet”. Then don’t fucking read teams.

Engagement based personalized recommendations.

Just make a file system that maps each file name to 2 files. The 0 file and the 1 file.

Now with just a filename and 1 bit, you can have any file! The file is just 1 bit. It’s the filesystems that needs more than that.