I'm having a hard time understanding your comment as a whole, but from a "europe"-centric perspective:

> If it would be possible to walk to get groceries

It is.

> do people choose to drive instead because it's simply easier and faster?

Some. You also have to factor in the cost of gas (quite high) vs distance vs how much you plan to buy and possibly other factors (like discounts,...).

> They then claim that the goal of exercise is simply not worth it any more given driving is faster (and easier)?

I would think the goal is to get groceries, but yeah. People are quite lazy. The possibility of taking a car or a bus is always there.

I think many saw working with Ramanujan as helping or being involved with a one in a generation (or even higher) talent.

Translating LLM proofs to human-ese is instead grunt-work. One that is bound to dissapear in a few years anyways.

If your goal was to do something for the games you love and understand them on a deeper level, then just handing that off to an LLM doesn't really give you the same sense of accomplishment.

There was a genre of YouTube shorts about Minecraft desire paths. The videos showed increasingly ridiculous attempts at stopping the desire path from forming. The joke of course being that dedicated Minecraft players will somehow make their way even through the unbreakable bedrock. And the admin/owner has to give up.

Unfortunately, the browser is not a Minecraft server. It's a living standard that has to maintain backwards compatibility. The desire path (React, Svelte,...) will always exist. And so will the ridiculous way they tried to stop that.

I have to step in here to say that, at least documentation wise, this is revisionist history.

The original react documentation is fine, but focused almost entirely on class components. What was there on hooks was either outdated or outright harmful.

It's not until 2023, 4 years after react hooks launched, that the new react docs which focused on them were released.

Yes, the original documentation is what I’m talking about. That documentation was not outdated when it was written. It was excellent compared to the standard at the time. The react doc site raised the bar for what we expect from web framework documentation.

Hooks came much later, long after react was already popular.

No humans really needed. The AI could order one of those nice humanoid robots we're making. This mostly solves the "humans need to do it for me" issue.

Of course this needs bootstrapping. But, paying a guy on Facebook marketplace (or whatever) to unpack and turn on your robot for 50 bucks doesn't require superintelligence.

Yes, if you only accept AI could be dangerous if and only if it manages to kill the last human alive, then yes. Everything is sunshine and rainbows. I'm sure the last survivors of whatever is going to wipe us out eventually (be it AI, an asteroid or whatever) will be delighted to know there was actually no danger at all.

Possibly in much the same way humans currently do this: bribing and lobbying, misinformation campaigns, cyber attacks on elections, blackmail. They're already being used for some of these, just perhaps not autonomously.

Integrating React with third party libraries has always been a pain for me.

The re-render model just doesn't quite fit with the way most JS libraries work. They hand you a class that you have to keep around. This can be solved with useState, but you have to use this weird construction `const [instance] = useState(() => new Whatever())`. Or even worse if the library needs an element to instantiate.

Then, you likely need some event listeners. They ended up not implementing useEvent, so this has to happen in useEffect. God forbid if you need to rebind the listener because a prop changes (possibly every rerender) or the library does something heavy on adding them.

Then, if a prop changes and you need to do something (like recenter a map), useEffect.

Occasionally you might want to reach for useSyncExternalStore but then get hit by the identity issue. The return value must be the same between renders or you end up with infinite rerenders. Many libraries just do `return { foo, bar}`. Not good enough for react.

Basically every JS library integration ends up with a thousand use effects, various useMemos (and useCallbacks) and I've never got (or seen) a satisfying result. There's always sync issues or too many rerenders or...

Yeah. I don't want to be conspiratorial, but there is some heavy censorship happening in certain (or maybe most) subreddits.

A good example is worldnews. For a long time I thought it was a pretty good source of, well, news. But at some point I started noticing that certain topics (cough Negativity about Israel cough) which got a decent amount of discussion were deleted as duplicates of posts that came in later and had 0 comments and could not be seen on hot/top/whatever.

Back to your topic, I think this is in large part due to the death of multiple forums and personal websites and the aggregation of everyone to like 4 platforms.

In the past, if you were banned or didn't like one forum, you could find another. Or maybe just post your thoughts on your own website/blog. But now nobody will see it unless it's on reddit, discord or YouTube.

I don't think we can get that back, but maybe a bluesky(-ish) forum/reddit alternative where you can chose who you interact/see posts and comments from would work well. It would take another collosal fuckup to get people to move and even then... Lemmy was alive during the API/third party apps thing and nobody really moved.

worldnews is a really egregious example of what you're talking about. If you say one negative thing about Israel it gets deleted, you get banned from the sub and sometimes even banned from Reddit. Of course other subs do this on other topics too.

And worldnews is still quite tame with it. Other news subs are much harsher in their moderation, especially the EU local ones.