> Having to mark everything as evaluatable at compile time is a stupid, stupid, decision that only C++ could think was a good idea.

What is stupid about it? It makes a lot of sense given how programming languages work.

What sense is that? I've worked on roughly 3 compilers with CTFE

Again, problems that people don't have

Watch this space

"Reduce your quality of life and distance yourself from your friends and family, it's cheaper."

Cramer used it to refer to high growth tech stocks that dominate their markets and have large market caps, Twitter was none of those.

I can't link for hopefully obvious reasons

In user studies it was found that beginner/novice coders (or really, users that aren't SWEs) autocompletion was the most requested feature for improvement in IDE support. It's foundational for understanding what they can write and making sure it's valid.

And that makes sense to me, if you have a lot of experience in a codebase and ecosystem it's not as important. If you don't then typing `.` and seeing a bunch of aptly named methods show up, then snippet completion for their arguments to tab through them, you are immediately productive. Autocomplete turns known unknowns into known knowns.

My org requires screenshots and/or gifs in the PR. Tooling is great, but not everything needs automation all the time when a little bit of manual work needs to be done anyway.

There's more stuff worth breaking today in JS than there was twenty years ago in PHP, and more people that know how to do it.

What are the axes? Is that number of posts per date or total number of posts?

cumulative count of posts having matching URL over time

Netflix (like many businesses) use stock buybacks instead of dividends.

> What is so hard about that?

Media companies have been using the value of "content you want to watch" to subsidize "content you don't know you want to watch" for about a century now, the back catalogs are what will keep you paying but that only retains value so long as new content can be added to it.