d357r0y3r

I feel vindicated. I knew this game was bullshit and it couldn't possibly have been a skill issue.

Why? Statins are one of the most well studied drugs in existence. Most people have no side effects, and the long-term benefits are incredibly straightforward - on par with blood pressure medication.

I thought I'd miss all the typing and syntax, but I really don't. Everyone has their own relationship with coding, but for me, I get satisfaction out of the end product and putting it in front of someone. To the extend that I cared about the code, it mainly had to do with how much it allowed the end product to shine.

It really is just mostly this, and social media has tricked people into thinking otherwise.

I was looking at some photos of myself about 10 years ago. At the time, I had been hitting the gym hard, consistently, and intelligently. I had a huge bench press, squad, and deadlift, and was lifting 4-5 days a week, and managed every facet of my diet.

Now, I'm older, have kids, don't sleep as much, and definitely don't make it to the gym as much. I might lift twice a week - and don't try very hard or do progressive overload at all - and try to get in 3-4 days of cardio.

And I honestly don't look very different. Muscles are roughly the same size. In clothes, most people wouldn't be able to tell the difference.

The reason it's faster is largely because it doesn't have all those little quality of life features and extension ecosystem. It's easyish to make software perform well if it doesn't do all that much. If you take base vscode, no extensions, and just do raw text editing, it's hard for me to tell the difference between vscode, zed, or any other editor.

When vscode was released, Sublime was faster - and it stayed faster. But that wasn't enough to stop the rise of vscode.

You can tell by the colors, the icons, the font...most Claude Code apps from scratch will look roughly like this.

I've built significant applications using Monaco, including things that tie into custom LSPs.

They really just should have used Monaco. This will be a burden to maintain and won't be a core differentiator.

What's the story with supporting CommonJS libraries? I've tried to update many projects to ESM multiple times over the years, and every time, I ended up backing out because it turned out that there was some important upstream library that was still CommonJS - or even if we fixed those issues, our downstream NPM consumers wouldn't be able to consume EJS. So then you have to go down this rabbit hole of dual compilation, which actually means using something other than tsc.

I just couldn't figure out what this was in <60 seconds. Examples and use cases need to be a little more prominent in the docs.

You've gotten good at telling the machine what to do. He's gotten good at telling people what to do.

The latter turns out to be a much more effective way to build power and influence.

It is absolutely worth the cost and complexity. The cost and complexity of building a web application using some home grown vanilla JS system will end up being a horrible engineering decision most of the time.

There have been zero times in my career where I thought "hmm, maybe we shouldn't have build this thing in React and let's just go back to page scripts." If you're building landing pages and websites, then okay. But that's not most of what we're all hired to build these days.

Cline is pretty solid and doesn't require you to use a completely unsustainable VSCode fork.

I agree that it's amazing as a learning tool. I think the "time to ramp" on a new technology or programming language has probably been cut in half or more.

By the time I've fully documented and explained what I want to be done, and then review the result, usually finding that it's worse than what I would have written myself, I end up questioning my instinct to even reach for this tool.

I like it for general refactoring and day to day small tasks, but anything that's relatively domain-specific, I just can't seem to get anything that's worth using.

The AI interpretation can be folded into a multidisciplinary approach. We wouldn't merely take AI's word for it. Does this interpretation make sense given what historians and anthropologists have learned, etc.