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. * nevet joined #primate
  7. * 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
  8. * skillbot joined #primate
  9. phalethonly 20 seconds to build primate website, used to be about 45-50 seconds
  10. phalethflog really needs trust me bro script and windows builds
  11. bluehi phaleth
  12. blueyes, the primate website now doesn't need to build packages anymore, runs TS from source
  13. bluebtw phaleth, this is something that flog/dog are gonna solve generally for TS. no build step
  14. phalethhi blue
  15. bluehi
  16. phalethyou mean there is no call to flog build?
  17. blueexactly. no packages are being compiled to JS
  18. bluethe 20s are, according to my analysis, 14s docker nonsense, 6s primate build
  19. bluedocker stuff can be cached. the real redeploy time of primate website is 6s
  20. bluethere's also flog install involved, but that is really, really fast. faster than pnpm currently
  21. phalethbut in the Containerfile there is RUN flog run --workspace apps/website build
  22. blueyes. flog run jst runs scripts
  23. bluein that case, the script is `primate build`
  24. phalethah, so before the call was: RUN flog build --workspace apps/website
  25. blueyes. `flog build` builds TS -> JS, recursively
  26. bluewith dog around, `flog build` should be kinda obsolete I hope
  27. bluebtw dog's motto: One paw at a time. I came up with it and clanker approved
  28. phalethnah
  29. bluedreamreal found it hilarious for some reason
  30. phalethI just hope clanker is done with flog except for the issues I've mentioned
  31. blueflog is only getting started. https://repopack.com/project/flog/tasks/73
  32. bluewe're getting `flog format` and `flog lint`. but for that we need dog, so it'll arrive later, probably in 2027
  33. blueflog -> everything related to monorepo maintainance, dog -> just running stuff
  34. bluethe split bun never had, but should have had
  35. bluemaintenance*
  36. phalethbut for just running stuff it can use node
  37. blueyes but node is slow and stupid
  38. phalethor the go backed in runtime
  39. bluewell goja doesn't have jit, dog has jit (already)
  40. phalethnode runs on v8
  41. blueya, dog is gonna be faster than v8
  42. phalethomg :D
  43. phalethI thought flog is gonna be generally useful for people who can't be bothered with pnpm, but cannot fully migrate
  44. blueyes, well it's gonna replace npm/pnpm/yarn/nub/bun
  45. phalethanyway, JS engine is ton of wasted tokens cause of web standards
  46. bluethe web standards are actually the easiest part because clanker has ref
  47. phalethgoja is slow, too bad
  48. bluejit is the hard part, but dog is already getting fast there
  49. blueit already has 0 recompilations for some warm operations
  50. phalethok, so that's what is clanker doing
  51. bluethat doesn't mean a lot right now, but it's only going to get better
  52. blueand btw remember it's currently only optimised for amd64
  53. blueunlike v8, which has instructions for many, many platforms. I just need linux servers for now
  54. phalethis JIT compilation doable with golang?
  55. blueyes
  56. bluea friend of mine built wago (wago.sh) which is nearly the fastest wasi runtime, has jit
  57. bluebeats the v8 wasm runtime
  58. bluethat's currently the inspiration for dog, wago showed it's possible
  59. bluewago is top of many benchmarks and 2nd or 3rd (to jsc) in others
  60. phalethnah, clanker has no chance
  61. bluewago is 100% clankered
  62. phalethyeah, but wasm is simple
  63. blueyes
  64. blueI'm not saying it's gonna be as easy as wago
  65. bluebut it is possible
  66. phalethwhat is this error? flog: binary target is missing
  67. blueno idea
  68. phalethtrying to call: flog run --workspace apps/website build
  69. bluebinary target sounds like esbuild stuff?
  70. phalethah, so package.json and other things got update in primate repo
  71. phalethso I need to pull down that
  72. blueyes
  73. bluephaleth, you'll notice it's really really fast
  74. blueit's actually ridiculously fast
  75. phaleththat @primate/source is some magic
  76. phalethwell, at least pnpm repos can still use the previous: flog build --workspace apps/website
  77. blueit's just runtime keys. with dog it's all gonna be standardised into the "source" runtime key
  78. bluethe idea is, no need to compile TS, ever
  79. blueit's perfect
  80. bluebtw this reminds me, once primate 0.43 releases and flog.run can serve binaries, we gotta move rcompat and repopack to flog
  81. blueget rid of pnpm completely
  82. phalethyeah, also bun
  83. blueyes bun is dead anyway. sumner threw out all the team and is now playing with claude alone
  84. phalethnot sure what you mean by: compile TS
  85. blueTS -> JS
  86. phaleththere is still build/server.js right now
  87. blueyes but that's primate build, don't confuse it
  88. blueprimate build is about building the primate server with esbuild. it also strips TS but that's not a costly operation
  89. phalethso tsc is not called on invididual primate packages?
  90. phaleththe 6 ones that the primate website needs
  91. blueright now? no. it used to, when we had `flog build` in the containerfile
  92. phalethhmm
  93. bluetsc (which is tsgo since version 7) is fast, but still costs a lot of time
  94. bluethe reason we went down from 44s to 20s are mostly factoring out the TS build time
  95. blueand a few optimisations in flog
  96. phalethmagic
  97. bluewell it's hardly any magic. bun has supported running ts directly for a while. node has had it since v24 I think
  98. blueit's not really magic anymore
  99. phalethwell, if rcompat can be built that way then it's legit I guess
  100. bluebtw phaleth, one of hte reasons I'm building flog, is that node doesn't allow loading TS from node_modules
  101. phalethah, so that's why
  102. bluewhich is a very, very backward decision
  103. blueone of the reasons I'm building dog*, sorry
  104. bluebun can load TS from node_modules
  105. bluebut node refuses. it has the capability, it just refuses
  106. phalethyeah, bun is pushing node around, good
  107. phalethwell, what a shame for people paying for all those CI costs
  108. phalethso dog is gonna be the first TS only runtime? JS completely banned?
  109. phalethI mean it should be exactly that
  110. phalethcause there are lot of optimizations to be had from the typesystem
  111. blueidk it needs to ban JS completely
  112. blueidt*
  113. bluebut dog is gonna be focussed on avoiding that pesky build step
  114. blueand also you to publish source-packages to npm
  115. bluein fact, encourage you to do so
  116. blueif you publish both src and lib, and point to src with the "source" runtime key, you allow dog to run your packages directly from source
  117. bluethe problem of newer runtimes, like deno and bun, they always tried to reshape reality around their own egos
  118. blueI think it's important to play along with npm/node even if I don't like it
  119. * nevet joined #primate
  120. * 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
  121. phalethsounds good, but it'll take a lot of time
  122. bluetime is all we got
  123. blueof course if we had funding, this would be done yesterday
  124. dreamrealSo getting streampack set up for another network has been... instructive
  125. phalethwhat's the tech stack?
  126. dreamrealthe backend server is postgres+jvm, the front ends are variable: everything's OCI. The main front end on bytecode.news is primate; there's a spring+JS UI at pudl.bytecode.news
  127. dreamrealthe UIs are "bytecode.news" that use the streampack API, they're not "streampack"
  128. dreamrealThe idea was to build an ontology on the backend, not using *ontology tools* because nobody really thinks of ontologies very well, and the translation from ontology to usable API isn't worth it for the most part. But the API says "here's what you can do," and the UIs and services make those operations appropriate for their domains.
  129. dreamrealso there's an ontology, and an IRC service, and... well, there's nevet right there
  130. dreamrealI had thought of actually doing an ontology, blazeds or rdf, but... again, ontologies
  131. phalethah, it's that nevet thing that is still deployed on the VPS next to repopack
  132. dreamrealyeah, I don't know the state of that at all, baby steps!
  133. phalethontology makes you sound like a doctor
  134. dreamrealDoes it? To me it makes me sound like someone who works with knowledge graphs, because that's what ontologists do
  135. phalethheh, ok, I never heard that term
  136. dreamrealan ontology = a body of knowledge
  137. dreamrealdesigning one is utterly nontrivial
  138. phalethI remember nevet deployment with primate as frontend was rather smooth, only one problem with jdbc
  139. dreamrealnevet's factoids are an actual limited ontology; a factoid has info, urls, seealso, tags, maven coordinates, etc., as a very limited ontology
  140. dreamrealoh yeah, primate stores the tokens in a db as a limited scope
  141. dreamrealthe nextjs front end doesn't, and probably should, but I'm trying to sort of drop that one as unmaintained except for security issues: if someone wants to write a GOOD nextjs front end I'll be happy to deploy it but it's not MINE and I don't like that UI
  142. bluenextjs and good are not typically words that appear together in one sentence
  143. phalethhmm, I think nextjs or in other words react on backend is wrong, should be all TS at this point in time
  144. dreamrealyep, I suppose it's doable but not by me and I have no interest in it
  145. dreamrealI WOULD like to try an HTMX UI, though, it'd be a lot like the pudl implementation
  146. dreamrealcould probably use a lot of the same server code
  147. bluedreamreal: https://primate.run/docs/frontend/htmx
  148. nevetPrimate — HTMX
  149. dreamrealheh
  150. dreamrealgood point :D
  151. dreamrealSee discord, BTW: I'm working on an article about rcompat
  152. blueprimate is kinda awesome: you could have both marko *and* htmx, in ONE app, in two disjunctive bundles
  153. bluelooking
  154. dreamrealIt feels like rcompat mostly needs a good thorough documentation workover
  155. phalethhtmx tends to go well with any view/template layer, but the framework has to be able to support partial html responses
  156. phalethbut might as well not use any framework and put all markup in TS
  157. phalethI mean template literals are a thing, not much support from IDEs, but clanker does not care
  158. bluedreamreal: you're also welcome to submit patches to rcompat (docs), if you want. otherwise I'll fix those things myself as soon as I can
  159. phalethnew rcompat favicon is very original
  160. bluephaleth: primate uses partial html responses on every htmx request, automatically
  161. phaleththat means dreamreal does not have to pester clanker with TS
  162. phalethI mean template literals
  163. blueya
  164. phalethactually, I gotta check if I pushed the favicon
  165. phalethrepopack site thinks favicon is binary
  166. dreamreal0ver.url=https://0ver.org/
  167. nevetZeroVer: 0-based Versioning — zer0ver
  168. dreamreal0ver
  169. dreamreal0ver.url=https://0ver.org/
  170. dreamrealFactoidUpdatedEvent(selector=0ver)
  171. nevetok, dreamreal: updated 0ver.
  172. dreamreal0ver=<reply>"0ver" refers to a versioning scheme that uses a significant version of "0," forever, used by *many* popular projects across many ecosystems.
  173. dreamrealFactoidUpdatedEvent(selector=0ver)
  174. nevetok, dreamreal: updated 0ver.
  175. dreamreal0ver.seealso=semver
  176. dreamrealFactoidUpdatedEvent(selector=0ver)
  177. nevetok, dreamreal: updated 0ver.
  178. dreamrealsemver.url=https://semver.org/
  179. dreamrealFactoidUpdatedEvent(selector=semver)
  180. nevetok, dreamreal: updated semver.
  181. dreamrealsemver=<reply>Semver is "semantic versioning," a version scheme that uses major, minor, and patch version numbers, indicating the severity of change from *prior* numbers.
  182. dreamrealFactoidUpdatedEvent(selector=semver)
  183. nevetok, dreamreal: updated semver.
  184. dreamrealsemver.seealso=0ver
  185. dreamrealFactoidUpdatedEvent(selector=semver)
  186. nevetok, dreamreal: updated semver.
  187. * phaleth quit (Quit: phaleth)
  188. bluedreamreal: https://rcompat.repopack.app got a logo... courtesy of phaleth
  189. nevetrcompat — JavaScript standard library
  190. dreamrealI HATE IT! Let me go look at it
  191. bluehow can you hate it if you didn't look at it >_>
  192. dreamrealno favicon yet, is it the flowchart-looking thing?
  193. dreamrealI was being funny
  194. dreamrealI am hilarious, you know, everyone tells me that after I pay them to say it
  195. blueyes, no favicon yet, because I was lazy
  196. dreamrealNo worries, one bit at a time
  197. blueweird, there is a favicon
  198. blueit's just not getting loaded
  199. blueit's not explicitly in the code, btw. it relies on browsers trying for it automatically
  200. bluelike primate.run does
  201. bluebut I think the favicon may be botched, will need to ask phaleth
  202. bluedreamreal: https://rcompat.repopack.app/
  203. nevetrcompat — JavaScript standard library
  204. bluefavicon works
  205. blueI do have some other fixes
  206. dreamrealwoot
  207. bluewhat woot
  208. dreamrealfixes + favicon
  209. blueya
  210. bluehttps://bytecode.news/posts/2026/10/emergent-design-outside-the-codebase
  211. bluethis is an incredible article, but I recommend listening to it rather than reading
  212. * dreamreal shudders
  213. dreamrealthe narrator's a goofball and is not good at this
  214. dreamrealThe author also needs to start putting "hey, share this if you think it's worth sharing" somewhere
  215. blueoh come on, don't go yt on us
  216. dreamrealWell, here's the thing: people are not sharing this
  217. dreamrealthey're leaving it up to me and that's not going to be sufficient to build critical mass, it's just the way it is
  218. blueI mean, I *get* the sentiment. people don't share unless you ask them to. I might be an exception, but still, the "subscribe, hit the bell icon" thing is what annoys me the most in yt videos
  219. dreamrealso I can do it all myself OR I can ask people to step up and help
  220. dreamrealI might ask and then nobody thinks it's worth sharing, that's entirely a possible outcome
  221. bluewell this is *good* content, and it's essentially for free, I don't see a reason not to share it
  222. dreamrealbecause sharing is an action and I don't have any calls for action, so people... don't
  223. blueand btw it's good, as we already established, despite the primary sources often being trrible
  224. dreamrealso the exposure is mostly limited to MY networks and I don't enjoy networking well
  225. dreamrealthere's some but not a lot
  226. bluebtw, you can add bytecode.news here as a feed too, I'd say
  227. dreamrealand I can't see myself doing the whole "click 'like' and subscribe!' thing
  228. blueit might not always or often be primate relevant, but it's almost always worth reading
  229. dreamrealrss feed subscribe https://bytecode.news/
  230. dreamrealfeed subscribe https://bytecode.news/
  231. nevetSubscribed to "ByteCode.News"
  232. dreamrealgrr
  233. dreamrealthere
  234. bluenice
  235. bluefeed list
  236. nevetjustine.lol - https://justine.lol/rss.xml Next.js Blog - https://nextjs.org/feed.xml Read the Tea Leaves - https://nolanlawson.com/feed/ The JetBrains Blog - https://blog.jetbrains.com/feed/ W3C - Blog - https://www.w3.org/blog/feed Terminal Trove - https://terminaltrove.com/blog.xml Distant Province - https://distantprovince.substack.com/feed That Privacy Guy! Blog - https://www.thatprivacyguy.com/blog/feed.xml James Shore - https://www.jamesshore.com/v2/feed Entropic Thoughts - https://entropicthoughts.com/feed Feed - https://hollycummins.com/rss.xml Eignex - https://eignex.com/feed.xml Nate Meyvis - https://www.natemeyvis.com/feed/ FREEZE64.COM - https://freeze64.com/feed/ purplesyringa's blog - https://purplesyringa.moe/blog/feed.rss Angular Blog - Medium - https://blog.angular.dev/feed Typotheque - https://www.typotheque.com/rss Ziglang.org News - https://ziglang.org/news/index.xml Martin Fowler - https://martinfowler.com/feed.atom bun.com - https://bun.com/rss.xml Svelte blog - https://svelte.dev/blog/rss.xml The Astro Blog - https://astro.build/rss.xml Improbable Research - https://improbable.com/feed/ Diátaxis - https://diataxis.fr/atom.xml Terence Eden’s Blog - https://shkspr.mobi/blog/feed/atom Ember.js Blog - https://blog.emberjs.com/rss.xml Random Notes and Cheat Sheets - https://www.kodewerk.com/feed.xml Deciphering Glyph - https://blog.glyph.im/feeds/all.atom.xml Docker - https://www.docker.com/feed/ Node.js Blog - https://nodejs.org/en/feed/blog.xml Simon Willison's Weblog - https://simonwillison.net/atom/everything/ Chicory Blog - https://chicory.dev/blog/rss.xml tRPC Blog - https://trpc.io/blog/rss.xml Primate Blog - https://primate.run/blog.rss OpenTelemetry - https://opentelemetry.io/index.xml Blog posts | RSS Feed - https://www.cockroachlabs.com/rss.xml Rust Blog - https://blog.rust-lang.org/feed.xml ByteCode.News - https://bytecode.news/feed.xml Nushell - https://www.nushell.sh/atom.xml Vanish is... - https://vanish.is/feed.xml Paged Out! Magazine - https://pagedout.institute/rss.xml JoshLong.com - https://api.joshlong.com/feed.xml Nature Reviews Computing - https://www.nature.com/nrcomput.rss David M. Lloyd - https://word-bits.flurg.com/rss.xml Biome | Blog - https://biomejs.dev/blog/rss.xml Deno - https://deno.com/feed Spring - https://spring.io/blog.atom OpenAPI Initiative - https://www.openapis.org/feed TypeScript - https://devblogs.microsoft.com/typescript/feed/ Enigmastation.com - https://enigmastation.com/feed.xml Open Liberty - https://openliberty.io/feed.xml MDN Blog - https://developer.mozilla.org/en-US/blog/rss.xml Fernando Borretti - https://borretti.me/feed.xml The Nuxt Blog - https://nuxt.com/blog/rss.xml The Vue Point - https://blog.vuejs.org/feed.rss cekrem.github.io - https://cekrem.github.io/index.xml Vlad Mihalcea - https://vladmihalcea.com/feed/ Piotr's TechBlog - https://piotrminkowski.com/feed/ Apache Fory™ Blog - https://fory.apache.org/blog/rss.xml Vercel News - https://vercel.com/atom Poimandres - https://pmnd.rs/feed.xml Apache NetBeans - https://netbeans.apache.org/blogs/atom React Blog - https://react.dev/feed.xml Christian Rackerseder | Blog - https://www.echooff.dev/rss.xml thoughts from the red planet - http://feeds.feedburner.com/ThoughtsFromTheRedPlanet WebKit - https://webkit.org/feed
  237. blueah, it's all feeds
  238. dreamrealgah, that's a horrible command
  239. bluenot just this channel's
  240. blueI forgot :/
  241. dreamrealyeah, I need to fix that
  242. dreamrealfeed subscribed
  243. dreamreala whole lot of commands I forgot how to use
  244. dreamrealfeed
  245. bluenevet should print help I think
  246. bluefeed
  247. dreamrealyeah, the IRC side has a lot of trouble with help because it's so verbose
  248. dreamrealfeed subscriptions
  249. nevetbun.com - https://bun.com/rss.xml Node.js Blog - https://nodejs.org/en/feed/blog.xml Primate Blog - https://primate.run/blog.rss ByteCode.News - https://bytecode.news/feed.xml Deno - https://deno.com/feed
  250. dreamrealthere
  251. bluenice
  252. * blue!~blue@user/blue changed the topic to: https://primate.run | This channel is logged: https://bytecode.news/logs/irc/libera/primate
  253. blue"The broad, general, forward-looking interface built for unknown future uses is exactly the speculative abstraction YAGNI forbids"
  254. bluevery good
  255. bluewhat's funny about this article dreamreal is that it describes rcompat almost to t
  256. blue"In both cases the design arrives when something uses it, and not before."
  257. blueit was always designed around my needs in primate
  258. dreamrealyes, emergent design isn't new
  259. blueto a t*
  260. dreamrealbain's book was mid-2000s and wasn't new THEN
  261. bluemaybe I should get it
  262. bluebtw: why don't you do affiliate links?
  263. blueI think you link to amazon relatively frequently
  264. blueif I buy the book anyway, I don't see any harm in you getting something out of it. it's a win-win situation, since amazon has enough to spare
  265. dreamrealI am allergic to such things :/
  266. dreamrealDon't want to feel like I'm trying to sell people on things, including thinking
  267. blueyeah I get it
  268. bluebut at some point it would be nice to have a business model around BCN.. maybe subscriptions
  269. dreamrealyeah, I know
  270. dreamrealI just hate the ideas I've had around it
  271. blueya
  272. bluehttps://news.ycombinator.com/item?id=50132798
  273. nevetEmergent Design, Outside the Codebase | Hacker News
  274. blueeveryone pls upvote
  275. * skillnews quit (Remote host closed the connection)
  276. * skillbot quit (Remote host closed the connection)
  277. * skillbot joined #primate
  278. * skillnews joined #primate
  279. bluedreamreal: https://repopack.com/project/flog/tasks/74
  280. bluea way forward for dog/flog
  281. bluehttps://repopack.com/project/rcompat/tasks/46
  282. bluesoon coming
  283. bluedog is screaming along...
  284. bluecurrently working on a measured array-index speed paw
  285. bluedreamreal: ^
  286. bluewe also need `flog test --coverage`
  287. * jreicher quit (Quit: In transit)
  288. * jreicher joined #primate