It feels kinda weird playing with again, after a long time working with .

I mean, it feels a lot like "Hey, did that just worked?" and "All that in just this little code?"

With Rust the questions become "Hey, why isn't that allowed again?" and "All this code for just that?"

@jeancf Someone called one of my pet Rust projects code "Pythonic", so I really don't buy the "all this code for just that" part.

@jeancf Also, like someone commented on Birdsite (

Literally all I do as rustc:

--> src/
6 | Can I do this?
| ^^^^ No. You can't
= note: expected `good idea`
found `idea that needs improvement`
= help: you should:
* find some
* what is this even

error: aborting due to bad idea

@jeancf (The parts where I had to write more code in Rust than Python actually proved to make the code easier to read later, IMHO.)

Actually, I agree that verbosity is not an issue with Rust. Java is a lot worse.

@juliobiason but the REAL revelation comes when you ditch all the ideas about Proper Object Orientation™ and start expressing what you mean as simple as possible, in small plain functions accepting arguments of standard types (as opposed to building custom classes for everything). That's where #Python starts to really shine :-)

@juliobiason well, you can do that with Java too, but you have to ignore community norms, possibly using Java 8+. ^_^

Sign in to participate in the conversation
Functional Café

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!