After having used TypeScript for like forever, writing Go feels like a huge step back in language ergonomics. Some of it because I'm more experienced in TS, some because TS really does have a lot more going for it with things like map().filter().reduce() etc. Let's not talk about error handling. That being said, it's good to be curious and Go does have it's place, which is why I still use it for certain tasks like where I want a single static cross-platform binary.
I always find the error handling argument weird. What do you guys do with your errors? I'm all for optimistic programming, but I've worked on so many projects where you have no luxury of just bubbling your errors up top, as in the end you'll end up having to still write a nasty block of code to actually handle those errors. I feel being explicit with every error just makes it easier to debug.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
After having used TypeScript for like forever, writing Go feels like a huge step back in language ergonomics. Some of it because I'm more experienced in TS, some because TS really does have a lot more going for it with things like map().filter().reduce() etc. Let's not talk about error handling. That being said, it's good to be curious and Go does have it's place, which is why I still use it for certain tasks like where I want a single static cross-platform binary.
I always find the error handling argument weird. What do you guys do with your errors? I'm all for optimistic programming, but I've worked on so many projects where you have no luxury of just bubbling your errors up top, as in the end you'll end up having to still write a nasty block of code to actually handle those errors. I feel being explicit with every error just makes it easier to debug.