gravity13

Just do what I do: capture everything I've ever written and ask AI to cobble together what I said using my own sentences.

No more LLM voice! Every now and then you might get a nonsensical artifact or two, but that's the price you pay for better groceries.

Sure, but you can build an agentic system which verifies outputs and fact corrects, with probably better accuracy than a human would.

As well, if people were a bit less anti-AI then maybe we can get disclaimers that things are written by AI that don't immediately torpedo any value the writing has.

This is what I'm grappling with myself. I'm building out a bunch of materials for things I'm learning and feel like others can benefit from my trudging through and correcting or getting AI clarification.

I think we're quickly getting to a point where AI is going to be able to do a better job teaching things than humans can (especially stuff with heavy associations with paper/screens, like programming and math). AI can augment for personal styles and spin up whole entire educational widgets on demand. Human's can't scale like that.

pretty sure claude made this one

Well, it's pretty obviously slopped together, which I think the commenter makes clear with "it's nonsensical."

The problems are obvious. The OP is not even toning down the 100 window height's worth of battle tabular data, it's pretty clear that OP just pulled the output from a simple claude code output without any taste or editorialization.

So I think it's pretty constructive. This is a cool map, I thought of doing something similar myself (for Alexander's conquest). It just needs to be de-slopped.

Very extremely. Quite a lovely presentation. I'm definitely having a Patrick Bateman-esque appreciation for that delicate cream background.

At this point, AGI seems to be more of a marketing beacon than any sort of non-vague deterministic classification.

We all thought about a future where AI just woke up one day, when realistically, we got philosophical debates over whether the ability to finally order a pizza constitutes true intelligence.

> "react's complexity isn't worth saving 5 lines of code" which people would agree with.

If you look at the code the example shows, the replication is a bunch of HTML and tailwind CSS classes in backbone. So basically if you decide you want to change the input to have a different radius in one place, you need to implicitly know that there's another piece of code patching and replacing that elsewhere, which has duplicated the code.

I'm not one to pray to the alter of DRY like it's the end-all be-all of programming principles, but you take this pattern and repeat it throughout a production codebase and you have a bunch of repetitions that need to happen.

This is the problem with Backbone - it's edits are imperative - meaning, each one is a source of errors. React makes state updates declarative, so you only need write the rules just once. Somebody coming along to edit the code doesn't need to find the implicit relationships in the imperative code that might break or cause inconsistency, because they don't need to exist anymore.

React is safer. It's not even a contest.

This is how Backbone looked back in the day. Not that I agree with him, but there's nothing new to this, it's essentially a basic View wrapper around a jQuery dom manipulator.

Yes. `useState` is essentially the "two way binding" of React at the component level. You may also enforce two way binding via an external state manager, and pass it to your React components via props.

This is the beauty of React, it's reactive style, that essentially means your UI is always bound to your state.

In Backbone, you do not get this for free, as the problem is that two-way binding in Backbone requires manual re-renders (via jQuery) which are direct DOM manipulations. This is expensive, meaning, it is not performant as your DOM grows.

React solves the problem via it's virtual DOM, which keeps an optimized DOM engine in memory, batching expensive updates onto the real DOM.

This means you get the convenience of your UI always representing your state, which means your code can become more declarative (what you want), and less imperative (what you need to do in order to get it). The author calls this "magic," but as somebody who was a Backbone main turned React main, I call this "sanity."

Nobody wants to have a discussion about [enter argument of the month here] because it's all BS partisan politics motivated by the right's outright disdain for all things liberal in America.

The problem isn't a lack of understanding or research for new vaccines, the problem is anti-intellectualism running rampant.

It seems like there's a lot of propaganda premised on the idea that "both sides are bad", it's just "two sides of the same coin," and it's always the people who know nothing about politics and just want to appear superior without putting any effort or though that give this insidious ideology it's breath of air.