zlacker

[return to "Had a call with Reddit to discuss pricing"]
1. gaudat+XX[view] [source] 2023-05-31 21:47:34
>>robbie+(OP)
I have a story to tell, about the demise of one of the largest internet forums in my language.

About ten years ago, when smartphones just started appearing, the forum did not have a mobile version, and there are various 3rd party clients on the App Store or Android Market.

Later on, one of the largest 3rd party client was blocked, because of they hammering the forum's servers too hard,. Or something about caching and stealing ad revenue.

Then a couple years later, in 2017, the 3rd party client's devs launched its own forum reusing the client's name. It exploded in popularity and quickly took over as the most popular message board among the youth.

The old forum now has a sort of boomer or mentally ill stigma to it.

I hope to see Apollo go down this route.

Oh, and I think both forums in the story did not monetize as hard as reddit going to paid awards and memberships.

One more thought: Keep the Apollo UI or whatever thing the users are most familiar with. Most of them do not care if it is fediverse or open source or backed by web-scale k8s, they only want it to just work (tm) good enough to post things on it. Eat the lunch you prepared yourself.

◧◩
2. Nifty3+lA1[view] [source] 2023-06-01 03:08:39
>>gaudat+XX
This is what everybody thinks, until they grow large enough to care about the amount of money they’re burning and get tired of it. Then they try to not lose so much money, and their loyal users turn out not to be so loyal.
◧◩◪
3. rgbgra+hC1[view] [source] 2023-06-01 03:31:23
>>Nifty3+lA1
All reddit is doing is storing text and serving it to people.

This not expensive or a hard problem. You grab a bunch of servers, you set them up properly, and then you write your app properly.

No resume-driven bullshit; no hype-driven bullshit; no “we need to be galaxy scale now” bullshit. No email notifications, besides basic “thanks for registering, here is your login” and “here’s a password reset link.” No cloud-based bullshit. Don’t use fucking python. Use a real systems language to eek out as much performance as you can from the hardware. Actually understand databases and how your specific databases work. Use Postgres unless you have a very good reason not to.

Just a few thousand dollars a month, and a brief reprieve from short-term mania to actually think, and you too can literally serve 1 billion pages a day.

Why does everyone run into problems with this? Because they have personal hang-ups and delude themselves (or simply don’t care). This path has been tread numerous times before. The mistakes have been made thousands of times. The people who made those mistakes are available to help you out (for the right price, or if you’re good enough company).

I am sick and tired of systems engineering being grandized, when all you have to do is sit down somewhere quiet and think about the problem — with a bit of tea, and some way to access reference material.

Reddit is not a hard or interesting problem.

◧◩◪◨
4. Maxion+bN1[view] [source] 2023-06-01 05:56:31
>>rgbgra+hC1
> I am sick and tired of systems engineering being grandized, when all you have to do is sit down somewhere quiet and think about the problem — with a bit of tea, and some way to access reference material.

> Reddit is not a hard or interesting problem.

Exactly, tech is full of this weird hubris that everything has to be super complicated and over-engineered.

Heck, while you exclaim disdain for Python, I've seen large web services run on Django and a few servers behind load balancers with very few problems.

◧◩◪◨⬒
5. Karrot+zR1[view] [source] 2023-06-01 06:50:34
>>Maxion+bN1
Care to show some proof? Create random data, store it somewhere, make sure it's about the size of Reddit. Off-the-cuff let's estimate that read traffic is 100x more than write traffic. Create some load generators that generate this synthetic read and write traffic. The load should follow a Zipf distribution of topics. Make sure it can handle huge traffic surges for events or abuse attacks. Show us your read and write performance. Do a small writeup on the architecture you ended up on, the number and types of servers you allocate, etc. You shouldn't be stopping at an order of magnitude short as scaling challenges change as the magnitude of scale changes.

Unlike Reddit, you'll have the benefit of the hindsight of 2023 instead of managing 20 years of tech debt.

◧◩◪◨⬒⬓
6. Attumm+fV1[view] [source] 2023-06-01 07:37:46
>>Karrot+zR1
Instagram has used python and django at scale. They have written about it in their engineering blog[0]. Not sure what their current stack is.

They did resort to all kinds of tricks. But your overal point still stands. The performance of python is lacking memory and it's embarrassingly slow. I hope python4 will have scripted for developing and compiled for production, like Dart. And a great compiler like Rust.

[0]https://instagram-engineering.com/static-analysis-at-scale-a...

◧◩◪◨⬒⬓⬔
7. Karrot+zW1[view] [source] 2023-06-01 07:54:36
>>Attumm+fV1
My question isn't about Python. It's about Reddit being trivial to recreate. I work on an API team at a Big Tech company and, funny enough, a lot of our legacy is in Python and we've scaled it using lots of pretty gross tricks. We may or may not be Instagram (:

The keyword here of course is "at scale". At what scale? Any commenter that believes what was written upthread should create a system and demonstrate that it can scale to Reddit levels.

[go to top]