Chat Logs

  1. bluehi phaleth
  2. blueworking on an rcompat article. might offer it to bytenews if dreamreal is interested
  3. dreamrealDefinitely
  4. dreamrealno question
  5. phalethhi
  6. phalethblue: a C lang related article?
  7. bluephaleth: no, a JS related article
  8. phalethok, cool, I'm trying to figure out how to use buildkit as tcp server
  9. bluedreamreal: where should I send it to you?
  10. bluesent over discord
  11. dreamrealYou could always just submit it on the site :D checking
  12. dreamrealand it'd be BETTER if you submitted it, since that way it's attributed to you and not to me
  13. dreamrealreading now
  14. blueyes, but that would require me creating a user
  15. dreamrealoh no
  16. * dreamreal sighs
  17. dreamrealit's just a login, you give it your email, it verifies you own that email, done
  18. dreamrealauthorship is a big deal: if *I* publish it, I get to preface it with "this was submitted by an anonymous user" because otherwise it's presumptive authority on MY part
  19. dreamrealand even if I agree with everything it says, it's STILL presumptive
  20. blueI guess I can submit it anon via the form, is that better for you?
  21. dreamrealBetter than under my own name, sure. At least it's attributed to *someone else* in that case, and it gives you more control over it, although not as much as if it's your user.
  22. bluecan you change my username, not sure why it's decided it's terrablue?
  23. dreamrealYou can change it, but I can, too
  24. dreamrealwhat do you want it to be
  25. blueI can only change the display name
  26. blueblue
  27. dreamrealit derives it from the email address
  28. dreamrealokay
  29. dreamrealI'm going to make notes for the article, then fix the refs
  30. blueoof, the generate preview thingy is a dumpster fire
  31. blueok, draft submitted
  32. blueI can't really see my submitted drafts, but I trust it's there
  33. dreamrealit's there, yes, I'm working on it
  34. bluethx
  35. dreamrealand your username has been updated, as has your display name
  36. bluenice
  37. bluehad to login again for that to show, but still nice
  38. bluethx
  39. dreamrealhttps://bytecode.news/posts/2026/05/javascript-server-side-interoperability-with-rcompat
  40. bluecool, great, thx
  41. bluedreamreal: could you please fix the extra ` in the @rcompat/symbol example?
  42. blueit breaks code highlighting
  43. dreamrealyes. And you SHOULD have had the option to edit your own posts, FTR
  44. dreamrealit's fixed, though
  45. bluecool, thx
  46. phalethprimate mentioned, only as a tag, but still
  47. blueoh yeah, I was trying to avoid too much dogfeeding
  48. dreamrealphaleth: *I* added that
  49. bluethe CodeError stuff is particularly legit btw. because a primate user can indepently import and throw a CodeError from @rcompat/error, and primate will still display it properly
  50. blueindependently*
  51. blueI'd been struggling with it a lot in the past. particularly in primate modules like @primate/ruby etc., I wanted to throw errors in a way that's standard but also that I don't need to import anything from @primate/core
  52. bluedreamreal: are you ok with me sharing that article on HN?
  53. dreamrealof course
  54. dreamrealandrew actually pointed out a few optimizations last night, applied them on the deployment
  55. bluehttps://news.ycombinator.com/item?id=48051959
  56. nevetJavaScript server-side interoperability with rcompat | Hacker News
  57. bluehere we go, please upvote
  58. dreamrealbwahahahaha
  59. dreamrealI was watching the server logs :D
  60. blueyes?
  61. dreamrealit was... hefty :D
  62. blueheh
  63. bluedreamreal: https://github.com/V4bel/dirtyfrag
  64. blueonosendi: https://bytecode.news/posts/2026/05/javascript-server-side-interoperability-with-rcompat