Well the company keeps saying coding is a solved problem.

> Some of the engineers working on the app worked on Electron back in the day, so preferred building non-natively

Why does it matter what tech the engineers used in the past? I thought they didn't write code anymore.

What resources? it's supposedly a solved problem. Anthropic just needs to spend tokens.

Are tokens not resources?

Not to Anthropic

How so?

>taxpayers

Who is paying taxes in this scenario

That's not vibe coding

The cell layers constraint led to better art. The detail in the background was minimal and the artists world compensate for it by interesting framing and lighting. Go back and watch one fish two fish or the black widower episodes from early seasons - just incredible animation.

You can see the number of lines drawn go up like crazy around season 10 or so, making it feel less realistic. Coincidentally, the writing also started to get worse around this time.

Thank you. This just makes sense. In fact, seperating them into different files don't make much sense when you think about it.

Tailwind is not what you're describing.

Isn’t that what utility classes are? Shorthand for inline styles?

Not saying it’s good/bad, but it feels like that’s the use case

It's much more than that because it can make use of CSS pseudo selectors like hover, which is not possible with inline styles.

Under that definition any css class is a shorthand for inline styles

There's a big difference between utility classes which are shorthand for inline styles (random example from Tailwind's site where every single class is a one-to-one mapping with a single style override.):

    class="ml-3 hidden rounded-lg bg-gray-100 px-2 py-0.5 text-xs/6 font-semibold whitespace-nowrap text-gray-700 lg:block dark:bg-gray-400/15 dark:text-gray-300"

and semantic names which use the CSS cascade:

    class="main-content subheading"

Calling that a shorthand for inline styles is just being obtuse.

Media queries, pseudo selectors, extensible design system with sensible and practical defaults, and many more

> Social media is the king of network effects. Almost nothing else compares.

Ecommerce is close second

It's hilarious. The whole point of "vibe coding" is that you don't need to learn or know anything.

It's like saying if you don't learn to use a smartphone you'll be left behind. Even babies can use it now.

That's another dumb thing that unfortunately some people can be led to believe. There have been parents who genuinely thought that screen time would make their kids digitally savvy and prepared for the future.

It has worked out quite well for some of them, but there's a lot of devil in the details of the implementation of that screentime that led to eg Mark Zuckerberg vs Markiplier.

Leave them with an old Toshiba and an Ubuntu cd. Good luck kid.

Nah, a pile of PC parts and DOS and Doom floppies.

I do think there's value in trying out fully vibe coding some toy projects today (probably nothing real or security sensitive haha).

The AI will get better at compensating, but I think some of it's weaknesses are fundamental, and are going to be showing up in some form or another for a while yet

Ex, the AI doesn't know about what you don't tell it. There's a LOT of context we take for granted while programming (especially in a corporate environment). Recognizing what sort of context is useful to give the AI without distracting it (and under what conditions it should load/forget context), I think is going to be a very valuable skill over the next few years. That's a skill you can start building now

Even if that were true you'd still need to be good at UX

The new claude/opus, esp, with additional skills is actually pretty decent with UX.