What came to mind while reading through it is that all of the information and details appear to be technically correct, but they don't really communicate much about the project to someone who knows nothing about it.
It's weird. I feel like this could maybe be interesting, but also... huh?
I feel like the idea is to produce a small, self-contained compiler with simple semantics that generates simple executables with a simple runtime model, and a basic supervisor model for scheduling tasks. Okay, that's cool.
But "vibe coded mass of JavaScript running in node.js" doesn't really mesh well with that vision, at the least to me.
Also, as whatever LLM that generated that table says, the code it generates isn't "seriously optimized". I don't buy the idea that compiler optimization is something you can bolt on to a project like this later, after you've written the IR and all the platform porting code and whatever.
It's so hard to tell what the real goal is from the page, that I'm suspecting maybe the author doesn't really know either.
In truth, I'm probably not "qualified" to write a programming language, but I'm doingg so anyway. I use LLMs (20 - 40/month plans) to implement, so do use 100% of my effort for this on design, model, and goals. JS is most familiar to me and lets me work instantly.
I know precisely what I want this to be, but I'm also open to its uses blossoming unexpectedly. I'm building because I want this thing to exist, and bc it also v fun. If it offended your sensibilities or you're look for a trad built, ultra-optimized C++-like compiler/chain on day one, you do miss the point a bit, and it prolly ain't for you, bud. lol
That said, two things: I use LLMs for coding a lot, and I'm not turning my nose at the use of LLMs here, though I do think the user-facing pages/documentation could use more direct, human-written language.
The other is I do think this is probably something I'd be interested in. I "maintain" a few modified compiler stacks for worth, using Nim to:
- generate libc-less, pure syscall binaries with minimal ELF/PE headers
- generate Cosmopolitan-libc binaries for all platforms
- cross-compile via Zig/LLVM for those platforms
It seems like there is some cool work here, I just think it could be expressed a bit more cleanly and directly on the front-page/docs.
op describe {name, role} (
print "user: " + name + " (" + role + ")";
)
for no-libc because i want tiny self-contained bins, no legacy bugs (legacy human slop ;)), and just no C. Not because I'm against C, I just want to start fresh. Fun + pure :)
That Nim setup actually sounds incredibly cool. Cosmopolitan libc is legendary -- what a proejct!, and doing pure syscall libc-less binaries with Nim is exactly the kind of stuffI love -- cool. It's a fun space to build in.
We kind of on same page about docs, I will give them a proper redux - but honestly, writing about my work has is never something I've really developed much. You don't have any "great examples" of great docs/landing page writing from relevant projects you could point me to look at, do you? I think I could benefit from reading some clarity there, tbh.
And if you do end up poking around the freelang internals at some point, lmk what you think!