Post
Previously, I set a date for the #iocaine 3.0 release, October 23rd, that's about 1.5 weeks. I may have to push it back a little again, so I can write the necessary documentation.
Already started on it, but a lot has to be written still, and even more reviewed - and this endeavour includes a redesign of the iocaine homepage, so that I can host docs both for the stable and the in-development branch too.
iocaine itself has been near release-ready for a while now, there's one issue I need to look into, but that's very possibly a Roto issue (or a me holding roto wrong issue), and isn't release critical, as it's hard to trigger, and has workarounds.
Nam-Shub of Enki is in a reasonable place too.
It is documentation that's lacking, and I do not want to release without good docs. The 2.x release was done with far better docs than 1.x, I'll do the same for 3.x: release it with far better docs than 2.x.
A lot of effort went into making iocaine 3.x easier to get started with, the documentation needs to show how.
One of the mistakes I made post-2.x is that I didn't have - and still don't have - a way to publish documentation for the development branch. That makes me skip writing those docs during development, and writing them later is always going to be harder. I will not make the same mistake again. When I release 3.0, I will have a way to publish docs for 3.1 (or 4.0, or whatever the version ends up as) too, as soon as I start working on it.
@algernon@come-from.mad-scientist.club im excited for the full release of 3.0! i appreciate you taking time you need to work on good documentation. it was a major hassle to get the current main branch of iocaine and NSOE running on nixos, mainly because of the giant docs-shaped hole in the middle of it
though i have to admit that the way NSOE is structured, with the source code kinda being the documentation (i've never seen this before and i love it) is really cool and helped me a ton. the fact that i could figure it all out without a guide despite not knowing roto means you're clearly doing something right here 😁
i hope this will get more folk to adopt iocaine for their own websites
@algernon I'd love to fix this quickly and release 0.8.1 with this and the public error type. Do you have a reproducer?
Hrm, I suppose ammit should be updated to iocaine 3.0 too. Or archived. Not sure if anyone ever used it, or wanted to use it.
I don't, and won't, and maintaining it for 0 users is pointless. So I think I'll archive it - if anyone wants an Anubis -> iocaine transpiler, my DMs and email are open. I'll unarchive & update it if and when there's a demand for it.
Uhh-ohh. Looks like my static builds of iocaine broke at some point...
thread 'main' panicked at /build/cargo-vendor-dir/cranelift-jit-0.120.2/src/backend.rs:249:40:
can't resolve libcall memcpy
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fish: Job 1, './result/bin/iocaine' terminated by signal SIGABRT (Abort)
This does not bode well.
A space for Bonfire maintainers and contributors to communicate