ByteCode.NewsSubmit
Use quotes for an exact word.

Subscribe

RSSPodcast
Log in

Chat Logs

  1. liolocmorning !
  2. liolocIs there any way to undo migrations?
  3. bluelioloc: morning, hello
  4. bluelioloc: no, migrations are forwarding breaking by design
  5. blueforward breaking*
  6. bluethe way to deal with it is create another migration that fixes the problem
  7. bluesome orms/db systems do implement reversible migrations, but it's a can of worms: destructible migrations cannot be reserved, and non-destructible are easy to forward-fix. so reverting migrations doesn't gain you much
  8. bluereversed*
  9. liolocah i see
  10. blueso the question is, what is your use case here?
  11. blueit's better to accept migrations as historic evidence and forward-fix than messing with them
  12. liolocif we had a database that operated kind of like git does, with "commits" then it would probably be an easy fix, but there's probably good reasons why that doesn't exist
  13. liolocMy use case was a personal project where I added a migration but decided to revert those changes, nothing crazy
  14. liolocI don't mind adding another migration to revert
  15. blueyes, if you had a database that operated like git, it would be easy to 'revert' migrations. however, you have to remember that databases do not operate in a way; their write operations aren't all gated by acceptance, like commits here, and any user performing an action post-migration already has the expectation that that action is persisted, rather than lost when you 'revert' to the old stage
  16. bluedatabases do not operate in the same way*
  17. liolocah ok
  18. bluegit's graph is visible all the way, databases are generally not ledgers... and even so, the complexity of reconciliating a back-migration with already-persisted changes is too high, I'd say even impossible
  19. bluelioloc: primate 0.44 released, btw
  20. blueit's not a particularly big release like 0.45, but I wanted to `primate update` out already
  21. bluelike 0.43*
  22. blueI'm also adding more features to flog. `flog format` and `flog lint` will hopefully soon arrive, as a fast replacement to eslint. then we'll have `flog test` and `flog test --cover`
  23. bluefinally, `flog typecheck` is planned. it will ts-check your project, but only against modern ts syntax. so erasable syntax only, no namespaces, etc.
  24. bluegenerally speaking this will be replacing eslint + tsc + test runners (like proby)
  25. blueso flog will do everything except run your code
  26. bluehttps://primate-master.repopack.app/docs/testing
  27. blueexciting
  28. blue(upcoming in 0.45)
  29. bluedreamreal: ^^^ that might be interesting for your tests, as it doesn't require starting a primate app
  30. blueprimate is getting a visual website refresh in 0.45, https://pewtxngij-task-295.repopack.app/
  31. nevetPrimate — The Universal Web Framework
  32. nevet[ByteCode.News] CheerpJ 5 launches: Java 21 and Java 25 in the browser - https://bytecode.news/posts/2026/10/cheerpj-5-launches-java-21-and-java-25-in-the-browser
  33. liolochey blue, 0.44 is broken with a simple react app, created task https://repopack.com/project/primate/tasks/302 for it
  34. lioloci couldn't access the visual website refresh, sasy 404 page not found
  35. bluehi lioloc, looking at it
  36. bluelioloc: @primate/core@0.13.1 is published
  37. liolocnice thanks
  38. liolocconfirmed it works
  39. liolocthanks
  40. blueno worries, fixing on master + adding tests now
  41. bluefeed list
  42. nevetjustine.lol - https://justine.lol/rss.xml Node.js Blog - https://nodejs.org/en/feed/blog.xml Obsidian Blog - https://obsidian.md/feed.xml W3C - Blog - https://www.w3.org/blog/feed Jan van den Berg - https://j11g.com/feed WebAssembly News - https://webassembly.org/feed.xml James Shore - https://www.jamesshore.com/v2/feed Distant Province - https://distantprovince.substack.com/feed Ember.js Blog - https://blog.emberjs.com/rss.xml The Astro Blog - https://astro.build/rss.xml Entropic Thoughts - https://entropicthoughts.com/feed Loris Cro's Personal Website - https://kristoff.it/index.xml Flog releases - https://flog.run/changelog.rss zer0ver - https://0ver.org/atom.xml Simon Willison's Weblog - https://simonwillison.net/atom/everything/ Andrew Kelley - https://andrewkelley.me/rss.xml danluu.com - https://danluu.com/atom.xml Primate Blog - https://primate.run/blog.rss Diátaxis - https://diataxis.fr/atom.xml The JetBrains Blog - https://blog.jetbrains.com/feed/ purplesyringa's blog - https://purplesyringa.moe/blog/feed.rss Rust Blog - https://blog.rust-lang.org/feed.xml Read the Tea Leaves - https://nolanlawson.com/feed/ Adoptium Blog - https://adoptium.net/rss.xml FREEZE64.COM - https://freeze64.com/feed/ Terence Eden’s Blog - https://shkspr.mobi/blog/feed/atom Docker - https://www.docker.com/feed/ Feed - https://hollycummins.com/rss.xml bun.com - https://bun.com/rss.xml Alan Williamson - https://alan.is/feed/ Ziglang.org News - https://ziglang.org/news/index.xml Svelte blog - https://svelte.dev/blog/rss.xml CheerpJ - https://cheerpj.com/feed.xml Chicory Blog - https://chicory.dev/blog/rss.xml yosh's blog - https://www.unix.dog/~yosh/blog/feed.atom tRPC Blog - https://trpc.io/blog/rss.xml Eignex - https://eignex.com/feed.xml Typotheque - https://www.typotheque.com/rss Improbable Research - https://improbable.com/feed/ Alberto Denia's Writing - https://www.albertodenia.com/writing/feed Deciphering Glyph - https://blog.glyph.im/feeds/all.atom.xml cekrem.github.io - https://cekrem.github.io/index.xml Apache NetBeans - https://netbeans.apache.org/blogs/atom The PHP Foundation - https://thephp.foundation/atom.xml That Privacy Guy! Blog - https://www.thatprivacyguy.com/blog/feed.xml Help Net Security - https://www.helpnetsecurity.com/feed/ maevyn.codes - https://maevyn.codes/rss.xml David M. Lloyd - https://word-bits.flurg.com/rss.xml TypeScript - https://devblogs.microsoft.com/typescript/feed/ thoughts from the red planet - http://feeds.feedburner.com/ThoughtsFromTheRedPlanet Piotr's TechBlog - https://piotrminkowski.com/feed/ Vlad Mihalcea - https://vladmihalcea.com/feed/ Deno - https://deno.com/feed WebKit - https://webkit.org/feed Eclipse IDE and platform on eclipseide.org - https://eclipseide.org/index.xml Fernando Borretti - https://borretti.me/feed.xml Enigmastation.com - https://enigmastation.com/feed.xml JoshLong.com - https://api.joshlong.com/feed.xml OpenTelemetry - https://opentelemetry.io/index.xml MDN Blog - https://developer.mozilla.org/en-US/blog/rss.xml Random Notes and Cheat Sheets - https://www.kodewerk.com/feed.xml The Nuxt Blog - https://nuxt.com/blog/rss.xml Spring - https://spring.io/blog.atom Vercel News - https://vercel.com/atom Christian Rackerseder | Blog - https://www.echooff.dev/rss.xml Nushell - https://www.nushell.sh/atom.xml Angular Blog - Medium - https://blog.angular.dev/feed Paged Out! Magazine - https://pagedout.institute/rss.xml Vanish is... - https://vanish.is/feed.xml Open Liberty - https://openliberty.io/feed.xml Apache Fory™ Blog - https://fory.apache.org/blog/rss.xml Poimandres - https://pmnd.rs/feed.xml The Vue Point - https://blog.vuejs.org/feed.rss Next.js Blog - https://nextjs.org/feed.xml Biome | Blog - https://biomejs.dev/blog/rss.xml Mystic’s Substack - https://www.wecodefire.com/feed Nate Meyvis - https://www.natemeyvis.com/feed/ マリウス - https://xn--gckvb8fzb.com/index.xml Nature Reviews Computing - https://www.nature.com/nrcomput.rss Blog posts | RSS Feed - https://www.cockroachlabs.com/rss.xml OpenAPI Initiative - https://www.openapis.org/feed The Go Blog - https://go.dev/blog/feed.atom React Blog - https://react.dev/feed.xml ByteCode.News - https://bytecode.news/feed.xml Codeberg News - https://blog.codeberg.org/feeds/all.atom.xml DuckDB - https://duckdb.org/feed.xml Martin Fowler - https://martinfowler.com/feed.atom Terminal Trove - https://terminaltrove.com/blog.xml GitHub hosting -> Codeberg - https://discuss.cachyos.org/t/github-hosting-codeberg/33963.rss
  43. bluedreamreal: ^ this really should show the feeds for this channel, showing all feeds is... not useful
  44. bluearticles
  45. bluearticles blue
  46. bluenothing is working :(
  47. blue`!articles` without [user], should show my articles, I think
  48. bluewith user, show should user's articles
  49. blueshould show*
  50. bluedreamreal: and coolest feature of all: link my irc user to repopack user, link channel to project, then be able to do `+task [title] [text]`
  51. bluethis would allow quick prototyping of ideas
  52. bluehi phaleth
  53. bluehttps://primate-master.repopack.app/
  54. nevetPrimate — The Universal Web Framework
  55. bluenew website coming in 0.45
  56. phalethhi blue
  57. phalethnew primate website?
  58. blueyes
  59. bluealso testing, ORM translactions, changelog for primate, and API docs
  60. bluetesting is already done: https://primate-master.repopack.app/docs/testing
  61. blueprimate already uses it internally for its frontend tests, this bypasses starting a real server and occupying a port, pretty cool stuff
  62. phalethcolors are a bit different, margins are a bit off in some places but many that's fine
  63. blueya
  64. phalethmaybe that's fine*
  65. bluealso flog is gaining many new commands, `flog check types`, `flog check imports`, `flog checks deps`
  66. blueso it'll replace many tools, eslint/prettier/biome, tsc, npm, knip, and many more. anything aside from the runtime itself, essentially
  67. bluethis is the bun thing I think systemfault was complaining about. flog is basically bun but without the runtime, so it's only a package manager
  68. bluethis is the one thing flog will never be, a runtime. because it's in go. but that's fine, I don't want it to be a runtime
  69. bluedog will carry that torch
  70. phalethshould be separate yeah, make the container too big
  71. bluewell flog right now, on master, is 4.5mb
  72. bluethat's not very big at all. bun is like 90mb
  73. phaleth9.8M on my disk
  74. blueflog-0.0.0-dev.1540bd0af077-linux-amd64.tar.gz 4.5MB
  75. blueI guess there's a lot of text inside? binaries are supposed to be compressed already I thought...
  76. blueanyway I'll see if I can make it smaller
  77. phalethunarchived
  78. blueya
  79. bluewell 9.8M is still ok. but I'll optimise once we get all the features
  80. blueI'm just trying to get rid of all this unreliable dumpster fire tooling that never works for me properly
  81. bluelike I install knip, then it shows a thousand errors where about 99.99% of them are false positive because it doesn't understand node private imports (#)
  82. bluedoes anyone actually test/use those tools?
  83. phalethno, people still use webpack
  84. blueomg webpack
  85. phalethit's always like yeah, dog shit slow, but it's battle tested and it works
  86. bluebattle tested my butt
  87. bluebut tbh, I delimit flog to *my* use cases. like for TS type checks, it's only modern syntax because I don't care about enums or interfaces or all that old garbage
  88. blueso it's just erasable syntax and no interface. it's anyway what the TS more or less recommends today
  89. bluesorry, no namespaces*
  90. blueinterfaces will be fully supported
  91. bluenamespaces was a module-like attempt of TS that predated proper ESM modules, I believe. so anyway you shouldn't be doing it anymore
  92. bluealso no type decorators and so on
  93. phalethI like TS enums
  94. bluethey don't degrade well at all
  95. phaleththey allow string values
  96. phalethlike Java enums, but Java enums look weird
  97. blueyou should just do `const ENUM = { 1: "HI", 2: "BYE"};`
  98. bluethat's as good an enum as you'll get
  99. phalethnamespaces in TS are a failure
  100. blueyes
  101. bluethat's why `flog check types` won't support htem
  102. blueso obviously if you need to check the world, you'd be still using tsc. but for modern projects, flog will be just as good
  103. bluethese are primate's devdeps right?
  104. blueright now:
  105. blue "@rcompat/test": "^0.22.0",
  106. blue "@types/node": "^26.6.4",
  107. blue "@typescript/native": "npm:typescript@^7.0.2",
  108. blue "apekit": "0.0.58",
  109. blue "eslint": "^10.12.0",
  110. blue "proby": "^0.27.0",
  111. blue "typescript": "npm:@typescript/typescript6@^6.0.2"
  112. blueafter flog is done, they'll all be removed
  113. blueit's all tooling upon tooling
  114. blueand I'm sick and tired of it
  115. bluejust need one good tool, (tm)
  116. phalethflog will replace tsc?
  117. blueyes
  118. phalethok
  119. phalethalso isn't proby your thing?
  120. blueyes
  121. blueproby is a test runner. flog will replace it
  122. blue@rcompat/test, that might stay there until primate can switch to std:test and dog
  123. phalethok, well concurrent test runner is better
  124. bluebut all those devdeps are heading to the dumpster yard
  125. bluethey're not really devdeps, they're tooling
  126. bluethe future is flog
  127. blueand not all those dumpster fires
  128. phalethso I've tried to use encore as just a JS runtime and it just wanted me to generate their project from their template and shit I was like hell no
  129. bluelol
  130. bluewhat is encore?
  131. phalethit's like you buy one product from apple and you have to dump everything else into trash to replace it with other apple crap
  132. phalethnot too sure, it's somebody having similar ideas to yours and just kinda replacing everything
  133. phalethbut they wanna lock you in you know, and maybe you will be accused of the same
  134. phalethyou will get comments like you do support TS, but it's not a TS, what it is
  135. blueI don't give a rat's butt
  136. phalethanyway, impossible to keep up with the standards
  137. blueI develop all my tools for myself, others are welcome to partake, if they don't want to, it's their prerogative to use their broken old tools
  138. blueI don't have to carry every backcompat nonsense the TS team feels obliged to. they have semver, they could decide to not do it
  139. bluepeople have apparently forgotten semver was designed so you can freely break stuff, like a bird
  140. blueinstead, people put themselves into self-inflicted prisons, not my problem
  141. phalethnah TS doesn't follow semver
  142. blueif TS doesn't follow semever, then why does it publish new majors? it should just switch to the firefox/chrome model
  143. blueso they kinda follow semver but also they don't
  144. bluealso your argument might hold for TS, but it certainly doesn't hold for node
  145. blueit does follow semver, but also it almost never breaks anything
  146. blueit could break stuff, it just doesn't want to
  147. blueif it broke stuff, people would be forced to update their old rotten software still using fs.write(callback) or whatever it is
  148. blueor stay on older, unsupported versions
  149. bluewhy do open source projects shift the burden of keeping your software uptodate, to themselves? and then complain they have no resource to maintain stuff?
  150. bluedreamreal: ^ honest question
  151. bluejust break forward, like linux does, and you don't need to maintain compat forever
  152. phalethpeople still use express and cjs, and still actually write more cjs than esm server side
  153. phalethand clanker keep supporting that crap too
  154. blueyeah but they do it because they can
  155. phalethso that means node cannot break, period
  156. bluewhen what's his name.. the esm guy, started publishing esm-only packages, people complained, but then they stopped complaining and continued to use his useful tools
  157. bluesindre*
  158. phalethso the thing is node is everywhere where non-browser JS is, I think even electron might use node, but dunno
  159. phalethand so if you wanna invade that space you just have to have everything well integrated, including editor support if you think people should write code
  160. phalethand in that integration sense also well automated, cause when people have to make effort they will not change their tools
  161. phalethit's always the same answer: PHP has already solved those problems
  162. phalethor whatever you put instead of PHP there
  163. phalethalso the biggest problem is mobile
  164. phalethmobile will be the biggest problem also for repopack, cause people like to sit on toilet when writing down ideas for whoever to work on, be it clankers
  165. phalethor lay down in bed or on a couch
  166. phalethlike who's having a desktop PC at home, only total nerds
  167. bluecan use repopack on normiephone too
  168. dreamrealblue: laziness
  169. bluedreamreal: ya but they complain about that one guy in nebraska maintaining it?
  170. blueidk, it just doesn't fit together
  171. dreamrealeveryone wants everything for free
  172. blueopen source should be something you do as a passion, you don't ned to maintain compat beyond what you have time to
  173. bluethat's what I do with primate. it's take it or leave it
  174. dreamreal"you gave it away, why are you not STILL giving it away"
  175. bluebecause I'm not obliged to :P
  176. bluebut no law of man or god
  177. blues/but/by/
  178. bluethe answer is simple to me. the question is why do so many open source maintainers put themselves in this bind
  179. dreamrealsure but people still want everyone ELSE to hold the burden
  180. blueI would never put myself in this bind
  181. dreamrealand since a lot of open source maintainers feel the same they bind themselves
  182. blueunless someone pays me to do primate, I'm not gonna support something I don't have the time, or more importantly, the passion, to support
  183. bluethis is something I will never compromise on
  184. dreamreal+1
  185. blueif I stop enjoying it, I'll stop doing it, I don't care
  186. dreamrealbut definitely fix all of MY issues
  187. blueyour issues are ALL fixed and more!
  188. phalethheh
  189. dreamrealI wasn't being serious anyway :D
  190. blueya, I know
  191. bluephaleth: did I tell you cit is compiling directly to assembly at&t, no libc?
  192. blueI think I also figured out ownership
  193. phalethyeah, so simple
  194. blueso clanker asked, how to deal with a scenario where you have a helper which needs to modify a resource, but also you want to give it back
  195. blueapparently rust has something like &mut or whatever craziness, like temporarily ownership or wahtever
  196. bluecit isn't having any of it, you transfer the ownership with !, and you give it back with ! again if you need to
  197. blueif you need to give it back AND provide more data, you give back a 2-tuple
  198. blue[!resource, bytes_read]
  199. blueit's all very simple, I don't know why rust complicates it so much
  200. blueit's a bit of go, a bit of rust, only the good parts
  201. blueit's very impotant to be able to read code in a linear way
  202. bluea bit like repopack tasks
  203. blueall those pointers are doing nothing good
  204. blueit's like all hidden sideeffects and whatnot. I think this is what zig is trying to avoid, but of course as we all know zig has become a dumpster fire
  205. blueso now we get zig simplicity, with rust-style ownership, and go returns
  206. blueall good and proper
  207. bluedreamreal: see how I actively engage in tikkun olam here?
  208. dreamrealI do, yes
  209. bluegood
  210. phalethblue: you should watch `Async Rust` from tsoding then you will remove rust completely :D
  211. phalethi can actually upload it for you if you want, it's a fun stream