Melanie Mitchell (2021) "Why AI is Harder Than We Think." https://arxiv.org/abs/2104.12871
That sentence is not from this paper.
717 karma · joined April 10, 2025
Melanie Mitchell (2021) "Why AI is Harder Than We Think." https://arxiv.org/abs/2104.12871
That sentence is not from this paper.
> Mitchell in her paper compares modern AI to alchemy. It produces dazzling, impressive results but it often lacks a deep, foundational theory of intelligence.
> It’s a powerful metaphor, but I think a more pragmatic conclusion is slightly different. The challenge isn't to abandon our powerful alchemy in search of a pure science of intelligence.
But alchemy was wrong and chasing after the illusions created by the frauds who promoted alchemy held back the advancement of science for a long time.
We absolutely should have abandoned alchemy as soon as we saw that it didn't work, and moved to figuring out the science of what worked.
> It actually does have typed values
Now. As the article points out, they were not part of the initial design, because of the Tcl heritage.
But this situation is not made any better by a blockchain - there's still no way to reverse a transaction except asking nicely and hoping the other party obliges, right?
How do we know that this unusual transaction is you doing what you want and not someone else controlling and defrauding you?
A small well-understood amount of friction that significantly reduces everyone's risk is not an attempt to control your funds.
Old systems with arbitrary delays based on twentieth century processes should be replaced, but not everything needs immediate infinite speed to be valuable.
https://web.archive.org/web/20140210072712/http://www.laurad...
Previously on HN
But according to the graphs in the article, after three years of LLM chatbots and coding assistants, we're seeing exactly the same rate of new software...
Step 1 is establishing a secure means of communication.
/frysquint.jpg
> [2] Another approach: instead of altering IFS, begin the loop with for arg in "$@" - double quoting the iteration variable. This changes loop semantics to produces the nicer behavior, and even handles a few edge cases better. The big problem is maintainability. It's easy for even experienced developers to forget to put in the double quotes. Even if the original author has managed to impeccably ingrain the habit, it's foolish to expect that all future maintainers will. In short, relying on quotes has a high risk of introducing subtle time-bomb bugs. Setting IFS renders this impossible.So does XSLT?
min-width: attr(foo) /* implicitly requires type to be length */
color: attr(bar) /* implicitly requires type to be color */
Unless you wanted to use a shorthand property like border, but restrict the attribute to only one part of it? border: 1px attr(bdrcolor type(<color>)) /* needs explicit type to prevent specifying border-style */
But that would be easier and cleaner to specify separately? border-width: 1px
border-color: attr(bdrcolor) /* implicitly requires type to be color */
In what scenarios does adding the explicit type information help, rather than having the parser infer the type of the attr() based on the context of the call?However, I do have to check it from time to time for one of my jobs (to monitor our Page and events, and respond to customers), and the occasions when I switch to the second profile can still hook me for 20 minutes of scrolling...
Once you have bought the car, you are locked into paying the higher subscription costs, because the costs of switching are much higher than the increased subscription costs. There are no alternative suppliers for "increased performance" of your VW. Thus, the disincentive of lost sales is removed, and VW is not incentivised to keep subscription prices low.
(See also: Netflix)