BTW, I don't mean this thread as an attack on MS or Google. It's more that if I could take a sabbatical from my job and intern somewhere to learn from them, Amazon would be at the top of my list and I don't think many others would put any company in my top 3 in their top 50.
-
Show this thread
-
I've also never understood Widows snobbery. StackOverflow was running on 11 IIS boxes + 4 MySQL boxes in 2016, could tolerate failing down to 1 IIS box. Meanwhile, some trendy SV companies were serving multiple orders of magnitude less traffic at multiple OoM greater cost.pic.twitter.com/iBNu8yQokW
4 replies 7 retweets 50 likesShow this thread -
PG also says: Python programmers are smarter than Java programers, good hackers prefer Python. Odd, Google was built on Java & C++ (w/some Python). But if you were on the MS stack you wouldn't have to choose between the perf & IDE support of Java and Python expressiveness.pic.twitter.com/i0f0aMr4oy
3 replies 3 retweets 22 likesShow this thread -
Until Kotlin, there wasn't a mainstream non-MS language that had anything close to the same combination of: * Performance * Ease of use / ease of onboarding new devs * IDE suport * General expressiveness (arguably Go, but I would disagree on expressiveness & IDE support)
3 replies 8 retweets 33 likesShow this thread -
Why care about performance? While trendy $1B to $70B SV companies were devoting a ton of time, money, & effort to scaling up a v. low performance stack, SO was humming along with relatively little effort devoted to scaling because they started with a moderate performance stack.
3 replies 7 retweets 50 likesShow this thread -
Replying to @danluu
I'm not sure about "with relatively little effort devoted"
@Nick_Craver &@marcgravell are always trying to squeeze more performance out of the stack.1 reply 0 retweets 2 likes -
To be fair - we do spikes, but just not ignoring it and dedicating some conscious time over the last decade is the main thing (not constant love). That's why MiniProfiler exists: gives us a number in the corner of every page load: put it in every dev's face. Make it a priority.
1 reply 2 retweets 13 likes -
Exactly this. We don't sit there thinking "perf perf perf" as our day job, but we a: monitor load on an ongoing basis, and b: occasionally investigate what the big pain points are, and solve those. We only solve actual problems.
1 reply 1 retweet 20 likes -
Indy, I'm not saying the SO devs don't work on performance. They clearly do. But, due to headcount in 2013/2016, it was impossible for them to have spent 1/10th the effort on perf as some trendy SV companies (that had 1/100th the traffic), even if they were full time on perf.
2 replies 0 retweets 3 likes -
Replying to @danluu @marcgravell and
The thing that's analogous to the first half of the thread is, if you ask who has the best engineering (ex GOOG), people will name some >$1B "startups" that have architectures with serious data loss/corruption problems that are low reliability, low perf, & high operational burden
1 reply 0 retweets 2 likes
The most frequent pick I hear had 2 9s of uptime, an architecture that scaled out to handle 0.5 QPS per VM, 8 figures of annual AWS spend, and rampant data loss & corruption. I find it odd that architectures like that are venerated while simple architectures that work are not.
-
-
Replying to @danluu
Stretch goal on your Patreon should be “Dan sends you a Twitter DM with the name of the 2 9s unicorn.”
0 replies 0 retweets 2 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.