ByteCode.NewsSubmit
Use quotes for an exact word.

Subscribe

RSSPodcast
Log in

Chat Logs

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