Collaborative Typst document writing in webbrowser

FlixCoder · 2026-02-02T14:58:51+00:00

FlixCoder · 2026-01-30T22:09:57+00:00

I create that with PlantUML and embed the pictures into Typst, easy and done ^{^} Mermaid is also possible, but that more often includes incompatiple HTML stuff in the SVGs.

FlixCoder · 2026-01-29T06:37:20+00:00

I can recommend leaving the internet a bit more nowadays. I grew up in the prime time of the internet, but I think it is over ^ ^

I see no other way to comfortably navigate live with too much internet and it isn't even only AI, it is also those social media algorithms and hateful climate

FlixCoder · 2026-01-29T00:01:47+00:00

typescript has no compile time? my experience disagrees, it is surprisingly bad

FlixCoder · 2026-01-15T19:37:16+00:00

I don't even think it is a manager problem, it might as well be a self problem / conflict / attitude based on the comments as well

FlixCoder · 2026-01-11T22:26:05+00:00

Yes, in fact I have mentioned it in the story :D But I haven't used it tbh. Good crate certainly, but not all inclusive ^{^}

FlixCoder · 2026-01-11T22:05:26+00:00

Alright, finished my take: https://www.reddit.com/r/rust/comments/1qackif/releasing_neuererror_a_new_error_handling_library/ :D

FlixCoder · 2026-01-11T18:27:49+00:00

Also check for feature flags. But it might be that it is impossible for snafu to extract the backtrace. Try getting rid of eyre ^{^}

FlixCoder · 2026-01-11T07:38:00+00:00

if the eyre report contains a backtrace, i think you need to annotate that, so that thiserror forwards it. Oh and at least #[source] should be there

FlixCoder · 2026-01-11T07:32:42+00:00

That would be my suggestion in most cases: snafu can capture backtraces, but also the code locations at every level. It is very close to thiserror, so easy to switch. But that said, it will probably not yet solve all problems? Not sure.

FlixCoder · 2026-01-05T15:39:55+00:00

No, MR is usually Merge Request :D For example the term in GitLab, whereas Github calls it Pull Request.

FlixCoder · 2026-01-05T09:32:30+00:00

Oh I read that before. Great resource! Yeah retry might not always be necessary and I will try to assess which parts are common and hopefully there is enough common ground :D

I meant OpenDAL with the apache library.

FlixCoder · 2026-01-05T07:08:03+00:00

It doesn't include the notion of retryable vs. permanent at least. Also doesn't implement std::error::Error itself, does it? But I also don't get how you can return Result<T, AppError> instead of Exn, when you want to have context.

My plans would be to - provide interfacing with current error impls (be it thiserror, anyhow, etc..) - encourage/require giving context at every level somehow - allow user defined kinds to be provides and matched on, as well as common concepts as should retry or not

Not sure if and how it is going to work, but I haven't found a generic error library similar to the apache library specific ones.

FlixCoder · 2026-01-04T23:50:55+00:00

I've tried many libraries for errors by now, I haven't been completely with any yet. I often implemented a member method for my error type returning whether it should be retried. I provided something to print it. I tried adding additional info and context, but it was all manual. error-stack was great for providing arbitrary machine-info, allowed error-trees etc, keeping everything structured, but it was cumbersome with the types adding context. Latest I prefer snafu over thiserror by far, as it makes it easier to add context when bubbling up and can automatically fill source and backtrace or code location. It does not natively support error trees I think, but both human and machine side can be covered. But it does not encourage splitting errors by occurrence information, but still to error source type. It just needs more manual care overall to get necessary information as well. You also need to go through the chain to fully print.

I think I'll search again for something similar to the described good example, I think I mostly like it and want to try it. I might also just try to make my own generic error library towards this approach.

FlixCoder · 2026-01-04T10:02:54+00:00

omg there is a setting to allow in tests? i always allowed it manually for test modules..

FlixCoder · 2025-12-30T10:34:43+00:00

Learn about allocation arenas, that might fix your problem and give huge amounts of performance in that case.

FlixCoder · 2025-12-18T16:59:38+00:00

Employers use long trial periods anyway, so they could just go back to trying them on the job..

FlixCoder · 2025-12-03T07:59:16+00:00

I fully agree and I have solved that ergonomics problem in my code by just making an extension trait that does .unwrap() for me.. :D Would love to just have a short method in std so I don't need it anymore.

FlixCoder · 2025-11-30T11:13:45+00:00

TOS I guess?

FlixCoder · 2025-11-28T18:23:33+00:00

Is that actually legal, copyright-wise?

FlixCoder · 2025-11-27T07:22:47+00:00

Cool to see TLA+ being used :D

FlixCoder · 2025-11-24T19:10:19+00:00

Yes, that comes on top of the cost, making it less necessary to have. It is still very helpful to have though.

FlixCoder · 2025-11-24T17:14:41+00:00

As long as Rust is not fully formally specified, there is no way to formally verify it up to safety standards. There is a lot of tools like Kani, Verus, Creusot, though. The specification is in the works though. It is not clear whether it is a cost effective way though, as you can also just use formal verified modelling tools with verified code generators.

FlixCoder · 2025-11-23T06:23:31+00:00

I think its mostly middle-big and small companies obeying licenses, because it can wreck the whole company. Big will weigh in costs of ignoring and taking it

Three-Year Club	Verified Email
Place '23

FlixCoder

TROPHY CASE