- I'm using https://einaregilsson.com/redirector/ with a couple custom rules. Unfortunately, it appears the author has died (https://github.com/einaregilsson/Redirector#tribute), and the project is in a maintenance state. But it does exactly everything I need, and I disabled the auto-update, so I should be safe from any takeover attacks. Thank you, Einar.
Love that there's an upper limit on compilation time. No matter how large your project gets, it will never take more than five minutes to compile (incrementally).Compilation Performance Small files (<100 lines): <1 second Medium projects (1K-10K lines): 5-30 seconds Large projects (100K+ lines): 30-300 seconds with incremental compilation- >> memory safety is simply table stakes
> Why?
Because it's a stepping stone to other kinds of safety. Memory safety isn't the be-all and end-all, but it gets us to where we can focus other important things.
And turns out in this particular case we don't even have to pay much for it in terms of performance.
> The real underlying comparison statement here is far more subjective. It's along the lines of: "I find it easier to write solid code in rust than in zig".
Agreed! But also how about "We can get pretty close to memory safety with the tools we provide! Mostly at runtime! If you opt-in!" ~~ signed, people (Zig compiler itself, Bun, Ghostty, etc) who ship binaries built with -Doptimize=ReleaseFast
- > Between mold and this, the linker space appears to be going through a renaissance.
No kidding. There are also https://github.com/davidlattimore/wild and https://github.com/kubkon/bold.
- Heheh, it was mostly a reference to my [and mostly others'!] experiments with encoding human languages in a programming language. There are some pretty neat ideas there to explore, like the difference between Subject-Object-Verb (SOV) and Object-Subject-Verb. Or postfix languages (e.g. Forth) mapping to some human languages.
In this particular example, having a subsequent part of an expression rely on prior parts would usually be accomplished at runtime in most languages. But some (like Idris) might allow you to encode the rules in the type system. Thus the rabbit hole.
- > making it safe (within reason) to expose the regex engine to untrusted input
Or even trusted input! https://blog.cloudflare.com/details-of-the-cloudflare-outage...
- Or these, which have their own Wikipedia page: https://en.wikipedia.org/wiki/UTM_parameters
- A small note here: even though the public version of jj only supports the Git backend right now (I believe there's also support for whatever Google's using internally?), it's designed to be backend-agnostic. So potentially, in the future it could grow its own native backend that could solve some of Git's pain points -- support for huge repositories, native large file storage, etc.
- There's https://github.com/keanemind/jjk for VSCode users. There are also tickets to add jj support in Helix and Zed, so that's promising.
- > Haskell
https://github.com/Frege/frege
https://github.com/typelead/eta
Of the others you mentioned, I bet there's a couple JVM Prologs out there, but haven't encountered any myself.
Edit: the two configuration.nixen has since been merged in a single dotfiles repo, which also covers my Macbook via https://nix-darwin.org.