Profiling Deno with Chrome DevTools

This is a period of about 8 seconds. A long-running function is destroying performance. Width is the important axis here, and that huge block in the middle goes very wide. When that happens, one CPU core spikes to 100%. (The other CPU cores will not be used automatically, because Deno processes are tied to a specific thread)

I can zoom in to see the stack at this time. It's `trendingTagsController`. That makes sense, because it's very unoptimized. I know this. As a quick fix, I will cache it, and then consider moving it to a Web Worker.

One of my favorite vegan restaurants in Philly was apparently protested by "The Philadelphia Free Palestine Coalition" simply for serving Israeli food. https://www.cnn.com/2023/12/04/us/palestinian-protest-philadelphia-solomonov/index.html

They chanted "Goldie, Goldie, you can’t hide. We charge you with genocide."

Used to go there and get falafel sandwiches all the time.

When I was coding on Elixir people would say: "You know I'd love to contribute to your Open Source projects, but why did you have to choose a fucking esoteric language that literally nobody understands? Do you even want people to contribute? You should kill yourself."

Now coding in TypeScript, people say: "God I hate JavaScript. I hate the web. I am suffering existential dread about society and the internet 24/7 and I'm going to kill myself."

Which is it???