Good write-up, however if you use a language like Javascript which doesn't have threads, you will obviously have to do 'reactive', whether you like it or not.
Promises and async/await make it much more manageable, but some of the drawbacks are still there (ever tried to decipher an error stacktrace in a node/express program? it ain't easy ...)
Haha, you're not a "JS backend" fan I see ... I can sympathize with that, I'm using node/express on a few projects but quite often I ask myself "WHY ... ?"
Good write-up, however if you use a language like Javascript which doesn't have threads, you will obviously have to do 'reactive', whether you like it or not.
Promises and async/await make it much more manageable, but some of the drawbacks are still there (ever tried to decipher an error stacktrace in a node/express program? it ain't easy ...)
Jup. That’s why I explicitly mentioned backend programming. ;)
Yup ... but Javascript gets used on the backend too, obviously ... Node/Express ;)
True :) trying to erase that from my brain whenever I can 😜
Haha, you're not a "JS backend" fan I see ... I can sympathize with that, I'm using node/express on a few projects but quite often I ask myself "WHY ... ?"
Yup, I'm not a "JavaScript for anything" fan 😇
We're using TypeScript for UI Code, Java in the backend.
Wise decision, saving yourself a lot of trouble ... yes and classical threads are fine for the majority of purposes