It's basically https://en.wikipedia.org/wiki/Chinese_room – a classic in the philosophy of consciousness and AI.
2,301 karma · joined November 15, 2024
It's basically https://en.wikipedia.org/wiki/Chinese_room – a classic in the philosophy of consciousness and AI.
so extrapolating from that, in another two years it will continue to bamboozle
I think the main point still stands. (And there have been some pretty prescient depictions, e.g. Marvin the paranoid android was a pretty spot-on prediction of Bing. Or perhaps the fact that Marvin was in the training set was what led to Bing?)
So this can actually be implemented in GHC? I've only read through this once so far and not understood more than ¼, but the section right before the conclusion made it seem like the best you can do is O(n^2.82) along with a huge constant.
Except for the 90% or more of the world's 7000-ish languages which have barely any data online.
E.g. the huge CommonCrawl corpus has stats https://commoncrawl.github.io/cc-crawl-statistics/plots/lang... for only 160 languages. English takes up nearly half the corpus, and after the top 16 or so all languages have <1% of the corpus, over half of those 160 have <0.1% and the other 6000+ languages are distributed amongst the <unknown> category. The long tail is very long.
(You'll see people use the term "low-resource language" and then talk about Finnish or Macedonian – if you're not a linguist and you've heard of the language, it's most likely not low-resource ;-))
Yeah, big trucks have started showing up in Norway too unfortunately, it's making it much harder to keep our environment of freedom and responsibility :(
https://cdn.masto.host/federatesocial/media_attachments/file...
* https://github.com/digitallyinduced/ihp/ is mainly written with Claude now
* https://jappie.me/haskell-vibes.html is gushing over agent-written Haskell
* https://discourse.haskell.org/t/anti-llm-sentiment-considere... huge thread about the divisiveness of LLM's from some person who loves using them with Haskell
I can see how agent coding is a nice fit for Haskell, since LLM's tend to be best at tasks where you can easily verify the output – and GHC lets you easily verify much more of your domain than say Python (sure you can test some of what dynamic typing doesn't catch, but LLM-written tests do not always do what you think they should[0]). At the same time, the LLMs tend to not code golf unless asked to, and they don't care if they have to wait for dependencies to compile, so that takes away the two major Haskell time sinks.
[0] https://haskellforall.com/2026/05/type-out-the-code#:~:text=...
> Despite the responses being identical for the UK and US, Copilot produced a rich, detailed summary of how US and UK respondents differed.
I'll bet there are lots of people trying to use llms to "discover" differences in datasets and just seeing whatever biases were in the base training data instead. Good that someone is out there showing how badly it can go, though I doubt the people who need to see it will :-/
and p17
https://cdn.vanderbilt.edu/vu-URL/wp-content/uploads/sites/4...
The fact that it wasn't thrown together in a weekend is the reason why we have both map and fmap, and why monoid wasn't originally an extension of semigroup (it is now). Haskell started out without that, then later added fmap and semigroup.
In any case, those are not real concerns when programming with Haskell. The actual concerns are more like "why do I have to wait for all this lens dependency stuff to compile just to fetch an url" or "why does the language server need so much ram"
That is insane.
Source: https://www.energy.ca.gov/data-reports/energy-almanac/califo... under Additional Information about the Data:
> The use of the terms megawatts and kilowatts as descriptive of battery energy storage is to effectively convey the instantaneous power contribution of battery storage as comparable to the power produced by grid-level generators. We recognize that energy capacity in the context of energy storage typically refers to the total energy a battery can hold in watt-hours, kilowatt-hours, megawatt-hours, etc. However, for statewide planning and reliability purposes, understanding the peak power capability of battery energy storage systems allows for the integration of data with the nameplate capacity of traditional power generation units serving the grid. It is in this context that battery systems are able to be effectively compared for their ability to serve the grid over short periods of time, typically two to four hours per day depending upon system conditions.