3 ms·
Funnily enough, it is mostly .NET applications running in production that I see stack-traces from these days.
by kawsper 8y ago
Funnily enough, it is mostly .NET applications running in production that I see stack-traces from these days.
- Someone1234 8y agoIf you even know something is a .Net app then the developer is likely terrible, so it is a self-selecting sample. You don't know most of the .Net MVC apps you interact with because there's no reason to know that.
- shawn 8y agoThis is really discriminatory and arrogant. I used to feel the same way. It’s worth changing.
- alexbecker 8y agoI think they mean if you can tell that it's a .NET app (e.g. because they left the X-Powered-By header on), not if it's a .NET app in general.
- shawn 8y agoFacepalm. I've filled my dumb comment quota for the week. Well, at least it was clarified. It got a couple upvotes, so I guess others misinterpreted it too. Sorry.
- detaro 8y agoThat's true for basically every stack
- tomazio 8y agoEver heard of Jon Skeet?
- tedunangst 8y agoBoy, getting hammered for poor phrasing. What's meant is if the stack (whatever it is) bleeds into the user experience, the dev has done a poor job.
- lojack 8y ago> If you even know something is a .Net app then the developer is likely terrible For sake of argument, this is pretty easy to do just by looking at job postings.