Konrad Hinsen
@khinsen.net
Researcher at CNRS (France). Computational science, in particular computational biophysics. Metascience, in particular the evolution of science in the digital era.
More active in the Fediverse: https://scholar.social/@khinsen
More active in the Fediverse: https://scholar.social/@khinsen
However, for the blog, I'll keep the static site as well. It's archivable and usable without JavaScript. Plus the posts get DOIs.
We have a long way to go before we can put together all the desirable features for scientific publishing!
We have a long way to go before we can put together all the desirable features for scientific publishing!
November 13, 2025 at 8:50 AM
However, for the blog, I'll keep the static site as well. It's archivable and usable without JavaScript. Plus the posts get DOIs.
We have a long way to go before we can put together all the desirable features for scientific publishing!
We have a long way to go before we can put together all the desirable features for scientific publishing!
Turning my blog into a HyperDoc is one of my projects!
As for network/server dependency, I am betting on having Common Lisp on WASM in the near future, and then I can run everything in the browser, while retaining the server option for heavier computations or larger datasets.
As for network/server dependency, I am betting on having Common Lisp on WASM in the near future, and then I can run everything in the browser, while retaining the server option for heavier computations or larger datasets.
November 13, 2025 at 8:45 AM
Turning my blog into a HyperDoc is one of my projects!
As for network/server dependency, I am betting on having Common Lisp on WASM in the near future, and then I can run everything in the browser, while retaining the server option for heavier computations or larger datasets.
As for network/server dependency, I am betting on having Common Lisp on WASM in the near future, and then I can run everything in the browser, while retaining the server option for heavier computations or larger datasets.
Thanks for reporting! I had forgotten install the SBCL source package on the server. That should be fixed now.
November 12, 2025 at 5:01 PM
Thanks for reporting! I had forgotten install the SBCL source package on the server. That should be fixed now.
Reposted by Konrad Hinsen
AI hype letter remains open for more signatures tinyurl.com/Sign-Letter-...
CryptPad
tinyurl.com
November 10, 2025 at 9:48 AM
AI hype letter remains open for more signatures tinyurl.com/Sign-Letter-...
Revised preprint: "Establishing trust in automated reasoning"
osf.io/preprints/me...
Based on two very helpful reviews from @metaror.bsky.social:
metaror.org/kotahi/artic...
More references, better discussion of unfamiliar concepts (e.g. conviviality), and more.
🧪 #metasci #compsci
osf.io/preprints/me...
Based on two very helpful reviews from @metaror.bsky.social:
metaror.org/kotahi/artic...
More references, better discussion of unfamiliar concepts (e.g. conviviality), and more.
🧪 #metasci #compsci
OSF
osf.io
November 6, 2025 at 9:26 AM
Revised preprint: "Establishing trust in automated reasoning"
osf.io/preprints/me...
Based on two very helpful reviews from @metaror.bsky.social:
metaror.org/kotahi/artic...
More references, better discussion of unfamiliar concepts (e.g. conviviality), and more.
🧪 #metasci #compsci
osf.io/preprints/me...
Based on two very helpful reviews from @metaror.bsky.social:
metaror.org/kotahi/artic...
More references, better discussion of unfamiliar concepts (e.g. conviviality), and more.
🧪 #metasci #compsci
Then please formulate it that way! The current wording suggests that floats may not be handled correctly by some implementations.
Yes, the current float support is useful, e.g. for small observational datasets. But only if support is reliable.
Yes, the current float support is useful, e.g. for small observational datasets. But only if support is reliable.
October 23, 2025 at 6:47 AM
Then please formulate it that way! The current wording suggests that floats may not be handled correctly by some implementations.
Yes, the current float support is useful, e.g. for small observational datasets. But only if support is reliable.
Yes, the current float support is useful, e.g. for small observational datasets. But only if support is reliable.
That makes perfect sense, but it also means that DASL is no good for scientific data. So: no need to worry about BigNums.
However, I don't see the point of having some float support but recommending not to use it for the sake of interoperability. It sends a message of confusion.
However, I don't see the point of having some float support but recommending not to use it for the sake of interoperability. It sends a message of confusion.
October 22, 2025 at 6:03 PM
That makes perfect sense, but it also means that DASL is no good for scientific data. So: no need to worry about BigNums.
However, I don't see the point of having some float support but recommending not to use it for the sake of interoperability. It sends a message of confusion.
However, I don't see the point of having some float support but recommending not to use it for the sake of interoperability. It sends a message of confusion.
"most of the IEEE 754 "special" floating points (infinity, negative infinity, minimal NaN, and NaN with payloads) MUST NOT be encoded."
Doesn't sound good for storing data that fully exploits the IEEE formats (which isn't that common, but it happens).
Doesn't sound good for storing data that fully exploits the IEEE formats (which isn't that common, but it happens).
October 22, 2025 at 2:06 PM
"most of the IEEE 754 "special" floating points (infinity, negative infinity, minimal NaN, and NaN with payloads) MUST NOT be encoded."
Doesn't sound good for storing data that fully exploits the IEEE formats (which isn't that common, but it happens).
Doesn't sound good for storing data that fully exploits the IEEE formats (which isn't that common, but it happens).
"Completely avoiding floating-point numbers is RECOMMENDED to minimize interoperability and tooling issues."
Doesn't sound promising for long-term storage and interoperability.
Doesn't sound promising for long-term storage and interoperability.
October 22, 2025 at 2:06 PM
"Completely avoiding floating-point numbers is RECOMMENDED to minimize interoperability and tooling issues."
Doesn't sound promising for long-term storage and interoperability.
Doesn't sound promising for long-term storage and interoperability.
"Floating-point numbers MUST always be encoded as a 64-bit IEEE 754 binary floating-point, never as a "half-precision" (16-byte, major 7-25) or "single-precision (32-byte, major 7-26)" CBOR key."
Doesn't sound good for large datasets.
Doesn't sound good for large datasets.
October 22, 2025 at 2:06 PM
"Floating-point numbers MUST always be encoded as a 64-bit IEEE 754 binary floating-point, never as a "half-precision" (16-byte, major 7-25) or "single-precision (32-byte, major 7-26)" CBOR key."
Doesn't sound good for large datasets.
Doesn't sound good for large datasets.
When I first looked at DASL a few months ago, to see if it could possibly serve for scientific data storage, I closed my browser tab immediately when I read about the mostly-absent float support. BigNum seems a minor problem in comparison.
October 22, 2025 at 1:18 PM
When I first looked at DASL a few months ago, to see if it could possibly serve for scientific data storage, I closed my browser tab immediately when I read about the mostly-absent float support. BigNum seems a minor problem in comparison.
Yes, it's fuzzy. The only way to figure out how to review code appropriately is to start doing it!
October 9, 2025 at 12:10 PM
Yes, it's fuzzy. The only way to figure out how to review code appropriately is to start doing it!