4 ms·
Using the MS stack for a situation where you will have huge spikes of activity on an app with an expected lifespan of less than 24 hours is not best practice.
by lifeguard 14y ago
Using the MS stack for a situation where you will have huge spikes of activity on an app with an expected lifespan of less than 24 hours is not best practice.
- acdha 14y agoI'm an open source developer – working on Linux servers since 1997 or so, etc. etc. Please stop what you're doing: it's not very funny and it's not helpful, but it does give OSS people a bad reputation. You can host plenty of high volume things on Microsoft's code – Azure, Bing, etc. have proven scale. We can argue about cost, ease of use, etc. but a decent team should have no trouble making a serious service. The problem here is that they didn't hire a decent team – from the sounds of it, it was the usual executive-level schmoozing and managerial incomplete you see throughout large organizations of every type. They could have used HN'a favorite stack and failed just as hard.
- lifeguard 14y agoHey, dogs can swim but that doesn't mean I use them to pull a barge up the river. I will not shut up about the ground truth I and many other people know about Microsoft and their software.
- acdha 14y agoThe way you're doing it won't will anyone over. Open source has been winning where I work because we've demonstrated better results with less cost. I suggest you try to outperform rather than out-market.
- waqf 14y ago> managerial incomplete I'm guessing you wrote this post using autocompetence?
- acdha 14y agoSigh, yes. iOS auto-uncorrection to the rescue!
- lifeguard 14y agoThis comment reminds me of AL Gore lecturing Frank Zapa.
- eli 14y agoA poor craftsman blames their tools.