121–130 of 278 posts
"SO goes to great lengths to reduce garbage collection costs, skipping practices like TDD, avoiding layers of abstraction, and using static methods." I don't understand this at all. What does TDD have to do with reducing garbage collection?
Earlier quoted context omitted.
+1 for Dapper - I'm a big fan. It is very fast and we use it to serve our live (mostly read-only) traffic, while using something like Entity Framework for the backend Administrative UI, which has a lot of inserts and updates.
There's a couple of user-contrib projects that do similar things for inserts & updates. Dapper Extensions is the one I'm using. https://github.com/tmsmith/Dapper-Extensions
Anyone else not quite expecting StackExchange to be using a Microsoft stack?
Joel worked at MS on office, Excel if I recall correctly. Jeff's blog is named for a feature from a book published by MS. I would be more surprised if it was MS free.
So this is what, a 2000 request/sec peak? Over 11 servers, that's like 200 requests/sec peak per frontend? The problem with scale-up is if you actually have to get a few times larger, it becomes super expensive. But fortunately hardware is increasing so much that you can probably just get away with it now. There's probably a crossover point we're rapidly approaching where even global-scale sites can just do all their…
Not quite sure how you derive a peak figure from a monthly average; but on average it's more like 560000000/(30 * 24 * 3600) = 216 req/s
Makes me wonder why smaller website teams need dozens of engineers to keep their infinitesimally smaller app running.
Rigid adherence to certain technologies could be a culprit. "We're a Ruby shop!" is fine for problems where Ruby is great, but the limitations of the technology are bound to creep up somewhere. Not using a polyglot approach would be bad.
Usually you want your solution to be just right for the problem; solve the essential complexity but don't introduce any accidental complexity.
Earlier quoted context omitted.
You get +100 rep bonus for linking your accounts, so you shouldn't have a problem being allowed to comment.
You do need to have more than 200 rep on one site though.
Anyone else not quite expecting StackExchange to be using a Microsoft stack?
Earlier quoted context omitted.
Anyone who knows Joel Spolsky would expect a MS stack :)
It's difficult to take pragmatic advice from someone who took the least pragmatic (and most expensive) route for a startup web company.
Earlier quoted context omitted.
Sometimes "efficient" and "easy to understand and be sure is correct" don't have to be mutually exclusive; see this example [1] of Java and Go. Note that the code is autogenerated, so it should be equally efficient. The Go version also happens to be very simple and no different than most humans would write by hand (without trying very hard to optimize). [1] https://gist.github.com/shurcooL/9f94bbd021b4693cf584
It's not clear to me what argument the example is supporting. The Go code is very concise and the Java code is very verbose. The Go code does look more efficient but what is ImpressionData? Where is it checking the string is valid utf8?
Earlier quoted context omitted.
Anyone who knows Joel Spolsky would expect a MS stack :)
It's difficult to take pragmatic advice from someone who took the least pragmatic (and most expensive) route for a startup web company.
* Currently three years of free licenses, all software you download during that time is free forever, and discounted MSDN subs thereafter.