Chat Logs

  1. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is publicly logged at https://bytecode.news/logs/irc/libera/primate and mirrored to Primate discord, channel #irc
  2. * nevet joined #primate
  3. * skillbot joined #primate
  4. * skillnews joined #primate
  5. * jreicher joined #primate
  6. blueWB nevet, jreicher.
  7. * jreicher joined #primate
  8. * nevet joined #primate
  9. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is publicly logged at https://bytecode.news/logs/irc/libera/primate and mirrored to Primate discord, channel #irc
  10. * lioloc joined #primate
  11. liolocblue: Hey blue! does the sqlite db package support a turso libsql database url?
  12. bluelioloc: hey; I'm unsure; the sqlite generally delegates to the native adapter
  13. bluethe sqlite package*
  14. blueI could check it for you
  15. bluelioloc: "No. @primate/sqlite currently accepts only a local database path or ":memory:". Its underlying @rcompat/sqlite client wraps node:sqlite or bun:sqlite, neither of which supports Turso鈥檚 libsql:// remote URLs."
  16. liolocah ok thanks
  17. blueIf you need this capacity, consider submitting a task to primate or rcompat. if libsql is standardised, this should be in rcompat, if not, in primate. can't promise implementation, but will consider
  18. blueif libsql:// is standardised*
  19. bluehttps://repopack.com/project/rcompat
  20. blueguest roles can report/read tasks
  21. liolocah ok, I will probably make my own module for this
  22. blueok, up to you
  23. liolocYeah I need it for a project i'm working on right now
  24. bluelooks like something @primate/sqlite could benefit from if it doesn't mean pulling in deps
  25. bluebbiab
  26. liolocinitially for speed I'll use an external dep, but if it works well i'll have an ai create it without dependencies
  27. bluek
  28. dreamrealhey, the signin feature works!
  29. dreamrealwoot!
  30. * nevet joined #primate
  31. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is publicly logged at https://bytecode.news/logs/irc/libera/primate and mirrored to Primate discord, channel #irc
  32. bluedreamreal: signin?
  33. dreamrealthe url you posted for repopack has a title of "sign in" which nevet did NOT echo because it failed the rule for "no signin pages"
  34. dreamrealfound an rcompat bug
  35. blue`task report --project rcompat`
  36. blue`task report` will *probably* be removed in the future and I'll just make it possible to use --project with all task commands, but for now it's still limited to reading tasks
  37. * nevet joined #primate
  38. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is publicly logged at https://bytecode.news/logs/irc/libera/primate and mirrored to Primate discord, channel #irc
  39. dreamrealOKAY, massive UI refresh coming up
  40. dreamrealyeesh
  41. dreamrealnot a lot visually changes, which is good
  42. dreamrealbut it's been all morning :D
  43. * lioloc quit (Ping timeout: 243 seconds)
  44. bluedid you report it, dreamreal?
  45. blueI don't see anything
  46. dreamrealShould be... primate task #183?
  47. blueI thought you said rcompat
  48. blueI'll look at it
  49. dreamrealoh, I think it's an rcompat bug, but ... found it in primate, so... err.... I AM A GENIUS
  50. dreamrealor something
  51. blueright
  52. dreamrealhttps://bytecode.news/atlas
  53. bluewow, awesome sauce
  54. blueyou konw, dreamreal, the one thing that takes me the longest is this review-revision cycle. I need to tell the agents to look at it. This is actually something that repopack chat solves: it will allow you to set a session to `autonomous`; so its agent (who is attached to a task) will be informed if attention is needed, either rereviewing, or revising
  55. dreamreal*nod* MAKE THAT NOTE and use it.
  56. dreamreal"Dangit, every time I run into ___ on $otherplatform it annoys me, I bet it annoys others too, I have something that doesn't annoy me"
  57. blueya well, it's just that they should talk to each other and work together. they don't need my input at these stages; if they did, they owuld stop
  58. dreamrealSure
  59. dreamrealjust saying that this is how you communicate the awesome sauce to others
  60. dreamrealI have the workaround for the problem but would far prefer it be in primate/rcompat, obv
  61. dreamrealBBIAF
  62. dreamrealthe atlas is what found the bug, FTR
  63. bluercompat and primate are both getting patches soon
  64. bluehttps://repopack.com/project/rcompat/tasks/4
  65. bluejust need to give this out of the door first
  66. bluewith omarchy.. could be good to have
  67. dreamrealno worries, and no hurry
  68. blue+1
  69. bluedreamreal: primate 0.42.2 is out
  70. blue+ rcompat patch, but that's not your direct concern, likely
  71. * phaleth joined #primate
  72. bluehi phaleth
  73. bluenub is such a dumpster fire, it accidently published a -pre package and marked it as latest...
  74. bluehttps://repopack.com/project/primate/tasks/185
  75. blueridiculous broken vibe software...
  76. dreamrealblue: doing a general tag cleanup now, which should end up touching the UIs, will update when it gets there
  77. blueand I couldn't even hit ctrl+c or ctrl+d on it. that's how bad it is, phaleth
  78. dreamrealright now tags are split between content and factoids, that needs to be normalized
  79. blueok dreamreal
  80. dreamrealand thank you!
  81. blueyw
  82. phalethhi
  83. blue"Nub asks for CLI OTP because it implements registry uploads itself. On EOTP, it invokes a terminal prompt; it has no browser authentication flow and does not retain the prompted OTP across recursive packages. Pnpm uses its web-auth implementation, opens the browser, and polls npm鈥檚 completion URL."
  84. phalethblue: oh, really, so pnpm is still needed for publishing
  85. blueit's so bad, having to enter >20 times the OTP one after another
  86. blueoh man I was so happy to get rid of pnpm
  87. dreamrealtag normalization is a necessary thing in nevet, factoids and content have different taxonomies and they shouldn't :/ resolving them is dumb
  88. blueand now nub is just a dumpster fire
  89. phalethwell, if it's just publishing for which you need pnpm then I guess that's still not too bad outcome
  90. phalethI think I saw some issues regarding publishing on the nub issue tracker, but it seems like the author does not focus on that currently
  91. bluewe need flog
  92. bluelike, yesterday
  93. blueeverything sucks
  94. blueit's like, every time you want to mvoe a step forward, you move two steps back
  95. blueso for 0.42, I can still publish with pnpm
  96. bluebut we do need a solution for master
  97. blueI'll see if we can keep pnpm for publishing, but two package managers is annoyig
  98. phaleththere is also still bunx in a bunch of places
  99. bluein primate?
  100. phalethanyway, if you just put pnpm in package.json script, you can call it with nub
  101. phalethyeah, in primate
  102. phalethor npm even if you can't stop getting used to typing nub for some reason
  103. phalethnpm run publish
  104. bluehttps://repopack.com/project/primate/tasks/185
  105. bluethis smells
  106. blueno, npm can't publish workspaces, phaleth
  107. bluenot to my knowledge, anyway
  108. bluehive mind: "So Nub builds; pnpm packages and publishes. The browser authentication and registry interaction are handled by pnpm."
  109. phalethI mean npm run publish runs the publish script that executes pnpm
  110. phalethbut can as well type nub run publish to execute pnpm
  111. blueya
  112. phalethok, I see that clanker already wrote some long TS script there
  113. blueyeah there's going nowhere
  114. bluewe're either going back to pnpm+ts check until nub gets serious, or clanker will find a way
  115. bluebest solution is, we get rid of both, they're both bad
  116. phalethnot sure it's worth adding all that code, can just modify the script line in package.json to use pnpm
  117. phalethoh, so you got rid of pnpm-workspace.yml
  118. blueyes
  119. blueI moved to nub completely, with nub.lock
  120. bluenow I'm regretting it
  121. phalethyeah, I bet, I didn't want to do that
  122. dreamrealAh, the joys of committed development :D
  123. phalethI wasn't expecting a gotcha, but it's always better to be cautious
  124. blueI'm just sad everything is bad
  125. bluethis is why I end up writing my own stuff. not because I think it's good, but because other tools just suck
  126. bluethey don't do the basic things you expect them to do
  127. phalethwell, I recommend reverting primate#178 and in primate#185 package.json modify "publish": "nub publish -r --access=public", to publish": "pnpm -r --access=public publish",
  128. phalethand also in primate#185 get rid of all that clankered nonsense
  129. phalethalso no reason to be sad about software tools, it's just tools not always perfect
  130. blueI think I'll revert nub completely if pnpm can run TS checks
  131. blueand then we just move to flog when it's ready
  132. blueclanker is on it
  133. blueit's checking why pnpm didn't do TS checks earlier
  134. phaleththere was no flag like --noCheck or the update --no-check I could find
  135. * skillbot quit (Remote host closed the connection)
  136. * skillnews quit (Remote host closed the connection)
  137. phalethbut yeah, you may as well go back to pnpm fully, which means slower clankering I think
  138. * skillbot joined #primate
  139. * skillnews joined #primate
  140. phalethupdated*
  141. blueyeah, checking
  142. phalethdeployment of primate website does not have to be done using pnpm, so using pnpm 12 is ok
  143. blueI think the next codex limit will be dedicated to getting flog to do package manager stuff
  144. bluebecause the landscape is awful
  145. phalethwait, look, it's rustified already https://github.com/pnpm/pnpm
  146. nevetGitHub - pnpm/pnpm: Fast, disk space efficient package manager
  147. blueoh god no god save us
  148. bluedreamreal: we need help
  149. phalethheh
  150. bluestarted work on flog
  151. bluephaleth: we probably need to prepare flog.run soon :P
  152. phalethyou are really gonna create a flog project?
  153. bluealready did
  154. phalethI think repopack and also primate still need a lot of work
  155. phalethand you gonna use the zig rewrite from github?
  156. blueya, everything needs a lot of work, but blockers should be unblocked. I'm giving this one day
  157. blueno, I'm gonna go with go. I kinda lost faith in the zig project
  158. phalethok, there is a js runtime written in go that's kinda popular
  159. bluethere is?
  160. blue(note I'm limiting flog for now for pure package-manager stuff, not runtime)
  161. phalethanyway, I'd recommend giving primate more effort, primate#186 makes sense
  162. phalethah, ok, that's good
  163. phalethbut you can just finish primate#186 and move on
  164. blueyeah. this is a spike, phaleth. if it takes longer than a day or two, I'll give it up and go back to primate#186 or its follow-up
  165. blueI don't intend to spend a month on it
  166. blueI just wanna untangle this situation if I can. two package managers is annoying, undoing the nub work is annoying, pnpm is annoying too
  167. blueso let's see if we can find the golden path
  168. blueI have a few other nitpicks I've had with package managers along the years, would be a chance to fix them too
  169. dreamrealthe answer is to use rust like god intended! ... or go! ... or python! ... or whatever today's favorite language is
  170. dreamrealI can't keep up
  171. phalethwell, pnpm 12 is prolly not very slow after all
  172. bluephaleth: sent you an invite to flog project
  173. phalethok, thanks
  174. bluehttps://repopack.com/project/flog/tasks?status=open
  175. phaleththe runtime is called goja, here's some performance comparison table https://github.com/dop251/goja/issues/2#issuecomment-2763265666
  176. nevetBenchmarks and performance data? 路 Issue #2 路 dop251/goja
  177. bluenot bad, phaleth
  178. phalethyeah, but the runtime needs perf, look at where ladybird sits in the table
  179. phaleththey prolly managed to optimize something during the year since the table was put together but still
  180. bluewhat's the point of putting bun in that table?
  181. phalethactually 1.5 years already
  182. blueheh, deno is slower than node
  183. bluewhat a stupid table, sorry
  184. blueconflating runtimes and engines
  185. phalethheh, yeah, but I think that's ok
  186. phalethshows engines are faster, obviously, but also by how much
  187. blueI wonder why should a runtime add any overhead at all
  188. bluewell, any meningful overhead, anyway
  189. phalethit's cause of FFI
  190. phalethv8 is C++, but deno is Rust
  191. phalethand node is C++, but they prolly also have some bindings
  192. phalethjust so they can easily update v8
  193. blueso you're saying, always write your engine in the same language as the runtime?
  194. phalethno, C++ is a mess
  195. blueyessir
  196. phalethalso don't write your engine, too many problems with web standards
  197. bluedreamreal: do we need a js engine/runtime in java?
  198. dreamrealWe already have one, depending on what you mean by "in java"
  199. dreamrealwe have multiple, actually
  200. phalethjava has nashorn
  201. blueone that can compete with v8
  202. dreamrealand graal has a different one, and there's rhino, too, if memory serves
  203. phalethnashorn cannot compete with v8
  204. phalethyeah, rhino is like a predecessor to nashorn I think
  205. dreamrealgraal MIGHT be able to but I doubt it, using JS from within java isn't really "the way to do it"
  206. blueheh
  207. * phaleth quit (Quit: phaleth)
  208. * nevet joined #primate
  209. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is publicly logged at https://bytecode.news/logs/irc/libera/primate and mirrored to Primate discord, channel #irc
  210. * nevet joined #primate
  211. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is publicly logged at https://bytecode.news/logs/irc/libera/primate and mirrored to Primate discord, channel #irc
  212. dreamrealOKAY! Now logs on pudl can be filtered to be ONLY conversation to cut out all the join/part/quit stuff
  213. dreamrealAnd now primate has the log filter in place too!
  214. dreamrealAight, I'm off for the day, seeya
  215. bluebyebye dreamreal, have a good one