94
Quarkdown
(quarkdown.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Jun 2025
94 points (98.0% liked)
Open Source
37987 readers
119 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
Looking through some of the docs I'm afraid I won't be able to move off of Typst to this either. Typst has a long standing bug that I would have liked to avoid (lists that are too long will overflow memory and the maintainers seem to not want to temporarily dump to disk) but if even rust has an issue with those 100k+ row lists, I'm not sure kotlin will handle it better.
Lists with 100k items? Impressive. I can see how with a document like that it will run out of memory. Is it a stack overflow? You could try increasing the stack size in that case.