Community
Chat Logs
Tuesday, May 19, 2026
- * jreicher joined #primate
- * blue joined #primate
- * nevet joined #primate
- * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is mirrored to the Primate discord, channel #irc
- * jreicher joined #primate
- * phaleth joined #primate
- bluehi phaleth
- blueI just pushed out a few things, amongst which: reverting markdown db, adding entrypoints and converting the website to use that
- blueyour pr might be obsolete by that
- blueyou can redeploy the website, and the memory footprint should go back to normal
- bluethis was a bad pivot on my part
- blueit's two different use cases: a docs website benefits immensely from bundling in the mds. and will later use target=static. a dynamic website can just save the .mds in a db, render them on request and/or cache the rendered out if necessary
- blueI'm standing down from the markdown db, at least for now
- phalethhi blue
- phalethoh, right, there are conflicts
- phalethwow, everything is gone
- blueI'm not sure your pr is needed
- blueya
- blueyou don't need to copy snippets/docs anymore, so you can revert the Containerfile to how it was before
- phalethoh, you've added entrypoints, that's why
- blueyes
- phaleththat's cool, lets try that
- blueworks locally
- phalethgetting these errors with npm run serve
- phaleth[ERROR] Markdown document backend not found
- phaleth[ERROR] Markdown document index not found
- phalethpages are not showing
- phalethyeah, so I should rebuild core and so on
- bluethat's old stuff
- bluethat's markdown db
- bluenpm run build:packages
- phalethnice, the site works quite well
- blueyes
- blueand memory hogging should be gone
- bluemarkdown db was a majorbutt time waste
- bluewell, at least perf metrics caught it
- phalethyeah, I mean that's fine, you have to experiment
- blueI don't mind experimenting, but the empirical data was clear. a 3x memory increase isn't acceptable, and also I don't like shifting stuff from build to serve
- bluebuild should be the heavylifter, serve should be optimising for memory consumption
- blue158MB was *already* much for serving what is essentially a static website
- blueunacceptable, really. should be in the lower 10s
- blueI really need to work on dog/flog because all modern js runtimes are memory hogs to no end
- phalethat least now you know a little more about how to get closer to having most of everything done at buildtime
- phalethalso me, I know that primate is very flexible :D
- bluewell, I'm glad this detour birthed entrypoints, because we were missing flexibility there
- blueso, good job there
- bluestatic is now a dumbed-down dir
- blueso we got less magic
- blueat some point, we'll arrive in reality :P
- phalethyeah, just wondering if there is anything else where primate website really needs a dynamic server
- bluenot really at this stage. it's essentially a static website, we just need target=static to be spitting out html pages
- blueentrypoints might getting extended syntax with { in: "file.ts", inline: true }, just to make sure that colorscheme stuff is processed as quickly as possible, those bytes are't a huge price to pay per html
- phalethinline into html? prolly a good idea, yeah
- phalethalso if you could add defer attribute that'd be great, cause the other app js bundle might need that
- blueso { in: p.string, defer: p.boolean.default(false), inline: p.boolean.default(false) }, ya?
- phalethI think there is one more attribute to the script tag that could be useful
- phalethlet me dig
- phalethasync https://javascript.info/script-async-defer#async
- phalethmaybe you could make those two referable by script.async and script.defer
- bluemhm
- phalethso there is also a smaller chunk of css with colors, that's cool
- phaleththat means there should really be no flash even when the website opens on a toaster
- blueya