Or does this only run in simulation anyway?

Comments URL: https://news.ycombinator.com/item?id=47322750

Points: 2

# Comments: 0

Even the documentation search is available:

```bash

/Applications/Wolfram.app/Contents/MacOS/WolframKernel -noprompt -run '

Needs["DocumentationSearch`"];

result = SearchDocumentation["query term"];

Print[Column[Take[result, UpTo[10]]]];

Exit[]'

```

Interesting project! I haven't really worked with Vulkan myself yet. Hence my question: how is the code compiled and then loaded into the cores?

Or is the entire code always compiled in the REPL and then uploaded, with only the existing data addresses being updated?

[1] https://crux-ecosystem.github.io/MOL/

https://www.weforum.org/stories/2026/01/davos-2026-special-a...

Is "human intelligence" and "intelligence" equal?

And: How to become conscious before being intelligent?

Or: If intelligence is a side-effect, how often this side-effect can't be observed?

Xor: What if an intelligent being denies being conscious?

An example: More than ten years ago a friend of mine was fascinated by the german edition of the book "A Cultural History of Physics" by Károly Simonyi. He scanned the book (600+ pages) and created a PDF (nearly) same layout.

Against my advice he used Adobe tools for it instead of creating an epub or something like DocBook.

The PDF looks great, but the text inside is impossible to use as training data for a small LLM. The lines from the two columns are mixed and a lot of spaces are randomly placed (makes it particularly difficult because mathematical formulas often appear in the text itself).

After many attempts (with RegEx and LLMs), I gave up and rendered each page and had a large LLM extract the text.

I agree it is a clever way. But it also shows exactly how hard it is to use XML and XSLT in a "proper way": Formal everything is fine to do it in this way (except the server is sending 'content-type: application/xml' for the /index.xsl, it should be 'application/xslt+xml').

Almost all implementations in XML and XSLT that I have seen in my career showed a nearly complete lack of understanding of how they were intended to be used and how they should work together. Starting with completely pointless key/value XMLs (I'm looking at you, Apple and Nokia), through call-template orgies (IBM), to ‘yet-another-element-open/-close’ implementations (almost every in-house application development in PHP, JAVA or .NET).

I started using XSLT before the first specification had been published. Initially, I only used it in the browser. Years later, I was able to use XSLT to create XSDs and modify them at runtime.

Comments URL: https://news.ycombinator.com/item?id=45836782

Points: 2

# Comments: 0

With Safari (standard and tech preview) the rendering looks strange (at least). The root sign does not have a strait line at the top (for many fonts) and at least the partial derivative is not rendered as italic (for all fonts).

But: Interestingly, the behavior of LLMs in different contexts is also the subject of scientific research.

[1] https://news.ycombinator.com/item?id=44689366

[2] https://news.ycombinator.com/item?id=44684373

Together with speed and const, this is from my point of view this is the only "case" for the return of fine-tuning here. And this can be managed by context management.

With growing context sizes, first RAG replaced fine-tuning and later even RAG was replaced by just a good-enough prompt preparation for more and more usage pattern.

Sure, speed and costs are important drivers. But like with FPGAs vs. CPUs or GPUs, the development costs and delivery time for high-performance solutions, eliminate the benefit most the time.