Community
Chat Logs
Sunday, May 3, 2026
- * phaleth joined #primate
- * blue_ joined #primate
- blue_hi phaleth
- phalethhi blue
- blue_so I had a discussion with my brother yesterday about how clankerdom stifles innovation
- phaleththere will be less and less people learning all sorts of skills, not just software development
- blue_like, why do people keep using next despite its terrible record with rsc (cve of 10.0!) and the general fact that it's a terrible piece of software
- blue_because the clanker recommends it
- blue_basically at this point you're better off using vanilla js and html than next
- phalethand php and raw sql
- phalethall in a single php script
- phaleth:)
- blue_yes, perfect
- phalethin any case nextjs got picked up by many because it had exquisite docs
- blue_anything better than this clanker infested nonsense
- phalethone does really have to think like a junior dev and describe things that way
- blue_look at this nonsense
- blue_phaleth: https://dpaste.com/BZWAEHADJ#wrap
- blue_this is what a vanilla next installation produces
- blue_you can't argue that's sane
- blue_phaleth: https://dpaste.com/GP9BAKEET#wrap
- blue_that's what a comparable primate (+react) installation produces
- phalethlooks like they use tailwind
- blue_and the bulk of those bytes are just nonsense headers that my dumb browser sends
- blue_that's why primate takes <0s to load on comp, whilst next is around 2-3s
- phalethnowadays next is obviously able to hide a lot of important details behind their easy to use framework
- blue_if someone has any shred of understanding of security, he would never let rsc run in any of his apps
- blue_the complexity of that is terrible
- blue_and for no gain
- phaleththey probably just state next is blazing fast due to having all those rendering strategies and that it
- blue_I don't even understand this chunking nonsense that next does
- blue_the esbuild approach is easier: you chunk only on dynamic imports
- blue_it's kinda funny it's 2026 and people still use subpar software for everything
- blue_anyway, I'm gonna upgrade the RP repo to primate 0.38
- blue_it's still on primate .36 and I wanna continue dev
- phalethit's 2026 and people just want an exe
- blue_phaleth, did you see this
- blue_https://github.com/primate-run/primate/commit/485cba0b86144c60cff81802353156310ae44158
- nevetmove to tsgo · primate-run/primate@485cba0
- phalethdrag and drop it into the browser and it deploys
- blue_lol
- phalethyeah, I did
- phalethI assume that's also not breaking the primate website deployment from master branch
- blue_you assume correct
- blue_in fact, you overassume. apps/website does not use typescript directly
- blue_none of the apps does
- blue_typescript in the primate monorepo is used for two things: compiling packages, which is increasingly rare because I'm using live TS during, and type-checking in the editor
- blue_when you build apps/website, what happens is that esbuild pipes all of the TS into a single JS file
- phalethok, can you take a look at the PRs then?
- blue_I could, but I wanted to ask you. you've fixed this woff thing a few times, do I keep changing things that it keeps regressing?
- blue_I anyway wanted to find some solution for woff because I keep needing custom code for it and it's annoying me
- blue_https://github.com/primate-run/primate/blob/master/apps/website/config/Website.ts#L18-L28
- blue_I have 100% the same piece of code on repopack's website repo
- blue_I was thinking of maybe adding {loaders": Record} to the config
- blue_so you'd just do {loaders: {woff2: "file"}}
- blue_but that feels like circumventing the module API a bit
- blue_maybe the best way is providing a primate helper
- blue_`import loader from "primate/loader"; ... export default config({ modules: [loader("woff2", "file")] })
- blue_translates interally to a Module, but without all the boilerplate
- blue_but anyway your first PR only makes sense if woff2 is used
- blue_and a part of me feels back about hardcoding woff2 support into the code
- blue_feels bad*
- blue_what does the patch do, create a preload script tag for woff2?
- blue_do we need this? esbuild inlines woff2 with the module I just showed
- phalethyou can move that from the core if you want to, that's totally up to you
- phalethI'm just fixing it again, but it's not really a regression
- phaleththis time the problem is in a different place
- blue_it just adds a preload script tag, or what does it do?
- phalethyeah, the code for adding that preload tag is fine
- phaleththe bug is not there
- phalethI mean the preload tag creation was already there :)
- blue_oh, so what is the bug
- phaleththe bug is that woff2 files are ignored by that magical thing dynamically processing assets
- phalethI also think that the build system should take care of pre-rendering the tags, but that'd mean lot of rework
- blue_the script tags?
- phaleththink header at least
- blue_it does create script tags
- phalethat build time?
- blue_oh, you want at build to create html files with the script tags already baked in?
- phalethyeah, but don't worry about that now
- phalethit's fine as it, cause it just works
- blue_lol, I just did `npx primate build`, and build/server.js isn't minified
- blue_when did that get lost
- phalethheh