this post was submitted on 12 Dec 2024
108 points (100.0% liked)

Programmer Humor

32743 readers
180 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] BlackEco@lemmy.blackeco.com 1 points 2 weeks ago (1 children)

Yeah, the janky foundation made me and my boss wish we chose Java for the back-end multiple times. I like async / await (or coroutines in Kotlin-land), it's easier to wrap my head around than Promises / Futures and I thought I would miss Reactive Programming, but not that much.

[โ€“] yogthos@lemmy.ml 2 points 2 weeks ago

Coroutines are indeed much easier to work with, and I find it shocking that they didn't catch on in Js world. In general though, I find plain sync code is just much easier to reason about and far less error prone. If you can keep IO at the edges, async's not too bad, but in a lot of cases you need to do some IO deep within your logic, and that's when things start to fall apart. Now you have to make everything async, error handling in particular becomes a pain. I think having async is nice as an opt in, but it shouldn't be the default.