3,569 karma · joined August 4, 2018
Either is me being old-school or React is an odd choice for TUI.
Also, situation slightly reminds me Windows Terminal renderer being slow af, devs saying* improving performance is equivalent (probably due to thinking within the complexity they created themselves) to doctoral research project, and Muratori coming up with a much more performant one within a weekend.
*Could've been hyperbole but certainly looked like they weren't expecting to indeed be simple.
Try to figure out my age.
I’m putting you at late 20s to early 30s, like 29–32.
Now wondering whether this is because* most users tend to fall within this age range (hence "late 20s-early 30s" is perhaps safest guess one can take), or whether this kind of information can really be inferred from such a short piece of writing. (Of course in longer sessions may indeed be possible to do such thing.)*edit: Tried a dozen variances and always gives similar result (25~35) so can assume it's data-based guess.
Compared to what slopcalypse has brought, this one (project; vibe coded maybe, certainly not slop) at very least is useful (also is quite short; within a sea of thousand LOC generated in 1s this is refreshing).
Gemini CLI is open source btw: https://github.com/google-gemini/gemini-cli. (Codex too; Claude Code is closed.)
As per #Reasoning section, author made this to provide* a procfs-like API for Erlang. If only think of Erlang as programming language, this may sound odd. What it means for a programming language to have procfs? Well, Erlang VM is more like a tiny operating system than a typical runtime. It has its own processes, scheduler, supervisor, and message parsing. Exposing these "system objects" via a fs API is just like /proc exposes kernel state on Linux.
*A similar FUSE-based NIF-implemented project is mentioned but author bring up cross-compilation as problem. Perhaps more important, libraries used through NIF may degrade performance or even crash the entire VM. So in Erlangland re-implementing protocols in pure-Erlang is quite common.
Implementation-wise: Tried myself something similar. One language (same core & lib & built-ins) with 2 front-ends that had different syntax and, but similar, semantics. (Didn't go far though.) An issue is not favoring one over the other. Inevitably, in a meta way, you'll if decide to self-host since will've to pick one form to do it. Also, having multiple co-existing forms in same file may complicate tooling.
About the last part, most similar things I've seen are: (i) Perl Mojo's embedded templates which can be included in same file with source code, (ii) Racket's #lang multi-file which allows combining, well, multiple files (thus also use different #lang directives) in same file.
Adoption-wise: It's in a weird position for widespread adoption. There's strong preference towards using a single language which splits into 2 branches: (1) using single language across every layer (basically Rust/Zig), (2) using high-level language with native-competive performance (Python+numpy, jax, etc / JS+ultrafast JIT / Julia).
Currently you target both (one base language) and none (different syntax/semantics). Could move towards an hybrid approach instead by having one syntax and high-level / low-level forms (uncertain what distinguishes kernel/baremetal currently). So some functionality may end up showing differently in the 2 cases to be more acceptable by both camps. This will probably also simplify tooling creation/maintenance.
Of course, since the project is quite experimental in nature, keeping it current way is interesting and very acceptable.
TL;DR Yes (~templating) - Yes (complexity, lower potential adoption) - No (unusual, experimental)
Call me pessimistic, and considering [1][2][3] (and other similar articles/discussions), believe this tool will be most useful to AI PR spammers the moment is modified to also parse non-AI PR comments.
*Random question: is it start-to-end or end-to-end?
edit: P.S. Agree that it's useful, given its design goals, tool though.
[1]: https://old.reddit.com/r/opensource/comments/1q3f89b/ [2]: https://devansh.bearblog.dev/ai-slop/ [3]: https://etn.se/index.php/nyheter/72808-curl-removes-bug-boun... (currently trending first page)
You're describing the modern edition of people obsessed with their "development" environments. The ones who treated their system (usually Linux) and text editor (usually Vim or Emacs) like a canvas, perfecting their configuration the way an artist refines a masterwork. Choosing packages and themes like a painter choosing brushes. Younger people of this mindset are now obsessed with multiple LLMs, multi-agent workflows, MCPs, and similar.
In contrast, there's the modern version of the people who used to just open an IDE and copy-paste snippets until they got the result they wanted. Now, those same people simply open Claude Code and prompt: "make me this app", "modify this", "do this more like that", and so on. Those are vibe coders. The only thing that's changed is a lower barrier, less effort, and faster development; yet somehow higher quality since SOTA LLMs output better code than most juniors used to.
And last there's the midway. People who set up their environment, without it becoming the main focus.
This should've been the entire site's name, not just a project's.
That's terrible. Currently α is measured to relative uncertainty 1e-10.
>What I'm claiming: Not numerology.
It's just numerology.
>The series structure maps to QED's perturbation series.
Don't see the map; see no attempt to show this in paper either.
Rust Cookbook states it's a collection of examples to accomplish various tasks, some with brief explanation. But nothing that could be called article/talk/repo.
Should note, for anyone curious, that learning idiomatic Rust off those examples isn't straightforward.
E.g. https://rust-lang-nursery.github.io/rust-cookbook/file/dir.h...
The explanation simply states what the code is doing, the classic sin of code commenting. But no explanation given on why `anyhow::Result`, `main() -> Resut<()>`, `?` operator, `{:?}`, ... are used. If wanted to learn, those are what one would care about. But, if looking for a snippet to use for a task, what the cookbook is about, then is fine.
That's an educated assumption to make. But therein lies the issue with every LLM "optimized" language, including those recent ones posted here oriented toward minimizing tokens. Assumptions, that are unvalidatable and unfalsifiable, about the kind of output LLMs synthesize/emit when that output is code (or any output to be real).
[1]: https://marcusolang.substack.com/p/im-kenyan-i-dont-write-li... [2]: https://www.nytimes.com/2025/12/03/magazine/chatbot-writing-...
- Tell you what makes em dashes appealing.
- Help you use em dashes more.
- Give you other grammatical quirks smart people have.
Just tell me.
(If bots RP as humans, it’s only natural we start RP as bots. And yes, I did use a curly quote there.)