harperlee

There is some research around minikanren that touches exactly that (minikanren is akin to prolog written in scheme, where order is just an implementation detail, and cuts and other non-relational things are looked with suspicion).

Would be interesting to see a movement akin to Asahi / OpenWRT that enables me to run my side project on my fridge or tv!

I'm sure the general population being asked whether they read books have a very clear idea of what a book is.

I don't know a lot about formal verification, but:

So you can formally prove that your e-commerce refund management logic is correct, except for proving that you /processed the refund/. You can't even prove anything about recording the refund in your database, say nothing of proving anything about your interactions with your payment processor.

You could say the same thing about the viability of functional programming on a CRUD webapp, but languages like clojure have been used to great effect here. The fact that thera are important, even fundamental, bits that you cannot verify, doesn't take out value from the fact that you can eliminate whole dimensions of issues.

I won't hesitate to give this to my children, in a year or two when they are reading more fluently and don't need lots of pictures.

Price is also a factor here!

It was posted at 5am in New York... not sure that that was a US view, so the fact that the platform is US-owned doesn't seem so relevant, if there's a global audience.

That being said, I do agree it is a legit thought (and moreso, completely on point in the subthread discussing downsides), and that it shouldn't be downvoted.

"Marjane Satrapi died of sadness a little over a year after the death of Mattias Ripa, her husband and the love of her life"

The simple humanity in this candid description brought a small tear to my eyes. I'd say that the classical approach to this is a dry, clinical description of a depression stage, or a description of a how and not a why. Very welcomed in the age of AI slop!

More strongly, if the pattern matching of a phenomenon totally / perfectly models the phenomenon, and you end up with a perfect model of the phenomenon, that enables you do do causal prediction, how can you NOT call it understanding? What more is there?

Don't know about your landlord specifically, and I'm no landlord, but there's also a bunch of people (including homeowners) that will wait until summer starts to test and then complain about HVAC... just on peak season for HVAC maintenance, where the waiting times are long (and the price will probably be higher).

Then use them! Then those projects will cease having a single contributor or being unmaintained. This doesn't need to be a binary decision (either there is no risk or I won't use it), just choose the project / scope with knowledge that there is some risk in a small community; so internal use rather than client facing, specialized uses, etc.

APL was designed to be written on a chalkboard (if I remember the story right). It is quite dense, and programs are quite small. Reading is slow and requires you to ponder about what was written. You can hold a lot of content in a small amount of 'ink'.

Now, an idea: HN is always complaining that an ipad (or any other tablet) is a consumption device, as it is not designed to be used with keyboard/mouse. Do any of you know if there is an app where you can write APL with a stylus, and has the ability to evaluate expression on the fly, similar to a repl? That would be an awesome thing to do.

Depends on the test design; is an agent competing against other agent in a given match, or against a test? Plus! Does the test's ELO fluctuate?

Hopefully this becomes a reversal in the trend of giving less and less context to the user.

I'm not against the considerations of the article regarding the user and its state of mind, but please do add as much technical detail as possible!

Even if an error message is a cryptic error code, that's better than a "Something went wrong" message. This is not better, or even friendlier, UX. An error code can be referenced, can be searched on the internet, can be passed around on a ticket or on a call... add parameters to your error template, reference the name of the file, the item name that does not respond, the HTTP error code... just give the user some transparency, some agency. Help the client build up a mental model of the error: when / how / why might it be happening.

I'd say Java, because it has a massive footprint amenable for training, and a strong type system (does not have sum types though and those are trendy).

You'd have to steer the LLM to use the style you want, and not massively overarchitect things though, but that's going to be an issue nonetheless.

Would be cool to have a plugin that shows % of bot per user, based on their history of comments.

It's already demeaning to expect them to "learn an accent"

The concept of an accent is broad, but at least part of it you need to learn together with the language, as speaking a non-native language with a thick accent is partly based on the fact that you have yet to learn.

Without being exhaustive, things that might fall into the "speaks with an accent" concept in this thread:

   - Prosody. Prosody can vary per region but a distinctly alien prosody to a language is a barrier for the receptor of the message, that expects a given language and a range of prosodies. E.g. as I know french quite well, hearing english with a heavy french accent makes my brain try to understand what's being said as said in french, and interferes a lot.

   - Sound shifts for particular phonemes. While some of it might be local to the language in certain registers (idea --> /ide"er"/, three --> /free/), others are clearly issues in the target language pronunciation (eg. japanese people having trouble with the l phoneme, spanish people adding an /e/ sound prior to an s-mobile, or v versus b for spanish people also).

   - Connected speech. Where do you end words, how do you omit sounds, etc. Also massive hindrance to understanding.

   - Grammar. Alien grammar is a hindrance to communication. You need to learn that.

Interesting! Could you expand?

There is a lot of hate in the comments but there is some merit to the post existing:

  1. Even if the task is unreasonable, it is good to showcase that the LLM will perform poorly - warning not to be used for diabetes.

  2. As it is a probabilistic model, the approach was to execute it multiple times and look at the distribution. They also tried to minimize variance: "All at the lowest randomness setting these models offer.", the post mentions. Yet the variance of the responses is surprising.

  3. A multimodal LLM should be in general able to discriminate between crema catalana and a cheese sandwich, and provide a textual, uncalculated range of how much calories the item has (internet is full with tables for calorie counting and things such as this https://fitia.app/calories-nutritional-information/cheese-sandwich-1205647).

  4. It is not clear that the "expose" surprised / outraged style is just a communication vehicle or if the author really thought that e.g. LLMs could be hypothetically able to provide confidence estimates.

Fwiw I just thought the same, parse (don’t validate) the bits you like and recreate / reject the input.

I mostly program with clojure. I'd love that I could agree with you. For clarity I was not meaning a culture of improductivity (but it also applies), and more of a trait of the culture that is improductive, choosing to focus productivity on the wrong goals, such as reinventing everything to do it "better", "more data-driven", "decomplected", etc.

You can take it word-by-word and apply to say Javascript, and it would largely feel true - JS arguably has the worst fragmentation of any ecosystem; dozens of competing frameworks, build tools, bundlers, test runners; new frameworks constantly replacing old ones; "Javascript fatigue" is a real thing, etc., but nobody talks about "Curse of Javascript"

You also need to take into account the denominator of "number of users", though. Clojure, with a tiny population, had a cambric explosion of libraries, and now we can't argue that those are dead on one argument, and that those are "done" on the next one. There is a huge fragmentation in the clojure world, and on small populations, that hurts. Case in point: SQL libraries. Korma, yesql, hugsql, honeysql, and those are just the popular ones. Case in point: spec vs. schema vs. malli. Case in point: leiningen vs. boot vs. deps.

I learned Lisp (once) and that opened up path to Clojure, Clojurescript, then Fennel, Janet and Clojure-Dart, libpython-clj, there's Jank that is about to break loose.

As we lispers like to say a lot, the syntax (or lack thereof) is the smallest of the issues. There is a lot of semantic difference between all of those (except libpython-clj, which does not belong to that list; but we could add Hy instead). That's even before starting to talk about library compatibility. So I'd contest whether having a common syntax is a major productivity gain.

I think Idris 2 is targeted more to programming than to doing math, no?

The question then is how they plan to avoid The Lisp Curse (in my words, language giving you too much power makes you do weird things, and you attract people to like to use things a tad too powerful / generic, and you end up with an unproductive culture).

Listen, I’m not a zealot, AI can help a lot, but the default LLM style is unbearable to read.

Warning, AI slop.

In order to mitigate link rot, the book is Numerical Analysis Second Edition, from Francis Scheid (Schaum's Outlines)

For the uninitiated like me:

The manosphere has its own distinct jargon.[31] A central tenet of the manosphere is the concept of the red pill, a metaphor borrowed from the film The Matrix. It concerns awakening men to the supposed reality that men are the oppressed gender in a society dominated by feminism

( From https://en.wikipedia.org/wiki/Manosphere#Jargon, I landed there from https://en.wikipedia.org/wiki/Red_pill_(disambiguation) )

That is not your job, but your role in the group. Being a parent, a child or a spouse, a friend or a running mate, are not jobs. The point of the article is that your identity should not be driven by just one role, that is transactional and will not span your whole life. You need to broaden your target and also understand that you open new roles with each new relationship, plus also you can create new roles into existing relationships.

Another thought experiment:

One by one your neurons are replaced by water. At which neuron are you no longer you?

The fact that there is no clear time to pinpoint for a change doesn't imply that there is no such change... so your thought experiment doesn't really prove that the 'you' is kept.

In the end, Theseus ship is, and is not, the original ship, and both things can be true at the same time.

In Spain it was on the TV also for like a decade, and everybody knows who he is. Also in France.

One is an immediate impact in your pocket, the other one has an impact lag that you count in years/decades.