3 ms·
His main argument seems to center around a "reactive socket server middleware" being absent in the .NET ecosystem. I frankly: 1) don't know what that is, and
by blakeyrat 11y ago
His main argument seems to center around a "reactive socket server middleware" being absent in the .NET ecosystem.
I frankly:
1) don't know what that is, and
2) can't even imagine what it could consist of other than a few lines of code exercising System.Net.Sockets.
- felixgallo 11y agothen why are you posting, instead of going and learning?
- trentmb 11y agoI regularly ask questions before seeking knowledge on my own, just to check back on my post a few hours/days/weeks later. The point of asking the question is to leverage others experience to guide your learning, and provide a reference for those in the future that have a similar question.
- felixgallo 11y agoThe post has no question marks, nor does it seek knowledge. Instead, it makes declarative statements implying that the knowledge is actually probably useless.
- trentmb 11y ago> The post has no question marks Correct. > nor does it seek knowledge. Open to interpretation- when someone claims they don't know what something is, I interpret that as an invitation to explanation, exposition.
- blakeyrat 11y agoI'd much rather someone write a one-sentence description of what the library does in plain English, so I (and everybody else reading the article) could get the "learning" without the "going". Since you didn't tell me what it does, I'll assume you have no idea either. ;)