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. phalethany idea why these two respond fine https://js.stdlib.run/site.webmanifest https://bytecode.news/site.webmanifest and these two return 404 https://flog.run/site.webmanifest https://primate.run/site.webmanifest ?
  7. * lioloc joined #primate
  8. liolocmorning 👋
  9. phalethhi lioloc
  10. phalethlooks like you need a better irc client, one that can just auth you using SASL
  11. phalethalso some that gets you cloaked before joining channels
  12. bluehi
  13. phalethhi blue
  14. liolocyeah definitely, i'm using bIRC on macOS
  15. liolocif you have any suggestions I'm all ears
  16. phalethdo you like TUIs?
  17. phalethlooks like weechat can be installed on a mac https://kb.shells.com/tutorials/macOS/Weechat/
  18. bluelioloc flog 0.1.8 is out, and it supports `flog init`
  19. bluealso, repopack gains rolling release channels, I'm gonna add support for that later into flog and rp
  20. jreicherThe IRC clients in Emacs are excellent TUIs.
  21. * lioloc quit (Ping timeout: 266 seconds)
  22. * lioloc joined #primate
  23. liolocthanks will checkout the weechat
  24. liolocalso i saw that blue, actually used it as well, very neat
  25. liolocahhh i see, so some people use something like weechat and then they use tmux to persist it?
  26. liolocso that they can have it running on a vps or something and then use it on their phone?
  27. liolocor desktop
  28. blueyes lioloc, that's what I do
  29. blueI have irssi inside tmux running on a vps
  30. liolocgotcha
  31. liolocway better than my current setup, i'll do the same
  32. lioloctired of getting disconnected
  33. blueweechat is similar to irssi
  34. liolockk
  35. phalethso the file is there https://primate-master.repopack.app/site.webmanifest of course not on primate.run yet
  36. blueya soon, when 0.43 releases
  37. blueif you need to backport things in the future, just create a task with another --base, phaleth
  38. blueso if you want to change smth in the live website, you'd create a task against --base 0.42
  39. bluesince the live website deploys from that branch
  40. phalethno worries, it's gonna be out when it's gonna be out
  41. blue"Key finding: #196 must release @primate/angular as at least 0.14.0; Flog rejects 0.13.0 for the new Primate 0.43 peer range."
  42. blue<3 flog
  43. bluerelease sets are amazing, I don't get why pnpm and other package managers never built them in
  44. blueit's almost like nobody ever dedicates thought in designing actually useful software, especially for monorepos
  45. bluehttps://repopack.com/project/primate/tasks/254
  46. blue<3 flog
  47. bluehttps://repopack.com/project/flog/tasks/106
  48. blueunstable flog is coming, now with repopack's rolling channels
  49. phalethheh
  50. phalethit's just that dev tools are the worst tools of them all
  51. blueya, that's why we have flog
  52. blueto put a stop to that
  53. * lioloc_ joined #primate
  54. lioloc_hello from my vps
  55. * lioloc quit (Quit: Disconnected)
  56. phalethhello root
  57. phalethtype `/nick lioloc`
  58. * lioloc_ quit (Quit: WeeChat 4.1.1)
  59. * lioloc joined #primate
  60. liolocah better now
  61. lioloci created a service to have it autostart on load as well
  62. liolocthanks guys
  63. phalethnice
  64. phalethon VPS boot you mean?
  65. phaletha systemd service I guess
  66. liolocyes
  67. phalethsounds convenient
  68. phalethlioloc: what host OS is running on the VPS?
  69. phalethblue: is the post ready for a read since there are no XXXs anymore? https://primate-master.repopack.app/blog/primate-043
  70. nevetPrimate — Primate 0.43: diamond migrations, deferred navigation and direct SQL
  71. liolocphaleth: ubuntu
  72. phalethtry archlinux, it's way better
  73. liolocreally? how come?
  74. phalethubuntu package maintainers are way too busy messing around making software packages ubuntu specific and also pushing rust into every hinge they can
  75. phaletharchlinux is a rolling distro
  76. lioloci'm intrigued
  77. lioloci'm using hetzner, idk if i can change the os though
  78. liolocoh nvm i can
  79. phalethI used hetzner previous year and remember I could choose archlinux no problem
  80. liolocwhat do you use now?
  81. phalethI was hosting a couple of pointless wp sites and told the owner of those sites to take care of that so I don't need that VPS anymore
  82. liolocah gotcha
  83. phaleththese days I'm messing with two blue's VPSes
  84. phalethboth run archlinux without a problem
  85. phalethanyway ubuntu just needs to stop being used, their maintainers and devs are just wasting time
  86. liolocdidnt know that
  87. phalethrewriting core utils that never had a single CVE and are essentially feture complete for decades only to make them worse is a huge waste of effort
  88. liolocoof
  89. bluephaleth: yes, https://primate-master.repopack.app/blog/primate-043 is essentially ready for a read
  90. nevetPrimate — Primate 0.43: diamond migrations, deferred navigation and direct SQL
  91. phalethblue: alright
  92. blueit won't change substantially. flog found operative situations, and they were fixed
  93. bluelioloc: once superarch is done, we will migrate from archlinux to superarch. but superarch is some ways off right now
  94. bluearchlinux is currently the best we have until superarch arrives. we will then likely switch to bsd-based superarch installs, if podman is properly supported on that
  95. liolocvery cool
  96. blueonce repopack matures a bit more, I could host orz (the superarch package manager) and its packages on repopack. the first iteration of orz will likely just download packages from upstream (so node stuff from nodejs.org), but later iterations will build locally
  97. bluelinting with eslint takes so long... `flog lint` has to come sooner than later
  98. phaletheslint is there to stay
  99. blueit's very slow, we don't need it. we need fast, but not biome, biome is terrible and doesn't cover most of the useful eslint rules
  100. blueget this, phaleth
  101. bluehttps://repopack.com/project/flog/tasks/73
  102. bluethis is the future, but without Dog instrumentation. linting/formatting/test coverage will be handled by a Flog library called Stick
  103. blueDog will benefit from Stick as well later when it needs to detype .ts files
  104. bluethe reasons for Stick is that I don't wanna wait for Dog so long, Dog will still take some time
  105. blueand Flog needs to get some real useful capabilities
  106. blueI have two Dog experiments that failed, it's currently stuck on 9x V8 so it still needs a lot of work
  107. phalethnot sure what is the meaning of stick here
  108. blueDog has now moved to a pure C++ pilot, we'll see where that gets us
  109. phalethalso clanker simply has no chance as usual
  110. bluestick is essentially an ast tree interpreter, not a full engine
  111. blueyou need that for formatting/linting/etc. mostly static analysis, not a full-blown engine
  112. phalethso it's supposed to be used by dog then?
  113. bluemostly by flog for `flog format`, `flog lint` and `flog test --coverage`, but also by dog for some things. like running .ts files
  114. blueI'm gonna turn flog into a monorepo with flog and stick in it. dog will join them later, I will delete the dog project, since they'd be sharing libs
  115. bluedon't worry about it, it's all lessons learned
  116. phalethwell, flog should be able to initiate, but execution will still happen running on the engine
  117. bluedog will still be running JS
  118. phalethso I just don't think stick is an appropriate name
  119. bluenone of these are appropriate names, it's just fanciful names, they don't mean much
  120. bluebut don't worry, stick won't have a webpage and you won't need to design a logo for it :P
  121. blueit's just going to be a library used by flog and dog
  122. phalethmaking logo is not difficult, it's just the repopack project is a mess having ton of duplicates here and there
  123. phalethpretty sure sh script lines of code already exceeded 20k in that project
  124. phalethprolly some bash in there too
  125. blueit's mostly the provision part, no?
  126. blueit's all gonna disappear once we move to Go tooling
  127. phalethso as long as the website is clean it should be a no brainer to get a new logo up there
  128. phalethno clue, most likely
  129. bluek
  130. phalethit's like clanker self inflicting problems all the time
  131. bluewell, we need flog, dog and stick. they all solve real problems
  132. blueflog is already improving the way to publish packages in rcompat/primate and prevents me publishing nonsense
  133. phalethno idea what is it on about here https://repopack.com/project/flog/tasks/107
  134. phalethsounds like it invented some bash script with pnpm deeprooted and now it insists on me running that generating some more scripts to make the thing get bloated for enternity
  135. phalethalso it mentiones warnings from new apt, totally irrelevant as long as it can install whatever is needed
  136. bluesubmit it again
  137. phalethok
  138. bluethis is clanker nonsense. AGENTS.md says every change needs benchmark measurements
  139. blueI will change that guidance to "every change to .go" files
  140. phalethalright
  141. bluehttps://repopack.com/project/primate/tasks/259
  142. bluethis is likely gonna make it to 0.43 as well, because it affects repopack
  143. bluehttps://repopack.com/project/flog/tasks/108
  144. blueI'm thinking of adding shortlinks to repopack
  145. bluemaybe repopack.com/t/flog:108
  146. bluephaleth: thoughts?
  147. blueit'd just be a redirect, but easier to share
  148. blueactually the : does nothing there, could be repopack.com/t/flog/108 as well
  149. phalethcould primate@259 be backported if 0.43 was out?
  150. blueit could be, but I'm doing it now so it'll soon be done
  151. blue0.43 has passed two audits, one by sol 6.0 and one by sol 6.1. it did find a few things, those were mostly pre-0.43 stuff
  152. phalethno reason to bother with short urls
  153. blueI do wish clanker would understand that when I ask it to review a release, I mean to review it against changes to the last release, not in general
  154. phalethI've said every byte counts but only when it comes to browser DOM abuse
  155. bluek
  156. phalethheh
  157. blueI mean, it's ok finding bugs that are unrelated, but they've been there for a while and no one complained
  158. blueI don't even know if anyone uses @primate/angular
  159. blueit's ok to fix a bug in it, but I wouldn't consider it a blocker for 0.43
  160. bluepity clanker doesn't understand that nuance
  161. phalethheh
  162. bluewhich is ok.. clanker doesn't know primate's userbase
  163. phalethclanker wants to clanker
  164. bluebut still, I asked it specifically to review the release, not to audit the project
  165. blueit has a tendency to overengineer/overthink stuff which is really annoying
  166. blueI feel like repopack's chat will be able to curb some of these tendencies by building-in good guidance
  167. bluebut clanker will clanker, as you say
  168. phalethat least it didn't start pushing rust into every hinge yet
  169. bluewell, rust is a no-go for repopack or any project I have a say in
  170. blueI will never accept code in a language you need a phd to understand
  171. bluethat's currently rusk and haskell for me
  172. bluerust*
  173. bluemy rule of thumb is that if I can't understand a piece of code, then I won't merge it
  174. blueI don't need to understand every detail, but I need to be able to map the code and understand what it does, and I can't do that with rust
  175. phalethyeah
  176. phalethsome languages are made for some people's amusements
  177. blueyup. rust is a purely ego-driven language
  178. blueit might satisfy some people's needs to show off.. but I can't accept it
  179. bluetoo pity zig turned into such a worthless dumpster fire
  180. blueI really liked it :(
  181. bluejust shows you sometimes good people with bad intentions can ruin good projects
  182. phalethzig as a lang is still fine, the zig standard lib got a bit weird
  183. phalethanyways, no need for a system lang for now, also there are alternatives anyway
  184. phalethI like the database optimizations in primate 0.43, that's actually the way to go
  185. bluediamond migrations?
  186. phalethwell that's nice too
  187. blueya
  188. bluethe repopack looks like a friggin' alien in the favicon, and I love it
  189. bluerepopack logo*
  190. phalethheh, after I scaled it horizontaly it's got a bit weird I think
  191. bluedo you want to rework it?
  192. blueit's got alien vibes right now
  193. blueif htat's intended, then it's ok
  194. phalethalien vibes are ok
  195. phalethit had them before anyway
  196. phalethit looked like a reptile in a mask in the favicon
  197. bluelol
  198. bluehttps://repopack.com/project/flog/tasks/109
  199. bluestick work has started
  200. bluephaleth: clanker review 749
  201. bluereviewed*
  202. blueit found some missing old logos
  203. bluewe should really centralise those assets
  204. phalethyeah, good review
  205. dreamrealnext BCN article on its way...
  206. bluedreamreal: `flog format` is coming
  207. bluelikely with a flog 0.2.z line
  208. dreamrealnoice!
  209. bot[ByteCode.News] That free beer has a brewer - https://bytecode.news/posts/2026/10/that-free-beer-has-a-brewer
  210. bluesweet, dreamreal
  211. dreamrealSomeone post that BCN post to HN please
  212. dreamrealbest if it's not blue this time because their filters watch for associations
  213. * nevet joined #primate
  214. * blue!~blue@user/blue changed the topic to: https://primate.run | This channel is logged: https://bytecode.news/logs/irc/libera/primate
  215. phalethdreamreal: https://news.ycombinator.com/item?id=50245121
  216. nevetHacker News
  217. dreamrealtodah!
  218. dreamrealsays "dead"
  219. dreamrealhrrrm
  220. phalethcannot even upvote?
  221. dreamrealit literally shows [dead] for me
  222. phalethoh, yeah, for me too
  223. phalethafter I logged out
  224. dreamrealNo idea why
  225. phalethyeah, well, hn does not like my account
  226. dreamrealhttps://news.ycombinator.com/item?id=50245457
  227. nevetThat free beer has a brewer | Hacker News
  228. bluedreamreal: I didn't peruse yet; node2shell might also merit mention
  229. bluethis, or rathe last week, has been a catastrophe for programming
  230. dreamrealOr something that's been LONG overdue, a butcher's bill that's been unpaid for far too long
  231. bluewell, php has always been a dumpster fire
  232. bluethis is nothing new
  233. dreamrealPHP isn't the point, though, and never has been
  234. dreamrealthis is a problem that PHP just ran into
  235. blueI beg to differ, mr dreamreal
  236. bluethis is very much a PHP point. good software, like openbsd, does not suffer from this
  237. * dreamreal thinks that's less true than blue might hope.. and the exploits are only EVIDENCE, not cause
  238. bluethere are superior and less superior models of programming. there *are* better programming languages, and more conscientious developers. all of this bears upon the product. the problem is NOT necessarily that PHP has one fulltime member. the problem is PHP is dumpster fire level garbage that should be retired ASAP
  239. dreamrealSure, but it's not ABOUT PHP
  240. dreamrealJava had the same kind of vulnerability
  241. bluethe place where your article and I differ, is that I generally do *not* believe that throwing money at problems fixes them. throwing money at stuff may, and often very poorly, alleviate symptoms. fixing problems is inextricably intertwined with uphill fighting many faults of the human nature
  242. blueand that is much, much harder than the article's promise
  243. blueif you give me a million dollars, that will *not* make primate better
  244. bluewhatever contributes to primate being good or bad is wholly connected with the culture around it
  245. bluethe people working on it, and with it
  246. dreamrealI don't think THROWING MONEY fixes problems
  247. dreamrealbut I think participating does
  248. bluethe reason I think Go is a great language, and I've only come to realise it recently, is because the c people wrote it, but also because it chose simplicity where others preferred complexity
  249. bluethose two things are completely unrelated to money
  250. bluethat is also my problem with rust: the "you-need-a-phd" complexity means people will produce conceptually bad software with it, and see those worthless rewrites of everything that crawls under the heavens, everywhere
  251. bluethat is a *bad* culture, no matter how much money the rust foundation has
  252. bluethe same criticism now goes to zig
  253. bluealthough it plays out differently there; the language is conceptually ok, the people are totally crazy
  254. * skillbot quit (Remote host closed the connection)
  255. * skillnews quit (Read error: Connection reset by peer)
  256. * skillbot joined #primate
  257. * skillnews joined #primate
  258. bluedreamreal: phaleth: lioloc: https://primate.run/blog/primate-043
  259. nevetPrimate — Primate 0.43: diamond migrations, deferred navigation and direct SQL
  260. blueprimate 0.43 is released
  261. bluethe 0.44 cycle has now opened
  262. phaleththe website works fine, well done
  263. phalethmobile score is better https://pagespeed.web.dev/analysis/https-primate-run/zmilz1ezks?form_factor=mobile
  264. liolocNICE
  265. liolocwill check it out
  266. bluenice phaleth
  267. blueya lioloc
  268. * phaleth quit (Quit: phaleth)
  269. lioloclots of changes, nice to see. Very nice. I'm off to bed, see you tomorrow!
  270. liolocCongrats on the release
  271. bluethx