Community
Chat Logs
Friday, October 16, 2026 (America/New_York)
- * skillnews quit (Remote host closed the connection)
- * skillbot quit (Remote host closed the connection)
- * skillbot joined #primate
- * skillnews joined #primate
- * jreicher quit (Quit: In transit)
- * jreicher joined #primate
- blue🐕
- bluedreamreal: dog is coming
- * jreicher is now known as Guest3554
- * jreicher joined #primate
- * Guest3554 quit (Ping timeout: 261 seconds)
- dreamrealwhat breed? :D
- blueyou know the answer, dreamreal :P
- dreamrealI, uh, might have a guess
- jreicherBasenji.
- dreamrealprobably a shih-tzy?
- dreamrealschnauser? dachshund?
- bluejust to be clear, I'm not getting a dog (yet)
- dreamrealmaybe a rottweiler?
- blueI'm working on a js runtime/engine called Dog
- dreamrealhaha
- * jreicher quit (Quit: In transit)
- * jreicher joined #primate
- blueWB jreicher.
- dreamrealnew mastheads online :D
- dreamreala colorized mondrian, colorized harmonizer, and two new life variants
- bluewow
- dreamrealblue: where's rcompat's site?
- bluedreamreal: nowhere
- dreamrealwhy
- dreamrealit needs one on primate.run at least
- blueidk, it was never needed I guess
- bluedo you need one?
- dreamrealhave a friend who's migrating from deno to bun, I'm like "crikey, rcompat, then you get node and bun without having to target them any more" but I have nowhere to POINT HIM
- bluehm
- bluedreamreal: give me 10 mins
- bluedreamreal: https://rcompat.repopack.app/
- nevetrcompat — JavaScript standard library
- blueI think this should be enough for his purposes, I don't have a bespoke domain for it atm
- bluein the future it'll be under std.flog.run or so
- bluedreamreal: you can tell him, but he probably knows, that going forward, deno support in rcompat will be sunset roughly 6 months after deno itself is discontinued
- blueso technically he can move now and continue to use deno, and test with bun/node
- bluemoving is anyway most effective, will spare a future rewrite
- dreamrealHe doesn't WANT deno support, but he's moving to other runtime environments, and porting TO them
- dreamrealso rcompat actually addresses his actual needs
- dreamrealbut he doesn't know that and I can't SHOW him because you don't show ME
- blueI just sent you the docs website dreamreal
- dreamreal(and showing me is pointless: show him!)
- bluewht do you need showing else?
- dreamrealwhere
- blue18:22 < blue> dreamreal: https://rcompat.repopack.app/
- nevetrcompat — JavaScript standard library
- bluehere, 14 minutes ago
- dreamrealoh, sorry
- dreamrealmissed it, was AFK
- blueno worries
- dreamrealSwnt to him
- bluegreat
- bluercompat itself doesn't have a suppotr channel. but he can use the primate discord or this channel for rcompat support
- blueI make the same promise as I do for primate, which is, I will at least look at the issue within 48h
- bluethe rcompat website is now triggered to redeploy on master advances :P
- bluetakes 22s to redeploy. hm, still too long, but then again it's using pnpm, I should move to flog
- dreamrealwhy is it r/compat and not rcompat?
- blueyou mean designwise? it's jsut what clanker came up, and I like it. I mean it is "runtime compat"
- dreamrealIt was a question from the guy I was talking to, he was like "was it reddit inspired of course it was"
- dreamrealI told him I severely doubted it :D
- blueyou can tell him that clanker came up with it, and the human operator approved
- dreamrealI'll let you do that if he ever joins
- blueI mean, up until 30 minutes ago, rcompat had no logo. now clanker proposed, and I didn't disagree
- bluewe all have to remember that rcompat is not yet eden. it is upon the gates of eden. eden is "std:*", but for that we need runtimes to hop on, and I don't have traction for that
- blueone of the reasons for dog is to challenge runtimes to get into that eden
- blueI have long pondered how it's even possible to get this done. and the only way I see forward is to use "std:", publish source TS to npm, and have `flog publish` rewrite "std:*" to @rcompat/*" for js. since node doesn't respect the "source" runtime key, it would still work for node, but anything that supports std:* + "source" runtime key, would benefit from the new world
- bluesystemfault: ^
- * skillbot quit (Remote host closed the connection)
- * skillnews quit (Remote host closed the connection)
- * skillbot joined #primate
- * skillnews joined #primate
- * nevet joined #primate
- * 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
- systemfaultHmm, so rewriting imports is the cleanest way?
- systemfaultWouldn't be possible to use something like require hooks or similar to allow it? (I guess the node devs don't want that...)
- bluesystemfault: the problem is that if I want to change primate to use "std:" imports instead of "@rcompat/", then the next version I publish like that, would stop working under node (and bun)
- systemfaultRight :/
- blueso my idea was, to publish both src (TS) and lib (JS). src contains "std:, lib contains the same imports, but flog rewrites them to "@rcompat/". and package.json uses a "source" runtime key for "src/". node ignores "source" unless you write --conditions=source
- blueif node ever supports std:, it would need to support the "source" runtime key...
- blueit's a complicated way, but it's the only way I can see to run things under node/bun until/if they add support for "std:"
- blueand also I've been wanting to publish TS to npm for a while. node not loading TS from node_modules is such a stupid and unnecessary limitation
- blueTS is the source.. why should I build it when publishing? building/type-stripping should be the user's responsibility
- blueI heard such weird arguments against publishing TS to npm. like, you'd have to publish a tsconfig and version it... I don't think that's a real argument. node can strip TS today and it doesn't need a tsconfig for that...
- bluethe only problem with publishing TS is if you use non-erasable syntax.. and you shouldn't. maybe flog could check that as well when publishing
- blueI think that's an elegant way forward systemfault...
- systemfaultThe only logic argument I can find is that they want the Node ecosystem to remain JS.
- bluewhy? TS is superior...
- systemfaultSome people just don't like TS... some people are "omgomg MS is EVIL, can't use TS"
- bluewell I used to be anti-TS as well, but then I gave it a chance, and it's just better. especially erasable TS is amazing...
- blueit's irrelevant if it comes from MS or whatever... it's good software/language
- bluewell, I'm gonna go back to watching die hard... I'm out of codex for now
- systemfaultThe first one?
- blueDie Hard with a Vengeance.. I think it's the third?
- dreamrealI don't like TS because it's TS, not because it's MS
- dreamrealTS types would be great if they were consistently enforced but it can use JS so it lies
- bluewell, it's a superset dreamreal, how do you mean, "it can use JS"?
- dreamrealWell, TS adds a lot of useful things like "type enforcement," for example, but types are lost once you go to JS
- dreamrealthis is just a generalized gripe about JS as an ecosystem, so ignore me
- bluethen you should be reading what I've written above; if you publish TS to npm, the only time it gets lost is when the runtime runs, stripping the types
- blueunless you're concerned with runtime types in your criticism
- dreamrealthe runtime is when I care :D
- dreamrealbut it's not a severe care, I write JS very rarely so I just shrug now
- dreamrealwhen I lived in JS-land I cared a LOT
- blueya