16:13:05 Gonna update my nightly in a few minutes, any late-minute breaking bugs or new shinies I need to be aware of? 16:14:33 tomman using it all day. So far not. New async cookie stuff in but seems to work. 16:14:43 OK, I'm good to go then~ 16:23:37 frg_Away: do i need to kick the xulorg xref? 16:24:51 i should just setup the dang cron job it won't do anything if there is nothing to do.. Yeah I'll do that .. disregard the question 16:25:08 also... NO NOT AS THIS NAME I WON'T 16:25:23 NewTobinParadigm Hi! No only in the prerelease yet. We are late with 2.53.18 16:26:17 frg_Away: I have had a week I tell you 16:26:31 lot of local insanity 16:26:51 really has my mind focused tho.. 16:28:41 MattATobin well insanity seems to be the new normal :) 16:29:28 well not the new insanity 16:29:33 this is.. classic insanity 16:29:40 I am well suited to handle it. 16:29:44 frg_Away: :P 16:29:53 insanity is the new normal indeed, be it old or new 16:30:11 the very moment you push the power button on a PC, you don't run code, you invoke insanity 16:30:14 yeah but the new insanity thinks the old insanity is old and insecure 16:30:18 or something tomman 16:30:19 lol 16:30:52 ah, that reminds me that GNOME wants to nuke X11 and Wayland defenders want to bury me with the usual "butbutbut it is INSECUUUUUUUURE!!!!" crap 16:31:05 tomman: I told you this a month ago 16:31:17 gonna be fun when Debian finally switches to Wayland with no option to go back 16:31:18 did you forget I am also a KIND of prophet? 16:31:26 sometimes 16:31:34 unlike Pipewire, a transition that was so subtle that things kept working without even noticing 16:31:51 man, I didn't had time to hate on Pipewire because... It Just Werks™! 16:32:03 that's something you can rarely say from any new piece of software these days 16:32:07 but Wayland... lolno 16:32:24 well wayland is gonna be forced on everyone regardless 16:32:31 xorg is dead 16:32:36 it has been dead for 10 years 16:32:51 deader than seamonkey under neil's leadership 16:32:59 then I'm a extinct dinosaur 16:33:09 if Debian forces Wayland on me, then I'm switching back to Windows Me 16:33:15 tomman: nah you're a cave man 16:33:17 or simply quitting computers forever 16:33:36 and your cave will likely outlast the other fucker's shack 16:33:47 my cave is anything but shiny 16:33:53 but at least it has LED lamps :D 16:34:19 anyway the SOLUTION is 16:34:28 make em do what they should anyway 16:34:34 which has been working recently 16:34:40 but it will never be x12 16:34:43 however 16:34:58 xwayland could be if more focus and attention was given 16:35:19 and more features added so that xwayland can actually HOST a de not just an application 16:35:41 this SEEMS to be the ONLY viable way through short of a new effort to create an actual x11 successor 16:35:48 tomman: 16:36:58 which would fail as it is too foundational to continue without vendor and distro support 16:37:05 or someone's bank account anyway 16:37:13 People insist in saying that "Wayland IS X12" and "Xorg developers are now Wayland developers", but with so many half-assed / missing / outright broken features, "my way or the highway" developers (sounds familiar?), nVidia's refusal to play ball (not Wayland's fault per se, but shaming users for their GPU choices is of bad taste), and a general disregard for anything that isn't lifted off... 16:37:14 ...from cellphones... well 16:37:24 ...I'm not using Wayland for as long as I'm alive 16:37:39 tomman: then you will not be using linux eventually 16:37:44 are you prepared for that 16:38:14 I'm a citizen of the Soviet Bolivarian Republic of Venezuela, so soon I would not even be using electricity 16:38:19 so yeah... 16:38:41 well least it makes it more interesting 16:38:54 which goes first 16:38:58 x11 or basic electric 16:40:12 that's no fair, betting on Venezuela is like betting on a race between a Formula 1 and a stolen bike with a flat tire :D 16:40:20 tomman: well just please understand i was not trying to say do this or else only highlight the consiquences.. most unlike you or I make those declairations and then a few days later are doing what they said they don't forgive me 16:40:51 nah, I'm well aware that the future is grim no matter which path me or the world pursues 16:41:24 can you .. leave? 16:42:58 nah 16:43:14 the last thing the world needs is yet another Venezuelan defector fleeing from a not-war 16:43:25 not an option for me, and that's for the best 16:43:51 at least I have a roof, some food, and aging computers being actively sabotaged by Apple wannabes :) 18:42:48 MattATobin: hasn't Xorg actually had a recentish release in the past few months? or that was just changing build systems? 18:43:31 the problem might be that there is no other group working on X, or is there any other X project? 18:44:39 (who's the current upstream for Xorg? freedesktop?) 19:11:31 hello, tried seamonkey 2.53.18b1-pre. this developer version contains a "New RegExp Engine in Spidermonkey" patch. This new RegExp Engine improove massively the capability to show javascript websites correctly. Does somebody know whether thist new RegExp Engine will be added to source code in version 2.53.18 ? 21:26:28 njsg: yeah but no one is invested in active development it is basically more zombied than sm was circa say 2015 21:57:47 norgo the new regexp will be 2.53.18. The prerelease will become the beta and then the release. Hopefully pretty soon. Still polishing a few things. 22:15:43 frg_Away: if it would help once I get xulorg's xr back onto another server I could support a latest_trunk.txt as well 22:20:56 MattATobin well there is only the messy queue and no actual latest trunk so this would be hard to achieve I think. 22:21:45 yeah i see 22:22:06 Spam. 22:22:12 I bought a can of spam 22:22:17 for what reason I dunno 22:23:18 MattATobin 2.53.18 got lots of backports and is overdue. Usually it is not that bad and evern here the xref 2.53.17.1 is usually ok. Check it frequently for stuff. 22:23:51 i can't wait to try it my self and build with it 22:23:52 also 22:24:37 frg_Away: for central do i just need vs2022 the sdk and rust and mozillabuild and i can build per normal or do i HAVE to use mach bootstrap 22:24:43 rust/clang* 22:24:56 cause i really hate that mach bootstrap process 22:27:58 MattATobin I think you need mach bootstrap. need to set up clang cbindgen bindgen nasm and a ton of other dependencies. Central is becoming worse by the month. Also the configure pulls in the stuff anyway during build unless you use ac_add_options --disable-bootstrap 22:28:31 Also ac_add_options --without-wasm-sandboxed-libraries unless you want to have some fun with rlbox. 22:28:32 linux isn't as bad i take it 22:29:26 yes but you still need llvm. But atl least the dependencies are mostly used from system. 22:29:55 thank you for that tho --disable-bootstrap should give me enough to assemblem manually and create a guide only a few nutballs like me will use but hey that is part of what I do right frg_Away 22:30:48 I just don't like the idea of mozilla controlling and installing toolchain stuff 22:30:53 it is.. conserning 22:31:14 I get why they do it but damn manual instructions would be nice 22:31:26 I WILL WRITE THEM 22:33:10 let me check if we have reached the 500 rust crates dependency yet :) 22:33:22 could be worse 22:33:24 could be... node.js 22:35:14 tomman They now pull in node js packages too and depend on them :) 22:35:26 eww 22:36:03 Only 491 rust crates. 4 more than the last time I counted. We are getting close! 22:40:30 well 22:40:52 it's only a problem if you ever have to touch the code 22:41:32 too bad aside from waterfox badly doing it and whaetver wackjob direction thunderbird is going no one else uses CURRENT mozilla technology for anything 22:41:56 not really 22:42:05 not for more than a minor rebuild 22:53:30 The build system is turning into a maze and you have a hard time using parts of iany gecko code. 22:54:20 I've seen projects whose build systems HAVE a build system! 22:54:33 I guess that's the next step for Mozilla 23:17:36 well leave why don't you 23:17:37 LOL 23:17:40 hi tomman 23:18:19 tomman: isn't mozbuild a build system to generate makefiles that rely on autoconf? 23:18:47 is that even a real question because as a "Build System God" as I deemed my self some time ago I already know the answer 23:19:31 https://developer.mozilla.org/en-US/docs/Web/API/Notifications_API/Using_the_Notifications_API wait, what - MDN now dies with a WSoD here!? 23:19:43 it blinks for a split second, then... bye bye page 23:19:50 "SyntaxError: An invalid or illegal string was specified" 23:20:12 that line starts with !function() 23:20:48 > SyntaxError: An invalid or illegal string was specified main.553bdfe0.js:2 23:21:15 ah no, it's some .TS script 23:21:30 iframe.contentWindow?.postMessage?.(message, { targetOrigin: "*" }); 23:22:05 https://developer.mozilla.org/static/js/playground/utils.ts