ByteCode.NewsSubmit
Use quotes for an exact word.

Subscribe

RSSPodcast
Log in

Chat Logs

  1. bluehype https://repopack.com/project/rcompat/tasks/61
  2. dreamrealhttps://bytecode.news/posts/2026/10/there-is-no-irrelephant
  3. bluedreamreal: wow
  4. dreamrealtold you I thought it was a firecracker
  5. bluedamn
  6. dreamrealAs always: if you think the content's valuable, or might be valuable to someone, please share it: without grassroots involvement, that site runs on whatever passion I have room to give it, and I'm *busy*
  7. blueI just realised that since I restart the server, I'd only rejoined #primate...
  8. blueI should add everything to my autojoin, but can't be bothered
  9. bluerestarted*
  10. dreamrealwhich client do you use?
  11. blueirssi
  12. dreamreal*nod* I don't remember how to configure it in irssi, I moved to weechat a long time ago and don't remember why
  13. bluedreamreal: I *love* compaction in repopack. it's basically like to distilling everything that happened before, and creating a new baseline for tasks. It's amazing because it's a much better way to move tasks with changing requirements forward, than editing notes
  14. bluehttps://repopack.com/project/repopack/tasks/283
  15. blueyou probably can't see that... but it looks REALLY nice
  16. blueI tried to give you read access to tasks on repopack, but I think you never accepted the invite
  17. dreamrealI don't remember that, either - I might not have, I get a ton of data across all input streams and I don't want to use tooling to sort it because I'm human, damn it!
  18. blueoh well, if you're ever interested or have the time, drop me a message
  19. dreamrealYou saw the issue I filed sunday or monday, yeah?
  20. bluehttps://repopack.com/project/primate/tasks/231
  21. bluethis?
  22. blueno I didn't, I was off monday
  23. bot[ByteCode.News] There Is No Irrelephant - https://bytecode.news/posts/2026/10/there-is-no-irrelephant
  24. dreamrealIs that the <head> bug?
  25. blueyes
  26. dreamrealthen yeah.
  27. dreamrealIt's not a huge thing, just duplicated data
  28. dreamrealand I think the OG stuff that requires node_modules is because the modules I used kinda suck
  29. dreamrealthey work but meh
  30. bluewell yeah, need to get rid of that
  31. bluenode_modules has lost nothing in deployment
  32. dreamrealWorking on backend streampack issues first, for forge subscriptions
  33. blueyou don't really put in your entire maven tree in java deployment either, as far as I know
  34. dreamrealwell, I think the problem is that they look stuff up at runtime
  35. dreamrealbut I'm not sure, I just needed OG to work pronto
  36. blueprimate actually copies node: addons too into the build folder. the idea is that the build folder must be self contained. you should be able to copy it whole and deploy from anywhere
  37. blueif this invariant is violated, it can have two reasons. either you messed up, or primate messed up
  38. blueI believe there was a marginal case where primate could not copy the .node addons due to some weird dynamic shenanigans
  39. blueor perhaps the mechanism just doesn't work, I haven't used it myself often, it worked the last time I did
  40. blueanyway, if it's an in-tree issue, I suggest you fix it, it'll improve the security and speed of deployment. if it's a primate issue, please file a task
  41. dreamrealI don't know, will have to look - it was satori, I think, if memory serves - I was *busy*
  42. dreamrealand was like "oh crap, why is OG failing, must make it work"
  43. blueopengraph?
  44. bluehttps://www.npmjs.com/package/satori ?
  45. bluehttps://repopack.com/project/primate/tasks/231 is done
  46. dreamrealI *think* so, and yes, the opengraph stuff
  47. blueoof, vercel
  48. dreamrealI've got two pri 1 fires to put out right now, so will deploy ASAP but not immediately
  49. bluebuddy, you got yourself in some deep manure there
  50. blue(vercel makes nextjs :P)
  51. dreamrealAll the OG stuff was thrown together. Maybe the fix for teh issue is "rip out the OG content and do it better" but I need to provide better directions for it - JS image manipulation is not something I know well
  52. bluewhat is this specifically used for?
  53. dreamrealat delos they assigned images to a junior engineer, who managed to get image generation for frames down to 120ms/per, at 16 frames per set
  54. dreamrealOG? Link previews on sites
  55. bluethe og: tags?
  56. dreamrealI got angry at them and yanked it away from the junior (who didn't do a bad job) and got all 16 frames down to 8ms
  57. bluelol
  58. dreamrealbut I did it with SVG because I'm not an idiot
  59. dreamrealand yes, the og: tags
  60. bluemein gott
  61. dreamreal(the junior did not know about SVG, nor did the CTO who assigned it to him: he was like "that won't work!" and insisted on that even after I showed him, until the guy who hired ME told him to shut up, he was embarassing himself)
  62. dreamrealso... I didn't actually gain any *actual image manipulation* experience because we didn't need images and apparently nobody else realized it
  63. blueya
  64. blueconst unbundled = (name: string) => import(name);
  65. blueew ew ew
  66. * dreamreal sighs. I liked that CTO but he did not understand programming or why you'd reason about code: he designed a language, but was utterly committed to it even though it had no BNF and no BNF could be constructed for it; he also didn't know about standard programming operators, so he'd CHOOSE operators if they were available, which is why BNF was ... difficult
  67. blueseriously, who wrote src/og/cards.ts?
  68. dreamrealblue: I think that'd why node_modules is necessary there
  69. bluethis majorly skirts primate's bundling
  70. dreamrealin ui-primate?
  71. blueyes
  72. * dreamreal points to claude
  73. * blue hits claude
  74. bluethat is TERRIBLE code
  75. dreamrealHey, I've been saying I threw it together!
  76. dreamrealI AGREE! How fix pls suh
  77. blue"Cannot fork because streampack-dev/ui-primate has forking disabled"
  78. dreamrealHold on, damn it
  79. bluethis should be on repopack, gh is so hard to work with
  80. dreamrealgrrr, it won't even allow me to alter the forking. Maybe it needs to be public.
  81. blueyou can also give me push permissions, and I'll push to rework-og or smth
  82. blueI just don't wanna push to master directly, I don't like that
  83. dreamrealIt's public, you should be able to do branches now
  84. bluek
  85. dreamrealand I don't want modules to live on rp AND GH, it needs to be a full jump for the entire project
  86. bluek
  87. bluekinda pity though you must make the project public just for someone to fork
  88. blueweird restriction
  89. dreamrealGH sucks
  90. dreamrealGL sucks
  91. dreamrealbut they're better than alternatives like "nothing at all"
  92. bluewell, RP is coming
  93. blue"Full suite: Fails during setup because no container runtime is available for the PostgreSQL Testcontainer."
  94. blueshould I fix your tests whilst at it?
  95. bluethey currently fail
  96. dreamrealoh, primate needs the testcontainer, doesn't it
  97. blueI guess because they assume stuff
  98. dreamrealI have postgres running locally at all times, and the ui modules were always sort of meant to be private modules, as you can see
  99. dreamrealso yes
  100. bluek
  101. bluedreamreal: are you interested in moving this node impl to rcompat? it currently hardcodes node: stuff, which makes runnable on bun, but not on native paths
  102. bluethat also means for you that moving ui-primate currently to bun won't speed up anything
  103. dreamrealI have absolutely NO objection to doing so, and I have no interest in moving to bun
  104. bluewell, I don't need to put in the work if cross-compat isn't a goal for you
  105. dreamrealI have no special OBJECTION to it, but eh
  106. dreamrealwell, here's my thought THERE: I do not mind a single damn bit for this to be a proofing of the projects it uses
  107. blue@rcompat/* stuff will possibly - but not guaranteed - be accessible to Dog native paths in the future
  108. dreamreallike, you see how I file bugs as I come across them, to pudl and to primate
  109. dreamrealand all of that's because the problem isn't originator's-problem-shaped, which is how to find the edges and limits
  110. blueI think Dog won't rewrite npm stuff unless it's evoked with --rewrite-rcompat or so
  111. dreamrealall I care about is that the project *works*
  112. bluewell, you know I don't like putting in work for stuff that doesn't matter to the owner
  113. blueif it doesn't matter to you, it shouldn't matter to me
  114. dreamrealwell, making it work well DOES matter to me, and giving originating projects data ALSO matters to me
  115. dreamreallike, fixing the head stuff? That makes primate better, so that's a total win
  116. blueI'm fairly agnostic on whether you use native node: paths or rcompat
  117. dreamrealbut I do not ask for free work
  118. bluemhm
  119. bluehttps://github.com/streampack-dev/ui-primate/pull/83
  120. blue"Primate 0.42.2 now handles these dependencies correctly: with ordinary static imports it bundles Satori into build/server.js and copies Resvg’s native addon to build/native/. The old workaround is obsolete, so the separate runtime node_modules installation can also be removed from the image."
  121. bluevery good, dreamreal
  122. bluevery good
  123. bluenext PR coming your way
  124. blueI told ya primate can copy native addons :P
  125. blueI specifically engineered it to do that, to avoid node_modules
  126. bluehowever, that dynamic import was black voodoo magic
  127. blueI wonder why claude did that
  128. dreamreal*nod*
  129. dreamrealProbably learned from millions of idiot JS programmers, all yapping at their keyboards stupidly
  130. dreamrealand I don't know JS well enough, being quite honest, to review the code and say "no, don't do that"
  131. blueya
  132. dreamrealat delos I LIVED in JS but that was all IOT and device interaction and a completely different profile of problems
  133. blueya
  134. bluewell PR is updated, and as I can see, now merged
  135. dreamrealI'm testing it locally before pushing live
  136. blueya
  137. blueI also found out why claude did it
  138. dreamrealjust run fails with five build errors: `client/annotate.ts:11:25: ERROR: Could not resolve "@streampack-dev/clientjs/annotate"`
  139. dreamrealwhy did claude do it?
  140. blueit claims primate can't bundle satori
  141. dreamrealhaha
  142. dreamrealwell, that would explain it, yes
  143. bluedo `npm ci`, then `just run`
  144. dreamrealgrrrr, damn it to hell
  145. dreamrealthank you
  146. blueyw
  147. bluejust to be fair to claude, it did find an issue with some wasm stuff back in satori 0.32. but that was 2 months ago, your primate is newer. it might have relied on old satori package data
  148. blue("it" meaning my codex, not claude)
  149. blueanyway, let's see if it works
  150. blueI at least can't see that it has issues bundling satori locally
  151. dreamrealDoing a full release and deploy, can revert if necessary
  152. bluek
  153. dreamrealYou reverted the dockerfile, yeah?
  154. dreamrealor fixed it, rather
  155. blueyes, I simplified the containerfile back to node_modules-free
  156. dreamrealgrazi
  157. dreamrealtodah
  158. dreamrealsorry
  159. blueyw
  160. dreamrealpushing image now
  161. dreamrealyep, works like a champ
  162. dreamrealblue++
  163. nevetblue now has karma of 4.
  164. bluegreat
  165. dreamrealis live :D
  166. bluefyi, that makes your build *portable*. you could use one server for building primate, and another for deploying it. you probably use the same server, but primate allows for a split build/deploy flow
  167. bluethe important aspect is that the deployment server/image would no longer require npm
  168. bluecool
  169. dreamrealI do not build on the server it runs on
  170. dreamrealand ideally we'd have a multistage build anyway
  171. bluewell, better, now you don't need to copy node_modules across the world
  172. dreamrealYou were around when I threw the primate build together, and it was VERY literally thrown together
  173. blueya
  174. bluedreamreal: release artifacts are COMING.
  175. dreamrealnice. Working on a pudl refresh.:/
  176. bluewhy :/ ?
  177. blueI thought you liked pudl
  178. dreamrealI do, I'm refreshing it to meet the pudl design and releases
  179. dreamrealThe pudl design was based originally on pudl 0.41 and now it's at 0.69.3
  180. dreamrealI have a lot of workarounds for features pudl actually supports better now
  181. bluewow
  182. * blue still doesn't know what pudl is
  183. blueexcept it can be friends with dog, of course
  184. bluedreamreal: I need a dedicated server for dog :/
  185. bluethe vs-v8 benchmarks on my comp keep getting tainted on account of other work
  186. bluemaybe I'll try to use my other comp
  187. dreamrealpudl is two things: a UI spec and an implementation of it
  188. dreamrealit's designed around accessibility for specific types of apps
  189. dreamrealIMO it's not so great for pure presentation
  190. blueand the implementation, it's pure frontend?
  191. dreamrealyes
  192. blueso why not add a @primate/pudl ?
  193. * dreamreal shrugs. No reason not to, IMO
  194. bluewhat's your backend on the pudl client?
  195. dreamrealfor BCN the primate front end IS tuned for production, where pudl is tuned for an application view
  196. dreamrealkotlin+spring
  197. blueyou talk directly to the api, or is that ANOTHER spring app in between?
  198. dreamrealthe ui-pudl is a spring app itself, a go-between with the UI
  199. bluemein gott
  200. dreamrealso postgres <-> app <-> ui-pudl (kotlin) <-> pudl on the client
  201. bluedouble'd spring, that's a memory nightmare
  202. dreamrealthe UI is not going to talk to the api directly
  203. dreamrealnot really
  204. bluewhy not?
  205. dreamrealmemory usage on that container's pretty low
  206. dreamrealwhy would it be a nightmare?
  207. blueI got (an older version of) nevet on the repopack vps, it's like 685M
  208. bluememory hog to no end
  209. dreamrealnevet's the backend though
  210. blueyes
  211. bluethat's the 'app' in your <-> chart, yes?
  212. dreamrealyes
  213. blueso what has a memory usage that's "pretty low"?
  214. blueui-pudl (kotlin)?
  215. dreamrealui-pudl
  216. bluehow much?
  217. dreamreali have it set pretty aggressively, it's around 300m, the primate version's way lower, but 300m on that server is well within constraints and could be dropped
  218. dreamreala lot of that is teh base image itself
  219. blueomg
  220. dreamrealme shrugs
  221. blueyou know repopack is 269mb, right?
  222. blueand it's not even optimised!
  223. dreamrealsure
  224. blueanyway, I think should be possible to create a @primate/pudl, though the gains mightn't be beyond less memory use
  225. dreamrealsure
  226. blueunless it has like ssr and friends
  227. dreamrealI want to say the author does all his backend stuff in go or C#
  228. bluewhich author
  229. bluealso, why does pudl release a very like every few hours
  230. bluethat's such churn
  231. blueI don't think I'd be able to keep up with that
  232. bluea version*
  233. dreamrealclaude
  234. dreamrealof course
  235. dreamrealhe works for a POS vendor, I think
  236. dreamreallike, point of sale
  237. blueyes
  238. dreamrealUsed to work for NCR, and Samsung
  239. bluesounds like a korean
  240. bluedo you know the guy?
  241. dreamrealFloridian like me. I've known him since I was 14. :D
  242. blueoh
  243. dreamrealhe was the best man at my wedding.
  244. blueoh WOW
  245. blueoh goddamn it
  246. blueI KNOW this guy, he lives in singapore
  247. dreamrealyes
  248. blueyou spoke about him before, I'm 100% certain
  249. dreamrealyes
  250. dreamrealI am too
  251. blueok, now it's falling into place
  252. dreamrealfor him, pudl's research+application, which is how I'm using it, too :D
  253. bluewell, as we all know, the best people are from florida
  254. * blue looks at perigrin
  255. blue- Full clean: 0.26 s vs 0.43 s — about 40% less wall time
  256. blue- Repeat install: 0.06 s vs 0.11 s — about 45% less
  257. blue- Production closure: 0.06 s vs 0.11 s — about 45% less
  258. bluedreamreal: flog vs pnpm, on the primate repo
  259. dreamrealhah
  260. dreamrealnice
  261. dreamrealclosing in on the pudl refresh
  262. bluenice
  263. dreamrealvery much a change in UI design
  264. bluealso: rcompat full API docs are coming
  265. dreamrealVERY nice
  266. dreamrealI'm using the pudl refresh to avoid fixing some severe requirement mismatches at $work
  267. bluecool
  268. dreamrealI actually told them today that i was rejecting the request with "the speed of light disagrees with this requirement"
  269. dreamreal"can we make our 8-cpu system emulate a cray with 800 cpus?"
  270. dreamrealum, no. You need 800 cpus to do that.
  271. blueoO
  272. bluelol
  273. dreamrealWe built the module on a specific set of requirements, and overshot them by 50%... and from the user: the actual requirements look NOTHING like our stated expectations, by like 15000%
  274. dreamrealyes, I typed the right number of zeros
  275. blue... and you need 800 cpus
  276. dreamreal"and oh can we make it faster?"
  277. dreamrealLike, "we built this to handle 150k inputs, and the requirements said 75k was likely" "cool, here's a 4T input and BTW the search vector isn't 800 but more like... uh... 24000"
  278. dreamreal"and oh yeah, you take 3ms for the 75k, can we do that 4T input in ... we'll have some grace, 5ms?"
  279. dreamrealme: "no."
  280. dreamrealnote: we have CSRs TALKING TO THE CUSTOMERS THE WHOLE TIME.
  281. dreamrealHow in the effing hell does this kind of scale thing not get brought up
  282. dreamrealYou might describe me as vaguely unhappy :D
  283. bluelol
  284. bluethis is the reason it's hard to trust clankers: const workspace = fs.ref(new URL("../../../", import.meta.url).href)
  285. dreamrealheh
  286. bluethey produce a lot of this nonsense. rcompat has a *funtion* for htis, in another package
  287. blue@rcompat/runtime.projectRoot(import.meta.dirname);
  288. blueis the correct abstraction
  289. bluethough import.meta.url should equally work there
  290. bluebut hardcoding paths.. that's bad
  291. dreamrealaye
  292. bluedreamreal: https://repopack.com/project/rcompat/tasks/64
  293. bluethis is legit cool..
  294. bluefs.spool... gets you a stream, but ONLY if it passes a digest.
  295. blueidea: to check the digest, you need to read the stream anyway; this operation saves you the trouble, when you know the expected digest up ahead
  296. blueyou can tell rcompat, I want this stream, but also, it must satisfy this digest, otherwise error out
  297. bluethat's an operation that's completely missing node
  298. bluefrom node*
  299. bluehi phaleth
  300. bluehaha phaleth
  301. blueyou lashing out at clankers is the funniest ever
  302. blue" \Stop blocking the logo and the favicon because of CPS already and go do something useful."
  303. blueLOL
  304. phalethhi blue
  305. phalethyeah
  306. phalethwhy did clanker add CPS to the docs anyway
  307. blueno idea
  308. blueit's flog
  309. bluebtw, I merged this earlier https://repopack.com/project/flog/tasks/80
  310. bluebtw, https://repopack.com/project/rcompat/tasks/61
  311. bluebtw, https://repopack.com/project/rcompat/tasks/62
  312. bluebtw, https://ptx6lcpc3-task-65.repopack.app/api/fs
  313. nevet@rcompat/fs API · rcompat
  314. bluedreamreal: ^
  315. bluesystemfault: ^
  316. blueincluding hover shenanigans!
  317. phalethlets try that linux speedup
  318. bluethese API docs are amaze sauce
  319. bluethey also unveiled some private types that should be public
  320. bluesome music for chill https://www.youtube.com/watch?v=KLlXJH7oJSI
  321. nevetYouTube: Tocotronic – Freiburg V3.0 (Official Video) | Tocotronic
  322. phalethflog docs site is peak performance, rcompat docs is an app pulling in a lot of JS to the browser
  323. blueawww
  324. blueit also takes a truckload of time to redeploy, gets on my poor nerves
  325. bluehttps://ptx6lcpc3-task-65.repopack.app/api/symbol
  326. nevet@rcompat/symbol API · rcompat
  327. phalethbut why is that on site there is no app and on another kinda same there is the app JS bundle?
  328. bluewhere?
  329. blueyou mean in flog
  330. blue?
  331. blueOMG THAT LOGO
  332. bluephaleth you are a genius
  333. phalethyeah, take a look at https://flog.run vs. https://rcompat.repopack.app
  334. nevethttps://flog.run "flog — predictable JavaScript package management" || https://rcompat.repopack.app "rcompat — JavaScript standard library"
  335. phalethheh
  336. bluethe rcompat website is seriously messed up
  337. bluewth
  338. bluealso I'm not getting a favicon on flog website
  339. bluealso, we probably need to adapt the flog website colours to the logo
  340. bluedamn, this logo is too good
  341. phalethand on rcompat docs you get the favicon?
  342. blueyes
  343. bluebtecause I wired the damn thing myself
  344. phaleththen LShift + Refresh
  345. blueyeah, this is a private brave tab
  346. phalethnah
  347. bluei'll close it
  348. phalethlet me check
  349. bluegoddamn brave
  350. bluenah, not getting favicon'd
  351. phalethso you put in <link rel="icon" href="/logo.svg" type="image/svg+xml" />
  352. phalethand then it works on brave
  353. blueyes, like a big idiot
  354. blueand primate website works without it
  355. blueI have no idea why
  356. blueI hate browsers
  357. bluebrowsers suck
  358. phalethI can see the favicon no problem
  359. * dreamreal hands blue w3m, lynx, links, gopher
  360. bluemaybe it's just brave, idk
  361. phalethand I've never seen <link rel="icon" href="/logo.svg" type="image/svg+xml" /> on any website
  362. bluedreamreal, can you see favicon https://flog.run/
  363. nevetflog — predictable JavaScript package management
  364. blueoh yeah, tell me about it phaleth. dunno, clanker suggested that
  365. dreamrealno
  366. blueWHY AREN'T THE FAVICONS SHOWING UP
  367. dreamrealhas the brave browser's default "world" favioc
  368. bluefriggin brave
  369. blueI'm gonna try another browser
  370. blueI gotta know
  371. blueI might have a chromium flying around here somewhere
  372. dreamrealsafari... looks like it's rendering SOMETHING?
  373. blueHAH
  374. dreamrealit's too small to tell what it is
  375. blueIT WORKS ON CHROMIUM
  376. blueI KNEW IT
  377. * blue kicks brave
  378. dreamrealchrome works too
  379. dreamrealsafari != chromium, though, I thought. Webkit, right?
  380. phalethI bet safari does not show the favicon
  381. blueya. safari is webkit, chrome is like the google thing, whatever it's called
  382. phalethcause epiphany doesn't
  383. bluesafari webkit/jsc
  384. phalethchrome is v8 and blink
  385. bluechrome is whatever the h the google renderer is called and v8
  386. blueyes, blink, thank you
  387. blueand why can't brave show the favicon now?
  388. blueonly god knows
  389. bluewe're only in 2026 and we haven't solved yet favicons
  390. blueI'm gonn adrop this explicit <link thing in rcompat
  391. bluethis is ridiculous
  392. phalethcan brave show favicon from bytecode.news?
  393. phalethI can add some metatags, but I'd like to avoid that
  394. blueYES
  395. blueit can
  396. bluea b over a black background with a red corner
  397. bluebut damn it dreamreal, that looks like...
  398. blueyou need phaleth for a new favion
  399. phalethok, I will try to fix that later for brave then
  400. bluehe's an aritst
  401. bluephaleth where is the favicon for dog
  402. phalethdog doesn't have a website
  403. bluewe all know favicons are the most important for a project
  404. phalethdog doesn't even exists I hope
  405. phalethyeah
  406. blueya but dog exists
  407. bluehttps://repopack.com/project/dog
  408. blueI hope dreamreal doesn't die of laughter here
  409. phalethso it's like a secret project
  410. bluewell it's secret until it reaches parity with v8, yes
  411. bluecurrently it's 9x slower
  412. blueit started at 30x, so we're going somewhere
  413. bluethe real goal is 5x faster than v8, though
  414. phalethlet me give you something to read
  415. blueI read a whitepaper over go jit perf earlier
  416. bluethat went nowhere, unfortunately
  417. blueanyway, if you fix the flog favicon on brave, fix that rcompat dumpster fire too
  418. bluefavicons should be auto discoverable via favicon.ico, not in <link
  419. phalethhttps://encore.dev/blog/rust-runtime
  420. nevetWhat We Learned Building a Rust Runtime for TypeScript
  421. phalethyeah, sure
  422. bluephaleth: can you have js.stdlib.run point to rcompat.repopack.app, please?
  423. bluejust registered
  424. phalethyeah, sure
  425. bluethx
  426. bluejs.stdlib.run 207.180.197.249 600
  427. phalethfavicon shows up twice on palemoon https://i.imageupload.app/7c3a342918e297635996.png
  428. bluerecord is there
  429. phalethalso the site is fast on palemoon cause it's peek performance
  430. bluedog will be hosted at dog.flog.run, fyi
  431. phalethhope you didn't pay $8k for that domain
  432. blue$4
  433. phalethok, nice
  434. phalethanyway, why js as subdomain?
  435. bluebecause it's a js stblib
  436. bluestdlib*
  437. phalethok, well, then there will be a TLS cert jut for that, but why not use stdlib.run also?
  438. phalethat least temporarily
  439. phalethand www.stdlib.run for that matter as well
  440. bluewe can use stblib.run if you prefer
  441. blueI'm not dogmatic on that, I just thought js. is cooler
  442. bluedreamreal: opinion?
  443. bluejs.stdlib.run or stdlib.run ?
  444. phalethok, I will setup all three of them with the same TLS cert
  445. dreamrealI'm all for it! What is the opinion about?
  446. blue20:15 < blue> js.stdlib.run or stdlib.run
  447. dreamrealoh, js.stdlib.run
  448. dreamrealit's scoped to js
  449. dreamreal... said with no forethought whatsoever on my part
  450. bluephaleth: we can redirect stdlib.run and www stblib.run to js.stdlib.run
  451. phalethok, I will setup the rewrite
  452. blueA js.stdlib.run 207.180.197.249 600
  453. blueA stdlib.run 207.180.197.249 600
  454. blueCNAME www.stdlib.run stdlib.run. 600
  455. bluegood?
  456. blueI thought of CNAMING directly to js.stdlib.run, but nah, sounds weird
  457. blueanyway, all three should point at rcompat.repopack.app, methinks
  458. blueor rather, the non js. ones should probably redirect to .js
  459. bluejs.*
  460. blueyeah, probably best
  461. phalethyeah
  462. bluethen dreamreal could send his buddy a real nice domain
  463. blueand his buddy won't have reservations anymore, clearly
  464. bluebecause domains are all that matters
  465. dreamrealwell, the ability to understand is relatively important
  466. blueya
  467. blueI should be able to finish the API docs today or tomorrow, and merge htem onto master
  468. blueand together with the new domain, it's gonna be wicked
  469. bluethen I'm gonna fix the flog website and throw out all the nonsense clanker garbage about primate
  470. blueout-of-the-box thinking is not a particular strength of clankers, I find
  471. blueyes, I used primate as a reference point for flog working as intended, that doesn't mean you need to write A WHOLE SECTION about it into the docs
  472. blueidiot
  473. dreamrealyes, they take offhand suggestions and explanations VERY seriously
  474. dreamrealI think I wrote an article about that
  475. blueI think I read it
  476. dreamreali think so, too. :D
  477. bluephaleth: btw, I fixed the node_modules pulling-in on BCN's primate client, earlier. clanker hallucinations
  478. bluenow it's pristine, and dreamreal's server is spared from sinking into the black hole known as node_modules
  479. dreamrealI find "hallucination" to be the wrong term - they're not hallucinations as much as model inferences
  480. bluewell, in that it decided that primate can't bundle .node addons, which is specifically NOT the case
  481. phalethblue: oh, I was gonna look into that, so you fixed that in primate?
  482. dreamrealit inferred, because it has no judgment
  483. blueno, I fixed it in BCN/primate
  484. dreamrealhe fixed it in the build
  485. blueas in, ui-primate, I mean
  486. phalethok, cool, I will see what you did
  487. dreamrealit was my code, not primate's, because *I* didn't write the primate UI, I directed it
  488. blueclaude really outdid itself there
  489. bluepeak stuff
  490. phalethor what clanker did anyway, curious
  491. blueit tried (and managed) to bust primate's bundler by inventing a dynamically importing function
  492. bluebecause it was of the opinion that primate can't do something
  493. blueproblem if, there are very few things, and still fewer USABLE things, that primate's bundler, esbuild, CAN'T do
  494. blueproblem is*
  495. bluehttps://github.com/streampack-dev/ui-primate/commit/5697be1ad785ba423b8a9ead3738756fedcc9615#diff-7bd1e06f12808abf8ebcab5b3789bc58f25461cc27e79f616ea5fceb84b48af6L9-L11
  496. nevetMerge pull request #83 from terrablue/master · streampack-dev/ui-primate@5697be1
  497. blue"satori's WebAssembly and resvg's native binary don't survive Primate's server bundle"
  498. bluethis is a lie
  499. bluehence hallucination
  500. blue"and Primate has no way to leave a package out of it"
  501. bluethis could have been true at the time. I believe it arrived in 0.42, and ui-primate was written against 0.41
  502. bluehowever, irrelevant, because the capability wasn't necessary
  503. bluehence this amazing code: const unbundled = (name: string) => import(name);
  504. bluewhich esbuild can't unroll
  505. blue>_>
  506. bluehttps://ptx6lcpc3-task-65.repopack.app/api/type
  507. nevet@rcompat/type API · rcompat
  508. blueis now ported
  509. blueI gotta do something about these terrible task urls
  510. perigrinfloridia does represent ... as do ex samsung employees
  511. bluelol
  512. perigrin*Florida (see you can tell I'm a product of Florida's education system)
  513. blueYou're a Florida Man :P
  514. perigrinI have my moments.
  515. bluelol
  516. bluephaleth: I love the flog logo
  517. bluewhen I'm done with the rcompat website I'll prop up the flog website
  518. phalethI had to put temporary redirect there cause otherwise browser will not change the hostname of the url https://stdlib.run/
  519. nevetrcompat — JavaScript standard library
  520. phalethheh, ok, I had fun making that logo
  521. phalethactually I think the colors could be better, but whatever
  522. phalethblue: anyway, try to figure out why is the rcompat docs site a full blown app, that's kinda weird
  523. blueya will do
  524. bluephaleth: peak rcompat website coming
  525. phalethnice
  526. blueThe workaround now produces fully static pages:
  527. blue- /api/array: 16,569 → 6,873 bytes (−59%)
  528. blue- /api/assert: 186,290 → 75,266 bytes (−60%)
  529. blue- Browser JS: 85.8 KB → 0
  530. blue- Hydration/walker scripts: 3 → 0
  531. blue- Page responses now include Cache-Control: public, max-age=300, must-revalidate
  532. bluephaleth: good? ^
  533. bluealso seems to have found a Marko <Head> bug, but perhaps dreamreal has already reported, unsure if this is the same thing
  534. phalethawesome
  535. blueI reported upstream to the primate team, hope they have some competent people to fix it
  536. bluehttps://repopack.com/project/primate/tasks/232
  537. bluethis isn't relevant I think to dreamreal, he uses hydration
  538. phalethyeah, bytecode.news uses the app
  539. blueanyway I don't think the primate team will backport it to .42
  540. bluenor doe the rcompat consider it necessary
  541. blueso it's all good
  542. blueprimate#232 is being worked on
  543. phalethmarko({ csr: false }) does the trick, nice
  544. blueyes
  545. bluebut still, the <Head> tag should play nicely without hydration
  546. blueand not force a workaround
  547. bluethe primate team is on it, but it won't get out until .43
  548. phalethcan you do a deployment preview on https://repopack.com/project/rcompat/tasks/65 ?
  549. bluehttps://ptx6lcpc3-task-65.repopack.app/
  550. blueit's building right now
  551. phalethoh, it was already there, it says No Preview on the task page for me
  552. phalethgreat, that's super fast
  553. blueya, I might need to fix permissions there
  554. bluethere you go
  555. bluefixed
  556. phalethyeah, now I can see the preview link
  557. blueyeah, very fast
  558. blueignore that terrible link. it'll look better in repopack ui once I have a bit of time
  559. blueshould be a button, not a link
  560. blueoh man, those websites are FAST
  561. phalethit's an anchor tag
  562. phalethbut that's good
  563. blueya
  564. bluenice, js.stdlib.run is online!
  565. blueonce I'm done with the api stuff I'll merge it and then it's all fine and dandy
  566. phalethso it's server rendered from TypeScript?
  567. blueyes
  568. blueit's hard to get dreamreal excited about stuff: so if I managed to do it, I know I'm on the right track
  569. phalethshould be fast the, not sure about node
  570. blueya
  571. phaleththen*
  572. bluewith dog will be faster
  573. bluealso rcompat is still being bundled with pnpm
  574. bluewhich is going to be addressed soon
  575. blueanyway, I'm off to play a board game and then chill for the rest of the evening
  576. blueyou fine gentleman, have a great rest of day
  577. bluegentlemen*
  578. bluealso note the wallop by libera team, and update your browsers/systems if applicable
  579. bluesomething something certificate keys leaked
  580. phalethok, bye
  581. dreamrealblue: let's talk in the morning about the zig article
  582. bluedreamreal: ok mate
  583. dreamrealAre you happy with where you left it?
  584. bluemostly, yes. I've kept some distance for a final human pass, it's still a bit too clankery
  585. bluefor my taste
  586. bluemostly thinking about std loaders right now, dreamreal
  587. bluewhether I want to do @rcompat/{yaml,toml,json5,jsonc}, or skip for now. bun offers most of them native, and it's something that I think would be good to have in a stdlib
  588. dreamreal*nod* I think the next question for that zig thing is what you want to post it as: do you want ME to post it an attribute it to a pseudonym, do you want me to edit it for voice to remove some of the clanker-y bits, as you put it...
  589. dreamrealdo you want me to narrate it, etc
  590. bluedreamreal: I think we can post it under my `blue` username. But I'd be grateful if you could edit it for voice and remove the clanker-y bits, because one of the thing that annoyed me about the last article I wrote on my blog, was how many people complained it was AI-generated. I do NOT want the HN plebs to complain about that - they should engage with content, not tone, but it's very hard for them to do
  591. bluethat if they smell clankerness
  592. blueone of the things*
  593. dreamrealblue: okay, will look at it tomorrow morning
  594. bluethx
  595. bluedreamreal: https://js.stdlib.run/
  596. nevetrcompat — JavaScript standard library
  597. bluehttps://js.stdlib.run/api
  598. bluefull API
  599. bluethere are still a few smaller things to fix, but it's looking good. tomorrow I'm going to publish new versions of everything