Griffinsauce

> theoretically > they believe

Exactly. From my experience: the times I've found an ad relevant and worth clicking is about one-to-a-gazillion. Maybe relevance is higher for others but that still doesn't necessarily translate to real value. (ie. your life was improved in any way)

Also, this all presumes the targeting actually works and the current sea ads for shoes I just bought disagree with that. It's all just spam.

> The internet only took off because the primary business model which ran on ads and derivative information that servers do to their users.

Arguable, on the other hand it did kill the internet. (or, almost so far, we'll see whether we rebound after decades of enshittification)

It took me less than 1 minute to find contemporary news reports. Come on.

There's a Dutch idiom: no shine without friction.

AI is all about losing every possible bit of friction, severely underestimating the value that friction brings.

Why? The permission dialog is crystal clear.

This take is the death of joy.

Look up in an old city, look at the facades of the buildings. They have quirks, uniqueness, it makes the city almost a living thing. Every time we shave off another edge we lose that. Nevermind the fact that shoehorning everything into the same patterns is actually an antipattern and very good paradigms have been invented after the 90s.

It's not perfect, but I'd rather have a bit of a mess than boring emptiness.

Simple answer right? It makes more money.

Not saying that was OPs motivation but that's obviously why the shift happened.

> But I do take some issue with the alarmist framing of what's going on.

On the contrary, your framing is quite defeatist IMO. The fact that stores get robbed frequently does not mean we should just normalize that and accept it as a fact of life.

Then don't bomb it.

"we couldn't tell whether it was a legit target" does not fly as a reason to continue.

Not with Raycast :D

Two problems: - people would need to know how to effectively include dependencies in a way that allows them to be tree shaken, that's a fragile setup - polyfills often have quirks and extra behaviours (eg. the extra functions on early promise libraries come to mind ) that they start relying on, making the switch to build-in not so easy

Also, how is this going to look over time with multiple ES versions?

You wouldn't if you look more deeply at this. He doesn't push for simplicity but for horrible complexity with an enormous stack of polyfills, ignoring language features that would greatly reduce all that bloat. .

Joke's on you, we implement all animations in JS

This could also apply to the recent wave of hate towards Next.

4 minutes?! How large is that app?

Not meant as a gotcha but I'm surprised because people always tout it as being so much faster than Next. (4m with Turbo would have to be a crazy huge app IME)

An example that is hard to follow defeats the point. It's just showing what pattern is possible and you can imagine the abstraction layers and indirection that would make it happen accidentally.

In the words of the comment: the rough edges are what make you.. you!

Keep polishing and everything eventually turns into a smooth shiny ball. We need texture, roughness, edges.

Is there a name for this phenomenon? I've taken to calling it "the nihilist's excuse"

Aside from that unlikely read, this deal was still used as a pressure point on Anthropic, there's absolutely no way OpenAI was not used as a stick to hit with during negotiations.

What is your red line?

This stood out to me as well. The level of discourse is incredibly low compared to other topics. Huge amount of "next/vercel sucks" without any constructive or deeper argument made.

There is a similar vibe on the Next.js subreddit, just enormous amounts of shallow negativity. Very strange.

(I'm not saying there aren't valid reasons to dislike the framework or company but the way it's expressed is consistently incredibly juvenile for some reason)

I've been pushing our apps at work in this direction and it's definitely worth it.

If you're relying on webpack plugins heavily, I'd consider that a liability either way. It's going to seriously hamper your portability to other frameworks and build tools and even new versions of the current ones.

You can easily run turbopack for development / preview environments and webpack for production(-like) ones btw. as long as you don't rely on custom magic.

It's extremely obvious that "main" is more ergonomic. It's sad that we're so resistant to change (regardless of how valid you think the initial trigger was)

That sentence does not give me a lot of confidence. The conclusion does not follow the initial statement at all.

The amount of typos in this comment section is pure gold.

> as well as talking very sycophanticly to you.

That's apparently a feature to a significant amount of people..

There is generally a heavy bias to focusing on abuse instead of outcomes. Who cares that there are some false positives if there is a net benefit, it's just noise.

If you're rebasing a lot, definitely set up rerere (reuse recorded solution) - it improves things enormously.

Do make sure you know how to reset the cache, in case you did a bad conflict resolution because it will keep biting you. Besides that caveat it's a must.

It's not that simple.

I used to enjoy Lostprophets before the news about the singer SAing children came out. You cannot disconnect your relationship with the artist from the art.

Three. He fired three people.

Just posting the "75%" without context is a bit of an odd choice. He explains why in the podcast, but it still feels like he should have specified immediately to avoid assumptions about scale.

People sailing on as if this flip will have another standard flop is wild to me. I guess it may be self protection.