I have to remind him that, unfortunately, YouTube has no shortage of content and absolutely nothing to lose from false flagging a subset of it, compared to the pushback they get for letting something truly horrible slip through the cracks.

My friend who worked in news regarded this as the first incarnation of "fake news".

As soon as the beer gets canned its got 2-4 weeks where you can drink it and say "wow, that's amazing". After that you'll have it and think "ok, a bit overhyped".

Distributing beer throws freshness out the window. A liquor store may put it in the back for a month before they throw it on the shelf and then your prospective customers won't get the best impression your beer can offer, as it's tarnished while waiting in that can. So now there's this surge of brewery controlled distribution where you make these pilgrimages to buy a bunch of beer that they'd canned only a few days prior, attracting people to enjoy it when it tastes its best and spread the word.

In one case [1] I ended up with a teaser + 3 parter that wasn't super congruent because research for part 3 sort of changed how I would have approached the script for the previous two.

[1] Killdozer Teaser - https://www.podcastdotcom.net/early-bird-news/2019/2/16/s2e4... I - https://www.podcastdotcom.net/early-bird-news/2019/2/24/s2e5... II - https://www.podcastdotcom.net/early-bird-news/2019/3/3/s2e61... III - https://www.podcastdotcom.net/early-bird-news/2019/3/10/s2e6...

I had a similar experience doing a podcast [1] with a group of 6 others, each putting out one episode per day. It felt like failing the group if anyone had to skip their day, as we came close to a year without a break. I'd spend hours researching and scripting my episodes while riding the bus, waiting for a friend at a bar, or just winding down before bed. It was peak creativity for me and I'm happy with how it all turned out.

But after a while we got burned out and decided to stop, with the idea that we'd keep making our own podcasts. But without that mutual duty to release daily, no one to date has actually put anything out. The deadline/responsibility was the only way to make it happen–at least for me.

[1] - https://www.podcastdotcom.net/early-bird-news/2018/8/5/8-5-1...

https://www.youtube.com/watch?v=3tr8JVZdHfc

I think we’re at that point with React today. It’s become the de-facto way to make a web page, oftentimes for the better. People use it on their complex sites so even for a simple landing page, it’s often the most comfortable tool to work with, despite the fact that it’s adding unnecessary complexity. Fortunately for the user, most of that complexity can be absorbed at build time using server side rendering (the client doesn’t even need to have react if the site is truly static).

It doesn’t matter that you have now moved your HTML into a transpiled javascript syntax that spits out a chain of javascript function calls which generates a javascript object that is then fed into a javascript library that builds an internalized DOM representation and, finally, translates _that_ into an HTML string (which, btw, is happening on a javascript powered server). The browser sees the same HTML + CSS that it might have seen if you had just served them a hand written HTML file over Apache.

For some devs, KISS might actually yield an incredibly complex blob of javascript ecosystem goodies, that is at the same time simpler to setup and get started with than remembering how to structure an HTML file ;)