Wouldn't it make sense to have these wikipedias created by different llms, and compare them to expose their biases?
Readit Newsmanx commented on Grokipedia and the coup against reality thedissident.news/grokipe... · Posted by u/coloneltcb
manx commented on Testing a compiler-driven full-stack web framework wasp.sh/blog/2025/10/07/h... · Posted by u/franjo_mindek
Have any studies been done on the use of newer or less popular programming languages in the era of LLMs? I'd guess that the relatively low number of examples and the overall amount of code available publicly in a particular language means that LLM output is less likely to be good.
If the hypothesis is correct, it sets an incredibly high bar for starting a new programming language today. Not only does one need to develop compiler, runtime, libraries, and IDE support (which is a tall order by itself), but one must also provide enough data for LLMs to be trained on, or even provide a custom fine-tuned snapshot of one of the open models for the new language.
It's not only the amount of code but also the quality of the available code. If a language has a low barrier to entry (e.g. python, javascript), there will be a lot of beginner code. If a language has good static analysis and type checking, the available code is free of certain error classes (e.g. Rust, Scala, Haskell).
I see that difference in llm generated code when switching languages. Generated rust code has a much higher quality than python code for example.
manx commented on Learning Languages with the Help of Algorithms johndcook.com/blog/2025/0... · Posted by u/ibobev
I fully agree with this approach! 5 years ago I built a prototype to execute that same concept of language covering. But instead of just using words, I used n-grams. It ii trained on subtitles to model spoken language. Combined with sqlite in the browser to get the next sentence with the most impact.
github here: https://github.com/fdietze/ravioli
prototype deployed here: https://raviolio.web.app/
I mean honestly my question is why should I bother ?
Java has memory safety and near native performance, the only thing going on for Rust is fearless concurrency which is a USP I think but not enough for me to bother learning its complicated syntax. Had I been unbelievably productive in that language, that would have sealed the deal completely. But alas.
I think memory safety is a weak argument for rust and only works against C/C++, as you mention. For me, the strongest arguments against GCed languages are static analysis goodies that other languages don't have. Like checked immutably by the compiler, the borrow checker which forces you into a certain architecture, fearless concurrency etc. All those lead to fearless refactoring, which is a very strong point for me.
This pre-AI article makes a very similar argument: https://mortoray.com/programming-wont-be-automated-or-it-alr...
Once we realize that what we actually want is turning specifications into software, I think that English will become the base for a new, high level specification language.
manx commented on Social media promised connection, but it has delivered exhaustion noemamag.com/the-last-day... · Posted by u/pseudolus
Like most of the other commenters here, I agree that modern social media is often an echo chamber, and frequently surface level.
I'm curious if anyone has any thoughts, what would a social media built for nuanced, meaningful interaction look like? Could there be such a thing?
Search for "bridging based ranking". The X community notes algorithm does that. I think it should be applied to all content.
manx commented on Clojure's Solutions to the Expression Problem infoq.com/presentations/C... · Posted by u/adityaathalye
This example just scratches the surface.
I don't think it's showing any Clojure-magic per se,
b/c in effect what you're showing is just "implementing an interface".
You can do that in most languages.
The magic of protocol/records is that they work across library boundaries. A library may provide a record - and then you can extend the record with new protocols. Key is that it's all without needing to explicitly creating new agglomeration types.
You can take some Dog record from some pet-simulation library and then `extend-type` it with the IPageObject protocol and make the Dog record now something that can be displayed on a webpage
Sounds like type-classes from haskell/scala? Or is that a different thing?
Similar simplicity but in rust: https://github.com/fdietze/alors