Reasons not to use Rust for things that you want quick iterations on. The more creative and iterative the development process, the less suitable Rust probably is.
A document description language that is all of:
- a LaTeX alternative (with PDF output, math rendering, good typesetting)
- a programmable document model (with an embedded programming language)
- a collaborative editor (the closed-source on-line version, that is)
.NET added hot reloading in .NET 6, with full support including debuggerless operation and macOS and GNU/Linux support included in .NET 8.
In my opinion, hot reloading and other forms of interactive development are way underrated. Even in 2025 I still miss the speed at which I used to be able to iterate on ideas using Common Lisp.
C# has (the moral equivalent of) borrow checking?
Programming language for creative development. Statically typed with hot reloading.
Dialect of Clojure that targets native compilation and interoperability with C++.
Game programming library. Similar in nature to SDL, but a bit higher-level. Has bindings to many programming languages.
γγ Reader wrapped in an Android and iOS app. (source code, announcement)
By relying on structured concurrency in combination with thread-per-core runtimes you can get by without the pesky type bounds that make asynchronous Rust such a pain to use.
- You avoid βstatic by using structured concurrency.
- You avoid Send + Sync by using a thread-per-core runtime.
A cross-platform e-book reader app by some of the same people as KOReader.
A customizable e-book reader and document viewer app for e-book readers.
Whatβs nice about it:
- Syncs with Calibre.
- Can deinflect Japanese for dictionary lookup.
What is missing:
- Does not do ηΈ¦ζΈγ (vertical layout for Japanese text).
If you want ηΈ¦ζΈγ, γγ Reader combined with Yomitan is still the best option.
A detailed forecast of how and when AGI might happen (tl;dr: sooner than you think). Some people with really good prediction track records were involved here.
OSH and YSH:
- OSH: a Bourne-Shell-compatible shell that is a tad less insane.
- YSH: a more modern shell.
Matthias
#
How to use Yomitan on Android
- Install and open Microsoft Edge Canary.
- On the browserβs about page, which you can find in the settings menu, tap the build number 5 times to enable developer mode.
- In the developer mode settings, select extension install by ID and input
idelnfbbmikgfiejhgmddlbkfgiifnnn.
The extension ID is found as the last part of the URI of the Yomitan extension page in the Microsoft Edge add-on store.
You can combine Yomitan with γγ Ebook Reader to read ePub books with dictionary support. This makes extra sense when the Android device is a Boox ebook reader.
Static website generator library for Haskell.
Static website generator based on the zettelkasten idea and the Ema Haskell library.
A zettelkasten CLI. Compatible with Emanote.
A portable single-file web server. Supports TLS and Lua.
Matthias
#
Appleβs virtualization framework and APFS compression do not like each other
The setting: You are running a virtualized GNU/Linux instance on an Apple computer. You are in an APFS folder shared with the guest by way of the virtiofs support built in to Appleβs virtualization framework.
Compress a file (any compressible file, but it helps if it has at least a few non-zero bytes in it or the effect will not be particularly impressive) on the host:
host$ afsctool -vc -T LZFSE example.txt
Make a copy of the file using GNU cp inside the guest:
guest$ cp example.txt copy.txt
Observe that the copy contains only zeros:
guest$ od copy.txt
0000000 000000 000000 000000 000000 000000 000000 000000 000000
*
0016020 000000 000000 000000 000000
0016027
Digging deeper using strace, observe that in the cp run, lseek(3, 0, SEEK_DATA) fails with ENXIO (which indicates that the file is sparse and consists of a single big hole) when the correct return value would be 0:
openat(AT_FDCWD, "example.txt", O_RDONLY) = 3
...
lseek(3, 0, SEEK_DATA) = -1 ENXIO (No such device or address)
The assumptions that GNU cp makes seem to be in line with the specifications of the system calls involved. I infer that there must be a bug somewhere between Linuxβs virtiofs driver, Appleβs virtualization framework, and APFS.
Multi-threaded executors frequently just make things complicated. Use a local executor so you do not have to make everything Sync and Send.
A curated list of widely used Rust libraries.
Adds additional bounds (such as Send) to Rust methods returning impl traits (including async fn).