4 ms·
Eh, a lot of this looks cool, but doesn't solve any really hard problems. It's easy to mess up a null check, but it's equally easy to find the bug and fix it.
by copsarebastards 12y ago
Eh, a lot of this looks cool, but doesn't solve any really hard problems.
It's easy to mess up a null check, but it's equally easy to find the bug and fix it.
It's easy to mess up a string format, but it's equally easy to find the bug and fix it.
It's easy to mess up a chain of Rx event streams and when you do--you're out of luck buddy. Have fun debugging that.
Async rewriting for error handling does solve a really difficult problem, but there are much deeper problems with using C# for the kind of imperative threading code where that problem comes up. I wouldn't write that in C#, that's certain.
- CmonDev 12y agoNested null-checks are a lot of code without the existential operator: if(){if(){if()}}} vs .?.?.?
- copsarebastards 12y agoLike I said, doesn't solve any hard problems. If having to type an extra few if-statements is the hardest programming problem you have to solve all day, you have a damn easy job. Don't get me wrong: I like that syntax change--I'm all for shorter, cleaner code. But I've moved on from C# because it was ineffective for solving hard problems like multithreading, scaling, networking, crypto. Eliminating a few if statements doesn't fix that.