HN user

WolfeReader

755 karma

Any discussion of AI that fails to mention its tremendous cost to Earth should be regarded as suspicious. Like talking about the pros and cons of tobacco without mentioning cancer.

https://unu.edu/inweh/collection/environmental-cost-of-AIs-Enrgy-Use-Carbon-water-and-land-footprints

Posts0
Comments387
View on HN
No posts found.

If you say "publishers require DRM" and then say that publishers sometimes sell books without DRM, you might need to review the definition of the word "require".

Some publishers require DRM. Which is entirely different than the false claim made earlier that "selling ebooks necessarily requires DRM".

Selling books doesn't require DRM at all. I buy DRM-free books all the time.

As an example: Kobo will tell you, at the bottom of each book's page, if it has DRM or not. And it will happily sell you a book without DRM and let you download it.

I already gave a specific example. And since your second paragraph shows that you don't understand what generative AI even is or how it works, you have got some learning due before you continue to discuss AI.

Easy: counting letters in a word. There are tons of examples where AI confidently presents incorrect letter counts as fact. Search it up, really! Good example article: https://wonderfulengineering.com/googles-new-ai-search-think...

If AI was learning and understanding, this would have been solved in 2024. As it is, it's just predicting words that are likely to answer the question.

You're slurping up the excrement of corporations if you think AI is "learning" from reading others' experiences. All it is learning - all it can learn - is what words are likely to appear one after another, with no semantic understanding.

Wow, you are drinking the corporate kool-aid eagerly.

The brain understands concepts. I can say, for example, "a penny saved is a penny earned" and understand that I'm talking about money and savings in general. I've felt the satisfaction of a full bank account and the panic of a near-empty one.

The AI knows that someone once wrote the words "a penny saved is a penny earned" in that order. It has ingested volumes of wise sayings and economic texts to facilitate the statistically accurate words which will follow previous words in the conversation.

They may have been implying it; I'll say it.

Token prediction machines do not produce meaningful output.

It is much more likely that they will regurgitate, without attribution, something meaningful that a human wrote (in their plagiarism/training data).

Meaningful "output" is only meaningful if the author understood the meaning, instead of predicting words in sequence.

Good on them! AI-produced "content" is a DDOS attack on human cognition. It takes more time to review than to produce, and the original coders rarely review the output before creating the merge request. And the planet is paying.

1. Ease of use. Other VCS have more consistent command line interfaces; Git's interface has to be studied. In practice, people end up using GUIs with missing functionality and then end up searching for help, and a lot of real experts come to rely on powerful wrappers like Magit, LazyGit, or JJ.

(Compare to Mercurial, Fossil or Git; those systems have consistent and usable interfaces. There's much less demand for wrappers or LLM tooling since they're easy to use already.)

2. Preservation of history. Two common commands - git rebate and git push -f - cause commit history to be lost, sometimes permanently. ("Just be careful" and "Just don't use those commands" are useful pieces of advice for an individual, and virtually impossible to enforce over groups.)

3. Conflict resolution. Git forces the user to resolve conflicts ASAP so we often lose information about A. What the conflict exactly was, and B. How the individual resolved it. Most VCS have this issue; JJ allows you to commit the conflict and solve it in a separate commit, which is nice.

"I wish commits could be folded into larger commits so that you can still capture the individual changes but also not see them by default when looking at the history of a file."

Fossil merges do this. More people need to use Fossil; it's got a ton of great ideas.

"If I split a file in two I still want to be able to see blame correctly for the author of the function, not one file as freshly created and the other with a bunch of deletes."

Now this is a good idea that I've never seen in a VCS.

We are in "the future" relative to both works. The current intelligence threatening our planet is an unconscious token predictor, much more like the hostile non-entity in Blindsight (which even speaks to humans via token prediction) than the mechanical persons in Terminator 2.

Those are some incredibly minor advantages. The advantages of ebooks - easy backups, infinitesimal physical storage requirements, searchability, accessibility for people with visual needs - each one of those outweighs every advantage you listed.

Opening lines: "Today we’re changing how code enters the Ladybird project.

We will no longer accept public pull requests. From now on, code changes to the Ladybird codebase will only be introduced by project maintainers."

Seems like a good bottom-line-up-front to me.