i feel my idea of how code should be structured does not really add up with how async rust code needs to be written. I'm used to java-esque encapsulation, splitting things to classes etc. it works quite well in sync world. For async it is more comfortable to have a huge function with tasks in it ?? A bit less pain with the borrow checker, too

@piggo@piggo.space I keep putting off learning Rust but everything people tell me about it tells me I'd like it.

@sun@shitposter.world @piggo@piggo.space This but go

@pwm@darkdork.dev @sun@shitposter.world go is horrible well unless you are one of the people who dont mind extremely dumb design choices like the way date formatting works

@piggo@piggo.space @pwm@darkdork.dev @sun@shitposter.world nigger

@sysrq@lab.nyanide.com @pwm@darkdork.dev @sun@shitposter.world get rekt

@piggo@piggo.space @pwm@darkdork.dev @sun@shitposter.world >blocks me >"get rekt"

@piggo@piggo.space @pwm@darkdork.dev @sun@shitposter.world It's the kind of conversation where I call you a nigger, nigger.