ByteCode.NewsSubmit
Use quotes for an exact word.

Subscribe

RSSPodcast
Log in

Chat Logs

  1. * skillbot quit (Remote host closed the connection)
  2. * skillnews quit (Remote host closed the connection)
  3. * skillbot joined #primate
  4. * skillnews joined #primate
  5. * phaleth joined #primate
  6. * phaleth is learning inkscape
  7. phalethflog docs are done exactly as I described yesterday, all template literals including css
  8. phalethI mean css in js is bad, but still
  9. * jreicher quit (Quit: In transit)
  10. * jreicher joined #primate
  11. bluehi phaleth
  12. bluehttps://repopack.com/project/flog/tasks/76
  13. blueI got it done yesterday, just forgot to merge
  14. phalethok, great
  15. bluephaleth: https://repopack.com/project/rcompat/tasks?status=open
  16. bluesee 57 and 58
  17. bluercompat is getting very close to be dependencyfree
  18. bluejust two more deps needed to eliminate
  19. phalethcool, noticed you removed crypto, crypto in JS is dumb
  20. blueit was just a weird package with one convenience function
  21. bluefs has FileRef#hash too
  22. blueand crypto would be shadowing globalThis.crypto
  23. blueso there's that
  24. blueanyway, it's gone
  25. phalethnice
  26. blueclanker did a full audit of rcompat, found a few things
  27. bluehence this
  28. bluehttps://repopack.com/project/primate/tasks/226
  29. bluephaleth: fyi: repopack *still* consumes 200 <= x <= 300 MiB of memory. Dog will specifically require to lower that number to <= 100 MiB. I don't know why it needs so much memory to be honest, is all of it JIT?
  30. phalethit's cause it's a VM
  31. blueyes I know it's a VM, but repopack isn't doing much
  32. phalethgolang runtime takes less memory only cause it's native
  33. bluethe repopack build/server.js is 36M
  34. phalethyeah, but you know there is event loop and that just in a sense heats up the VM
  35. bluewhich is already a lot and probably needs optimisaing. but 36M -> 300M is only 10x
  36. phalethall VMs are like that, node is actually doing very well for a VM
  37. bluealso bun was leaking like crazy
  38. phaleth36M means it should take ten times the memory, yeah
  39. phalethbun is a different story
  40. bluebun is dumpster fire
  41. bluephaleth: https://repopack.com/project/primate/tasks/228
  42. blueI'm gonna merge this, but the website itself uses the .svg as a favicon..
  43. bluejust fyi
  44. phalethnot really I think
  45. blueI added a <link tag to app.html
  46. phalethnope
  47. phalethno reason to do that anyway
  48. phalethunless you need multiple favicons on the site
  49. blueit didn't load the favicon.ico otherwise, for some reason
  50. blueit does it on primate.run, didn't do it for rcompat
  51. blueI couldn't be bothered to figure out, and implicit things are weird
  52. phalethyeah, it's fine as is
  53. phalethimplicit is fine
  54. bluewell if you can figure out why the browser didn't issue the request, then remove it again
  55. bluedreamreal said he saw no favicons on rcompat.repopack.app
  56. phalethit will load, don't worry :)
  57. phalethseems like flog is node specific https://upaste.de/raw/Trr
  58. bluelet me see
  59. phalethapps/website/static/favicon.ico | Bin 15406 -> 5430 bytes
  60. bluewow phaleth
  61. bluebtw, clanker said that this isn't about flog. the postinstall specifies "node install.js"
  62. blueflog just ran the script
  63. phalethyeah, I saw node in those package.json scripts I think
  64. phalethbut that's weird
  65. phalethwhy can't flog do whatever install.js is doing?
  66. bluewhat is this install.js?
  67. bluelike, where does it come from right now?
  68. blueI can't see it in primate website
  69. bluepackage.json
  70. phalethyou can search for `node --conditions=@primate/source`
  71. phaleththere are alot of those
  72. blueyes
  73. phalethactually three of those in apps/website
  74. blue "start": "node --conditions=@primate/source ../../packages/primate/src/bin.ts",
  75. blue "build": "node --conditions=@primate/source ../../packages/primate/src/bin.ts build",
  76. blue "serve": "node --conditions=@primate/source ../../packages/primate/src/bin.ts serve",
  77. blueyou mean these?
  78. blueyes, this is currently only necessary because package.json's "bin" field doesn't support conditions
  79. phalethok, that is where node is called
  80. phalethso node is hard dep
  81. bluewe're doing straight from source run, not compilation to JS
  82. blueno compilation*
  83. phalethok, well, the error message I posted said it happens on flog install
  84. phalethso those node calls are possibly not to blame
  85. blueyes, but where does that `node install.js` come from?
  86. phalethesbuild postinstall
  87. phalethhttps://github.com/evanw/esbuild/issues/4288
  88. nevetpost-install documentation · Issue #4288 · evanw/esbuild
  89. phalethtried to add --ignore-scripts to flog install, same error
  90. phalethtake a look at the pnpm-workspace.yml it had a directive to ignore esbuild scripts
  91. phalethand I think there was also some other package
  92. bluelooking it up
  93. blueyeah, oracledb was same
  94. bluephaleth: flog install --workspace apps/website --prod --ignore-scripts
  95. phalethtried exactly that
  96. blueare you running current flog?
  97. bluealso, can you paste the current containerfile that's failing?
  98. blueso I can have clanker test
  99. phalethis there newer flog released today?
  100. bluenot today
  101. bluewell there is, but it's just triggered by the website updates
  102. bluejust take the latest, build 65
  103. phalethok, I will just put that new version in and write task
  104. bluehttps://repopack.com/project/flog/jobs/1/runs/65/artifacts/flog-0.0.0-dev.07a7aad7035f-linux-amd64.tar.gz
  105. bluethe best is if you have a reproducible test case for me as a containerfile
  106. bluethen I can run it past the agent
  107. phalethyup
  108. bluephaleth: https://repopack.com/project/rcompat/tasks/57
  109. bluelook at this beauty, we're beating busboy :)
  110. phalethwith latest flog --ignore-scripts seems to work, but there is another error
  111. bluewhat error?
  112. phalethon build about node --conditions=@primate/source
  113. phalethI'll create a task
  114. dreamreal*sigh* two new pieces underway for BCN
  115. phalethI think it's a primate problem, not flogs
  116. dreamrealI need to get critical mass enough that other people write for it, because I'm burning myself alive
  117. dreamreal... although... okay, question time: blue, you read BCN because I force you to, phaleth, do you?
  118. bluephaleth: flog is pristine, so probably primate
  119. phalethdreamreal: sometimes, when I have time to lurk
  120. bluedreamreal: well, I read BCN for particularly two reasons. the first, I don't need to look around prefiltering what any idiot writes on his blog, I get the rough gold nuggets (usually) and 2) I get them in a REFINED form, so the rough gold nuggets are made pristine
  121. dreamrealWell, here's the question: am I setting the bar too high for people to be willing to write on BCN?
  122. dreamrealLike, I'm trying to write well but at full resolution
  123. dreamrealand if people go "I can't do dat, I rite gud on twitter insted" ...
  124. bluepartially, yes
  125. bluethe bar is pretty high because the takes are often complex and require thinking
  126. blueI do wish you had more plebs-oriented takes; like the current value destroying that andrew-zig has been hard at work on, for the last few months
  127. blueyou did have a take on zig's AI policy; but it was *way* too nice
  128. bluezig's AI policy, combined with lashing like crazy at bun, combined with the crazy and irrational move to codeberg... just shows you what a deranged dictator-for-life can cause for damage, in a project with otherwise high value
  129. dreamrealWell, BCN's editorial policy is to keep criticism unpersonal, and there's no way I'm digging in against anyone.
  130. blueI'm actually less annoyed with the AI policy, less annoyed with the childish lashing out at bun, than I am annoyed at how condescending and insufferable this guy was against *donors* on github
  131. dreamrealI'd like to have more plebe-oriented stuff as you call it, but I don't really think that way so it feels scripted
  132. dreamrealand since I don't use zig I don't have enough visibility into the specific issue, if you will
  133. bluewell, *you* draw the consequences, one of your most seen pieces was the bun rust rewrite, and it was closest to plebs content
  134. dreamrealI wouldn't mind publishing something written well
  135. blueI'm not gonna try and tell you how to run BCN. But if you want more exposure, and consequently perhaps more authors, you might have to stoop a bit
  136. blueyou don't *have* to make a zig 'hit' piece a personal attack
  137. dreamrealActually, I need to check the actual numbers: the bun rust rewrite piece maintains the most temperature but that doesn't actually correspond to "most hits"
  138. blueit is a personal problem caused by the project leader, but it is equally a project problem, by now
  139. dreamrealI don't mind, but I cannot stand ragebait, so I'm very sensitive to hosting it
  140. bluecodeberg regularly doesn't work properly; a ton of work was left unfinished on github in terms of issues, that the zig project did not bother migrating
  141. dreamrealRight now I'm binding pele into BCN, which will be a content piece as well, AND I'm working on a piece on irrelephants
  142. phalethcelld is the current hype, and the deno team being bought by cloudflare to work on celld
  143. blueand people are wary of using zig on high profile project, because if they pivot away, they'll get lashed out at
  144. dreamrealblue: See, I don't have those perspectives to even work with
  145. dreamrealwhich kinda sucks: I can't know everything and (surprise!) I don't
  146. phalethI mean clanker on celld, inlcuding the original author of node Ryan Dahl (think I spelled that right)
  147. * nevet joined #primate
  148. * blue!~blue@user/blue changed the topic to: https://primate.run | This channel is logged: https://bytecode.news/logs/irc/libera/primate
  149. dreamrealpele installed on server! Now working on one of the front ends to test it out :D
  150. bluebecause personally the lack of major 1 in zig is currently the biggest problem
  151. dreamrealblue: you mean major 0?
  152. blueno, I mean major 1
  153. dreamrealI mean, I agree with you, and you know why
  154. bluezig was not meant to be a 0ver
  155. blueand for a change, I don't think it should be. I'm in the 0ver-camp, but not for programming languages
  156. dreamrealSee, I know who should write this, and who should edit it
  157. dreamrealor I THINK I do
  158. blueI can tell you that such an article will generate A LOT of interaction
  159. dreamrealI'm sure it would
  160. bluebecause I know how people feel, and they feel strongly, either way
  161. * dreamreal actually does not, which is part of why he shouldn't write it
  162. blueit touches on all the current plebs seams. AI, semver, hosting platforms
  163. dreamrealTo me, zig is very much a storm in a teacup
  164. dreamrealI know it's actually NOT - that's the point of the irrelephant article I'm working on - but to me it is
  165. bluedreamreal: I'm just gonna tell you that if *I* wrote it, it'd probably be titled "The Zig project is going nowhere"
  166. dreamrealhell, write it that way! We'll edit it into shape if it needs it.
  167. dreamrealHideki Idoru has only published one thing so far!
  168. * dreamreal giggles
  169. bluetrue
  170. blueunfortunately I'm currently busy with Dog
  171. dreamrealI'd actually prefer a different pseudonym, or under your name, but eh, whatever. If we want to reuse it as an anonymous id, we can.
  172. dreamrealSit, dog!
  173. dreamrealLie down!
  174. dreamrealRoll over!
  175. dreamrealPlay dead!
  176. blueIt's edging on V8, believe it or not
  177. bluewhether it can beat it or not, remains open
  178. blueI'm skeptical, but Dog seems to be confident
  179. blueI'd be actually personally ok with getting lim(v8) rather than surpassing
  180. dreamrealdang it, now I want the zig thing too
  181. bluehaha
  182. bluethis is where we are currently at: "recent Dog timings varied roughly 59–76 µs/batch versus V8’s 3.3–4.0 µs/batch."
  183. blue17-18x roughly, on a non-representative benchmark
  184. bluewe started at 30x
  185. blueWe're still doing work for reference-bearing JIT, but it's not enabled yet
  186. * dreamreal is so jazzed by pele - BCN is getting mermaid graphs in posts, I think
  187. dreamreal(I say "I think" but it's actually looking like it's working on the server, but the UIs need to respect the directives)
  188. blueya, I recently added mermaid support to repopack
  189. dreamrealpele.run!
  190. dreamrealpele > mermaid so far, since it actually generates SVG differently
  191. blueusing the "mermaid" npm package, I believe. you should render it on the client, cheaper
  192. dreamreals/should/could/ but mermaid's expensive
  193. dreamrealthe problem is that we'd have to pass the mermaid block to the client
  194. dreamrealI AM rendering drafts on the client, though
  195. bluepele is great. let me replace the mermaid dep with pele in repopack
  196. bluePele 1.6.0 replaces Mermaid 12.1.0
  197. blueand its diagram dependency graph, including KaTeX, Chevrotain and lodash-es.
  198. blueso nice, dreamreal!
  199. dreamrealI'm impressed as all hell
  200. dreamrealGot a crackerjack post underway on it but want to have it deployed, so the post on pele uses pele :D
  201. blueand the zig post?
  202. bluehas it materialised yet?
  203. dreamrealHmm,I don't think I'm the one to materialize that one, it could be written here with !article (that's why that command exists, to allow people to discuss content that creates an article) but I don't think I should sole-source it
  204. dreamrealbut to answer you directly: no, I have two high-effort pieces underway, a third would be a lot for a calm peaceful sunday
  205. blueI can give clanker a few pointers, see what it comes up with
  206. bluebut I won't be able to read it aloud!
  207. dreamrealThat's fine, I'll narrate it
  208. dreamrealthe audio isn't literally narrated, the audio is a separate piece of content and should be considered as such
  209. bluefair
  210. dreamrealWhat I do for the audio is have the *rendered draft* in front of me, and it's mostly a mostly-faithful way of how *I read it*
  211. dreamrealso no footnotes unless they occur to me as I read the actual main content, etc
  212. dreamrealthe main thing about using !article is that if you use the AI features for it you get haiku as the model
  213. bluezig article is cooking, dreamreal
  214. dreamrealooo that's awesome
  215. phalethdiagrams will finally properly display in librewolf? https://repopack.com/project/repopack/tasks/701
  216. dreamrealI am SO jazzed about this pele thing
  217. dreamrealphaleth: so what did you see in the ui-primate OCI image?
  218. phalethnot yet, I will log into github, one sec
  219. dreamrealno hurry
  220. bluephaleth: maybe
  221. dreamrealI'm doing a general site refresh this morning thanks to pele but most OCI updates like that barely affect traffic
  222. phalethdreamreal: don't see any notification
  223. bluephaleth: https://repopack.com/project/rcompat/tasks/58
  224. bluebeating ws as well now
  225. dreamrealphaleth: you're on there as "phaleth" right?
  226. dreamrealsays it's got a pending invite :/
  227. * nevet joined #primate
  228. * blue!~blue@user/blue changed the topic to: https://primate.run | This channel is logged: https://bytecode.news/logs/irc/libera/primate
  229. phalethlooking at the Dockerfile and there are few changes I am gonna suggest in the PR, the one big mistake I see is to use npx to run the app, that results two node processes instead of one I think
  230. dreamreal(graalvm's native images do not do image libraries well)
  231. dreamrealphaleth: *nod* I used AI to build the app, I do not and did not expect it to be good at it, just sufficient
  232. phalethbut I will create a PR
  233. dreamreal*nod* and thank you VERY much
  234. phalethno problem
  235. bluedreamreal: discord, zig article
  236. dreamrealgot it, looking, will get to it ASAP but drowning right now
  237. blueget a LIFE VEST
  238. phalethanother big mistake is to use main as branch name :)
  239. blueYES
  240. bluefinally someone calling it out
  241. phaleththe sole reason why dog exists
  242. blueyes
  243. bluefinally someone who gets it
  244. dreamrealphaleth: I don't care, it's github default and I saw no reason to give a single crap about it :D
  245. dreamrealI don't care about main/master, use master and I'm fine, use main and I'm fine, no reason to get my knickers in a twist about it
  246. dreamrealAdding fonts and styles for primate, and getting the preview renderer in place
  247. dreamrealand doing a rare nextjs update so the fonts render in case any damn fool uses the nextjs front end :D
  248. dreamrealblue: https://primate.bytecode.news/posts/2026/10/test-post
  249. blueHOLY HECK THE ZIG POST IS GOING PLACES AND THE EDITOR IS BUSY FIDDLING WITH GRAPHS
  250. dreamrealblue: the editor has a queue and is human and stuff AND the author hasn't granted access to the zig post anyway
  251. blueI sent you a glink
  252. dreamrealyes, and I requested access because I didn't get granted access despite the link
  253. dreamrealokay, one of four done in the queue, now to work on #2
  254. blueDONE
  255. dreamrealthere's #4!
  256. bluelol
  257. dreamrealokay, how do you want to do this
  258. dreamrealdo you want to post it yourself, or do you want the same process as the prior one
  259. blueto what are those questions tending
  260. bluedo you want to draft it on BCN?
  261. blueotherwise I'd say, let's finish it first on gdocs, then decide
  262. dreamrealWell, I mean is it a hideki irodu-type "a user sent this in" post, or what
  263. dreamrealokay, I 'll file comments, some will be to me, some to you, okay?
  264. blueidk, I haven't decided yet
  265. dreamrealThat's fine, it just affects voice
  266. bluesure
  267. dreamrealif it's you or attributed to a pseudonym, some of the stronger statements get to stand
  268. blueI'm currently trying to make it sond more human, because it screams clanker, and it annoys me because I don't like reading clanker content either, feels so unreal
  269. dreamrealThe way to do that is for you to read each sentence and phrase it yourself, including flow, FTR
  270. dreamrealbut I get it
  271. blueyes
  272. dreamrealOkay, I'm goingto wait on the bun section until you're done editing
  273. bluek
  274. bluethx
  275. dreamrealLMK when, going to work on the pele post now
  276. bluek
  277. bluedreamreal: done
  278. dreamrealOkay, almost done with the pele edit, will switch when I get closer on this, won't be long
  279. phalethdreamreal: I found the current deployment is very insecure, there are all node_modules in the container at runtime with write permissions
  280. dreamrealphaleth: *nod* feel *very* free to fix
  281. dreamrealI make no claims to the primate ui's quality
  282. bluephaleth: did you see the native gains on `ws`?
  283. bluethis is amazing. Getting rid of a dep, and becoming faster
  284. phalethdreamreal: PR is already there
  285. phalethblue: I saw some 2x improvements in some table
  286. phalethwell, consider using websockets instead of SSE for repopack
  287. bluethis is amaze sauce
  288. dreamrealthanks for notifying me, GITHUB YOU PIECE OF SHIT
  289. dreamrealsorry
  290. * blue points at repopack
  291. blueactually, there's no way to subscribe to a project's tasks... yet.
  292. bluephaleth: we need a task for this
  293. dreamrealphaleth: deploying now
  294. dreamrealmuch appreciated
  295. dreamrealphaleth: ++
  296. nevetphaleth now has karma of 1.
  297. phalethblue: btw, should be tricky to make flog work against bcn's primate frontend, I tried nub but nub failed
  298. phalethyeah, I wonder what happened to the release candidates task in repopack, forgot the number
  299. dreamrealdefine sesquipedalian
  300. nevetdefine sesquipedalian: sesquipedalian (noun): A long word. (Wiktionary via FreeDictionaryAPI.com, CC BY-SA 4.0: https://en.wiktionary.org/wiki/sesquipedalian)
  301. dreamrealokay, queue item #2 done! back to #4 for a bit
  302. * phaleth quit (Ping timeout: 246 seconds)
  303. dreamrealblue: okay, my thought: this needs to be attributed to an outside contributor, either through authorship (you submit it) or direct attribution (as we did with the idoru article)
  304. dreamrealIf I narrate this, I'm gonna have to use a ring modulator or something to change the narration voice, becuase these aren't my words.
  305. * phaleth joined #primate
  306. bluetrue dreamreal
  307. blueyou don't *have* to narrate it though
  308. bluewe should make a podcast recording out of this article really
  309. phalethdiagrams now display correctly in librewolf
  310. * lioloc joined #primate
  311. liolocblue: Hey blue, are websockets up to date in the primate documentation?
  312. lioloci only found this: "https://primate.run/guides/responses/websocket-chat"
  313. phalethtake a look at https://rcompat.repopack.app
  314. nevetrcompat — JavaScript standard library
  315. phaleththere is currently only this change pending https://i.imageupload.app/43b5fc35da9bbdc36d38.png
  316. liolocoh interesting, do you know if blue is going to update the documentation website for primate.run? It looks homeless compared to this one, looks clean
  317. phalethyou mean the design or the content?
  318. liolocdesign
  319. phaleththere's gonna be some pema section when 0.43 is out
  320. phalethoh, hmm, dunno
  321. phalethcan you create a task in primate repo?
  322. liolocI can, but i'll have to first identify the issues with it, there's a few things that break on mobile
  323. * blue quit (Remote host closed the connection)
  324. liolochow are you btw? thanks for helping me out on a sunday :D
  325. phalethok, I think blue fixed some mobile issues, but it's all stuck with 0.43
  326. phalethI'm doing alright
  327. phalethcan you test against https://primate-master.repopack.app ?
  328. phalethhmm, I think I got the wrong url, one sec
  329. phaleththe server has died
  330. phalethbye bye blue
  331. lioloc😵
  332. phalethheh, weird, that never happens, but the uptime is of course not 100%
  333. liolocits ok, i'm busy doing other stuff anyway
  334. lioloci'm building a meal prepping app with a primate server as my backend and native swift app, personal app for now
  335. liolocwould be so awesome if i could have used primate for the ios app as well
  336. phalethcool
  337. phalethlioloc: https://primate-master.repopack.app is the one that tracks master branch, if you find issues there then please create tasks
  338. nevetPrimate — The Universal Web Framework
  339. * blue joined #primate
  340. phaletheven small tasks are good, does not have to be super detailed
  341. bluephaleth: hey, did you restart the server?
  342. phalethblue: there was a server restart all the sudden
  343. blueah ok, hm contabo
  344. phalethactually a slow one, but contabo never claims 100% uptime
  345. phaletheverything needs maint
  346. phalethone container didn't start, I think that's repopack docs, will redeploy it
  347. blueright
  348. bluelioloc: you had a question?
  349. phalethhmm, it only took 7 seconds to deploy
  350. blueyes
  351. bluephaleth: I merged the rcompat native ws rewrite, so rcompat should now be completely depsfree and ready for dog
  352. phalethok, did you merge the favicon and logo optimizations?
  353. bluenot sure
  354. bluenot yet, will review
  355. blueI like the rcompat logo
  356. bluedunno who made it, but it's cool
  357. phalethyeah, but the SVG is huge, so I made it simpler
  358. blueI think it's time to start looking at repopack#283
  359. blueI've been pretending it doesn't exist for a while
  360. phalethtrue
  361. phalethhttps://repopack.com/project/rcompat/tasks/59
  362. blueyes, reviewing
  363. bluethe rcompat image builds in 15s.. still too slow
  364. phalethI'm working on logo and favicon for flog
  365. blueand dog?
  366. blueremember dog's motto...
  367. phalethrcompat build uses pnpm
  368. blueI guess flog comes first because it already has a website
  369. blueyes I know, it needs to switch to flog
  370. bluedog's website will be dog.flog.run
  371. phalethI was planning to do that, but still kinda waiting for trust me bro installer
  372. blueyes that's 283
  373. phalethnah, dog does not need a website yet
  374. phalethalso flog's docs are outdated already
  375. blueoutdated how
  376. phalethwaste of tokens, it should have been just a frontpage
  377. bluethis reminds me flog needs `flog outdated`
  378. phaleththere is something about primate migration
  379. * blue creates task
  380. phalethheh
  381. blueyeah, the primate migration needs to get out of there
  382. blueclanker overcomitted on that
  383. blueI somehow don't like rcompat's font
  384. bluesuch a generic documentation font :/
  385. bluefeels like it's inter of smth
  386. blueor smth*
  387. blueoh, it is inter, LOL
  388. bluetotally soulless
  389. blueI like the code snippets
  390. blueboth the colours and font, ui-monospace. they're good
  391. blueI just don't like the prose font
  392. bluemaybe you have a better suggestion
  393. phalethlioloc seems to like rcompat docs
  394. phalethI only need to see if the logo gets updated properly
  395. bluewell he helped writing them, why wouldn't he like them
  396. blueor do you mean the website
  397. phaleththe design
  398. bluercompat logo merged
  399. bluehttps://repopack.com/project/primate/tasks/226
  400. blueI'm honestly thinking of pulling this into 0.43
  401. blueI have half a mind to release a primate 0.43 that comes with totally outdated rcompat versions, and then I'm gonna need to start backporting nonsense
  402. blueso better pull off the plaster now than later
  403. phalethcool, looks fine
  404. blue(that's bandaid, for our american friends here)
  405. liolocblue: hey blue! yeah i was just wondering if the docs had a page on websockets, or if the most up to date page was the guide "https://primate.run/guides/responses/websocket-chat"
  406. phalethyeah, rcompat updates is just chores
  407. bluehey lioloc. so are you asking if it properly reflects the source code, or whether it updates with 0.43?
  408. liolocand yeah i prefer the documentation website for rcompat than primate
  409. lioloclooks nice
  410. bluebecause we haven't done a lot of work on websockets in 0.43
  411. liolocmore so if it is up to date in general
  412. bluewell, the @primate/http example is a bit ridiculous, we should switch to marko or svelte, but I thik it's uptodate
  413. liolocin case it wasn't an old page
  414. bluelet me sweep over it shortly
  415. blue@primate/html*
  416. bluethe guides should ideally contain switchable examples when they show frontend snippets, but it's too much work
  417. bluemaybe now with AI it's improvable
  418. bluebtw lioloc, I'm not particularly set-in-stone about the primate website design, if you have another suggestion, create a task and send it to revie
  419. bluefortunately now with task apps I can quickly review for aesthetics
  420. blueand yes, the example is correct. it contains a small bug, which I'm going to fix for 0.43
  421. liolocyeah tasks make it quite easy to make updates, pretty neat
  422. liolocoh it does? I'm using it atm
  423. liolocnot with html
  424. liolocjust as a raw endpoint
  425. blueit's a huge bug, just a small incorrectness in the examples, I'll show you the fix
  426. bluehttps://repopack.com/project/primate/tasks/230
  427. blueit's not a huge bug*
  428. bluelioloc: the next rcompat versions got rid of their last few deps (busboy and ws, both for @rcompat/http on node), and replaced them with custom implementations, which are faster than those packages
  429. bluercompat is now completely dependency free, as it should be
  430. bluethe stdlib should not rely on npm
  431. bluethis is also somewhat relevant for the future of rcompat and flog/dog https://repopack.com/project/flog/tasks/74
  432. blueI believe I found a golden path there, but it's yet to be seen if it's doable
  433. bluethere's also `flog format`, `flog lint`, `flog test` (which is proby, really) and `flog test --coverage` coming for flog, but most of those need AST stuff and thus will need to wait for dog
  434. blueflog will refuse to publish with any "std:" imports in the tree, unless --std-compat or --std-pure are provided
  435. liolocwhen you say rcompat is completely dependency free, it still uses node for some stuff or not at all?
  436. blueyes, it uses node, just not npm
  437. liolockk gotcha
  438. liolocthat's insane
  439. liolocvery cool
  440. blueya
  441. liolocand you're using flog already?
  442. blueyes, primate has already switched to flog for 0.43, and it's faster than pnpm
  443. blueand safer, too
  444. bluewe're waiting for release primitives to land in repopack so people can download flog from flog.run
  445. liolocneat
  446. bluewell, 'waiting' is a general term here. I need to do it
  447. blueit's more like phaleth is waiting and I'm wasting my time playing with Dog
  448. bluebut I sometimes need the right mindset to get into a task, and until I get it sorted it in my head, I don't start
  449. blueright now it's a bit hard to conceptualise whether releases draw from job runs or vice versa
  450. blueI guess they need to draw from job runs, but also that means you can only create a release after the job has finished running, at the ref you want to create the release
  451. bluemaybe we'll just go the gh way where you create or choose a tag. but still creating a tag would then need to run a job and create the artifacts first
  452. blueanyway, I'm not entirely convinced here which way is the good way, need to sit on it a bit longer
  453. blueshould be done hopefully by next week, I want to push 0.43 out the door
  454. phalethcan have release stable and release unstable
  455. phalethstable is supposed to be tagged
  456. blueyeah but like, I don't wanna a second mechanism to create artifacts
  457. bluejobs already do that
  458. phalethone stream of runs, overlaping
  459. * skillbot quit (Remote host closed the connection)
  460. * skillnews quit (Remote host closed the connection)
  461. blueand releases should probably include the source in one way or another
  462. phalethsecond mechanism?
  463. blueyes
  464. * skillbot joined #primate
  465. * skillnews joined #primate
  466. bluejobs can already create artifacts
  467. bluebut releases should offer the source as tar.gz etc.
  468. bluethat's another 'artifact'
  469. blueI don't want two systems
  470. bluemaybe it's unavoidable
  471. phalethcreating tag does not have to run job, just take artifacts from tagged commit and rename those
  472. blueyes but who creates the tar.gz of the source at the ref?
  473. bluewhat primitive? the release or the job run?
  474. blueif the release owns it, then that's two mechanisms that own artifacts
  475. phalethI'd not worry about tar of source
  476. phaleththat's like duplicating the source code, downlodable artifacts is the goal
  477. bluefair, so you're leaving it to the jobs
  478. blueyou know, maybe jobs should just have the option of delivering source artifacts
  479. blueI think that possibly solves the conundrum
  480. blueand then releases are just light tags that link to job runs (and freeze them, so they don't get cleaned up)
  481. phalethtar.gz is another issue, that needs to be downlodable on demand
  482. phalethnot stored permanently with release
  483. bluek
  484. bluephaleth: there's a new feature on repopack
  485. blueif you hit p, you get the quickjump to projects, don't know if you knew that
  486. bluehowever, if you fully type the name of a project, you can also quick-quick to a task there
  487. bluetry it, hit p
  488. bluethen write repopack:283
  489. blueand Enter
  490. phalethI knew about /
  491. blueyes but you didn't know about p, t, j and a
  492. bluehitting t, j or a and immediately Enter also jumps to the section itself
  493. bluekinda neat
  494. phalethforwardslash does not accept repopack:283 but p does, weird
  495. blueyes because forwardslash isn't in project mode
  496. phalethah, you can switch to /projects from /
  497. blueyes
  498. phalethblue: take a look at tasks in review in the flog repo
  499. * phaleth quit (Quit: phaleth)
  500. bluedreamreal: I did another sweep of the article. I think it's much better now, care to rereview?
  501. * jreicher quit (Quit: In transit)
  502. * lioloc quit (Ping timeout: 240 seconds)
  503. * jreicher joined #primate
  504. * theskillwithin joined #primate
  505. * theskillwithin left #primate (Textual IRC Client: www.textualapp.com)
  506. * nevet joined #primate
  507. * blue!~blue@user/blue changed the topic to: https://primate.run | This channel is logged: https://bytecode.news/logs/irc/libera/primate