ByteCode.NewsSubmit
Use quotes for an exact word.

Subscribe

RSSPodcast
Log in

Community

Chat Logs

Sunday, October 11, 2026 (America/New_York)

  1. jreicherblue: nah, I don't have privacy concerns at all. It's more a matter of time and respect. I don't want to disrespect your work by giving you the impression I'll spend more time looking at it than I actually can. But part of that is deciding how much time I have, which is a constant challenge for me.
  2. jreicherhangman
  3. nevetHangman: _ _ _ _ _ _ _ _ (6/6 lives) -- Use 'hangman <letter>' to guess, 'hangman solve <word>' to solve.
  4. jreicherhangman e
  5. nevetHangman: _ _ _ _ _ e _ _ (6/6 lives, guessed: e) -- 'e' is in the word!
  6. jreicherhangman t
  7. nevetHangman: _ _ t _ _ e _ _ (6/6 lives, guessed: e, t) -- 't' is in the word!
  8. jreicherhangman n
  9. nevetHangman: _ _ t _ _ e _ _ (5/6 lives, guessed: e, n, t) -- No 'n'. 5 lives left.
  10. jreicherhangman a
  11. nevetHangman: _ _ t _ _ e _ _ (4/6 lives, guessed: a, e, n, t) -- No 'a'. 4 lives left.
  12. jreicherhangman u
  13. nevetHangman: _ u t _ _ e _ _ (4/6 lives, guessed: a, e, n, t, u) -- 'u' is in the word!
  14. jreicherhangman y
  15. nevetHangman: _ u t _ _ e _ _ (3/6 lives, guessed: a, e, n, t, u, y) -- No 'y'. 3 lives left.
  16. jreicherhangman s
  17. nevetHangman: _ u t _ _ e _ _ (2/6 lives, guessed: a, e, n, s, t, u, y) -- No 's'. 2 lives left.
  18. phalethjreicher: everybody in this channel is exactly in the same situation, that's why people are clankering heavily these days, it does not take long to try repopack website and also the cli. If you don't feel like contributing to repopack specifically you can always leave feedback in the pop up window on the website
  19. phalethand by contributing I mean just writing tasks for clanker to do
  20. jreicheri
  21. jreicherhangman i
  22. nevetHangman: _ u t _ i e _ _ (2/6 lives, guessed: a, e, i, n, s, t, u, y) -- 'i' is in the word!
  23. jreicherWow, this is hard
  24. jreicherOh
  25. jreicherhangman o
  26. nevetHangman: o u t _ i e _ _ (2/6 lives, guessed: a, e, i, n, o, s, t, u, y) -- 'o' is in the word!
  27. jreicherhangman f
  28. nevetHangman: o u t f i e _ _ (2/6 lives, guessed: a, e, f, i, n, o, s, t, u, y) -- 'f' is in the word!
  29. jreicherhangman l
  30. nevetHangman: o u t f i e l _ (2/6 lives, guessed: a, e, f, i, l, n, o, s, t, u, y) -- 'l' is in the word!
  31. jreicherhangman d
  32. nevetjreicher got it! The word was 'outfield'. Use 'hangman' to play again.
  33. bluephaleth: true, also hi
  34. phalethhi blue
  35. blue570 will soon be fixed
  36. bluephaleth: https://repopack.com/project/repopack/jobs/1
  37. bluedid you see job runs are now paginated
  38. bluebut 20 is too much. I'll reduce it to 10
  39. blueugh, too much open stuff :)
  40. blueI'm excited about 0.43
  41. bluefinally, full pema docs
  42. bluebeen long time in the making
  43. bluehttps://repopack.com/project/primate/tasks/194
  44. blue0.43 is already growing way beyond what I'd intended
  45. bluebut it's all good, that's what you have releases for
  46. blueI'm not going to lie, I like the npm 0.* model too much
  47. bluedreamrea1: I should really submit an article to bytecode.news, "Major 1 is overrated"
  48. bluedreamrea1: fix your nick
  49. dreamrealwhat would "major 1 is overrated" be about? (remember, you can build an article from IRC conversations with nevet.)
  50. bluedreamreal: it's an idea I've expressed time an again. that majors, particularly major 1, are *mostly* pr, but they limit you in breaking properly and moving forward. In a way, this is the linux development model: it *has* no stable version that carries backcompat for years
  51. dreamrealSure, but this is known
  52. bluefor primate, I'm perfectly comfortable in staying on 0.* for quasi-forever, unless someone can convince me elsewise
  53. blueI do not know what I'll gain by publishing a 1.*
  54. blueother than claiming some sort of stability / ripeness to which I don't think I as the creator have a real claim to
  55. dreamrealWell, fair. But psychologically, a 0.x release doesn't feel like it's "baked." It's a promise that says "this works" that 0.x does not make, even though 0.x can certainly work just as well.
  56. blueyes; and my point is that a "show not tell" situation like esbuild's, is far superior to a bun 1.* that is broken
  57. dreamrealbut users aren't going to LOOK at the "show don't tell" version. Their first gate is the release version.
  58. dreamrealNote: am not telling you "do not write this."
  59. bluethat's totally fine, I don't need to write it, we can steelman it first here
  60. blueif this is a triviality, then you spare me time by showing iti s
  61. dreamrealweather 27596
  62. nevetThe weather for 27596, Franklin County, North Carolina, United States is 23.43C (74.2F), and is described as "overcast clouds"
  63. bluebut I still maintain that major 1 is a derivative form of snake oil
  64. dreamrealhrmph, there's apparently a tornado warning here, AWS!
  65. blueit's a trust me bro situation
  66. bluelol
  67. dreamrealsure, it's easy to say "hrm, we want users, let's brand it 1.0 and goooooo and we'll fix all the user stuff as soon as they whinge"
  68. bluedreamreal: kudos on setting CELCIUS as the standard there and not freedom units
  69. blueyes
  70. bluebut you do not lay claim to major 1 being more than a trust-me-bro, yes?
  71. phalethhttps://0ver.org/
  72. nevetZeroVer: 0-based Versioning — zer0ver
  73. dreamrealI'm not making a claim anyway. Users are valuable; the things that help users decide are valuable by extension; some users value 1.x and others don't care, and both sets of users have reasons.
  74. dreamrealwindows 0.8 would NEVER have taken off, even if it were byte-for-byte equivalent to 1.0.
  75. dreamrealhmm, I'm now thinking 0ver would have been a net positive for windows :D
  76. bluephaleth: DAMN, there's already a concept for this
  77. blueso I don't need to write an article after all
  78. dreamrealWell, it's worth churning the stream for, if you're passionate about it
  79. dreamrealthe fact that it's significant to YOU is significant, after all. Consider the idea on 0ver as being, well, 1.x
  80. bluehm
  81. blue"Unlike other versioning schemes like Semantic Versioning and Calendar Versioning, ZeroVer (AKA 0ver) is simple: Your software's major version should never exceed the first and most important number in computing: zero."
  82. blueI must say I disagree with this. this is NOT the extend of what *I* am thinking
  83. dreamrealSee? You could write 2.x!
  84. bluelol
  85. * dreamreal is definitely amused by this
  86. blueyou're not taking me seriously
  87. dreamrealNo, I definitely am - the humor is well-intentioned
  88. blueit's just in a 0.x.y scheme, x+1 should indicate breakage, whilst y+1 shouldn't
  89. bluethe major is USELESS
  90. bluein fact it's an anti-feature: it communicates a false sense of stability
  91. dreamrealeh, not really: semver says that patches don't affect behavior while minors do and majors are incompatibility
  92. blueI didn't say semver, dreamreal
  93. blueI said what my ideal is. incidentally, this ideal is exactly how npm interprets 0.* software
  94. dreamrealand I'd say 1.x says "this behavior is contractually there, we guarantee that the 1.x spec is valid," and .x patches are "we're fixing the contractual fulfillment" and .y says "you probably won't notice this but we will"
  95. dreamrealyes, npm is clearly what we should be emulating
  96. bluenpm will auto pull-in a y-change on 0.x.y, but it won't be pulling in an x change
  97. blueoh gott, more deprecating humour!
  98. blueI can see you are amusing yourself well
  99. bluegood good
  100. dreamrealwhere?
  101. blue16:44 < dreamreal> yes, npm is clearly what we should be emulating
  102. blueif this isn't tongue-in-check, I'm a hare
  103. bluecheek*
  104. dreamrealpffft, that's humor at npm's expense, I'm not being self-deprecating at all
  105. dreamrealnpm is just software, if you like it, great, but it's just a set of decisions
  106. blueI don't care for npm one least bit
  107. dreamrealI'm working on an article myself, trying to figure out if I should bother putting it out monday which is a federal holiday here
  108. dreamrealAND working on the annotation mechanism for BCN
  109. blueya
  110. dreamreal```This is why authors are often their own terrible reviewers: an author *knows* what they meant and they naturally elide errors themselves, and they don't even *see* their own errers. A good copy editor who's able to be brutally honest while interested in the success of a project is worth their own weight in gold. Software authors have it even worse, since most of us aren't authors *at all* and
  111. dreamrealwriting is not our strength or interest in the first place.```
  112. dreamrealand no, I'm not leaving "errers" in even though I worked HARD to type it - dang that was not easy - because it's just ... too easy for a reader to go "hey, you made an error" without realizing that I was illustrating a point.
  113. blueyes
  114. blueWB phaleth
  115. phalethheh
  116. bluephaleth: if we move to flog as part of 0.43, I could also close primate#186
  117. phalethyeah
  118. bluephaleth: https://primate-master.repopack.app/docs/pema
  119. phalethpema
  120. * phaleth is drinking lemonade atm
  121. bluelemonade is great
  122. bluephaleth: primate's web-master app now automatically redeploys on master advances
  123. bluethis is amaze sauce for many different reasons; but above all, we now officially eclipse what we wanted to get out of fly
  124. blueand it takes roughly ~10s to redeploy, as opposed to the >30s on fly
  125. bluephaleth: https://primate-master.repopack.app/docs/pema/schemas
  126. nevetPrimate — Schemas
  127. bluenow works on mobile well, too
  128. bluehttps://primate-master.repopack.app/blog/primate-043
  129. nevetPrimate — Primate 0.43: diamond migrations, deferred navigation and direct SQL
  130. phalethhuh, the blogpost is merged by there are XXXs in it still
  131. blueyes, merged into master
  132. blueit's not online yet on primate.run, nor is 0.43 released
  133. phalethyeah, I can see that
  134. blueman will I be happy getting rid of nub/pnpm
  135. bluedreamreal: https://flog.run
  136. nevetflog — predictable JavaScript package management
  137. jreicherzero-versioning reminds me of https://en.wikipedia.org/wiki/Software_versioning#TeX
  138. nevetSoftware versioning - Wikipedia
  139. jreicher(note that's a link to a specific section)
  140. dreamrealblue: nevet now has CVE support. :D