If anyone would like to check, please check the updates. *Should* be working now.

worldpopulationreview.com/country-rankings/internet-speeds-by-country oh joy, another consumer of ReadableStream

no ReadableStreams? Have a blank page that for sure will load fast even on 300bps dialup

oh! enabling javascript.options.streams and dom.streams.enabled DO make the site work

wonder what can break

JamminUnit: what did you mean by "system-sqlite" ? different from sqlite3 ?

which does look to work (with a basic look, from what i can tell)

can (should ?) ircbot.comm-central.org:8080/seamonkey be include in the motd ?

therube: didn't mozilla remove system-sqlite (and likewise seamonkey) because their bundled sqlite is different from the original sources?

oh, i'd have no clue of specifics, i just download sqlite3 from sqlite.org, drop the .exe into my path & that's that (& rarely use it at that ;-)).

i know for sure with ZIP (aka, .xpi), that Mozilla diverged from, using obscure settings such that "standard unzip's" failed.

therube if you compile with system sqllite things might and did break in interesting ways. Sometimes needed changes in the code. So mozilla took it out.

One of the rare cases where I actually concur with them :)

System libs are awful, I will never understand those who feel the need to link the Mozilla application they're compiling to something like system ICU

Bundled libs are awful because you have to wait till vendors are fixing their bundled libs.

And sorry, I'd rather recompile one system lib than a dozen of applications that all use their own bundled crap.

Just look at the libwebp desaster...

In general, libraries that are used by a lot of stuff (e.g., libpng) should be installed system-wide and dynamically linked. Whereas obscure libraries that are used by so few things that most people will only install at most one thing that uses it (e.g., libjansson, opensrf) should NOT be.

In the middle, there is some gray area.

The exception is anything that breaks API so often that attempting to get all your software using the same version of it is an exercise in futility. The poster child for this is Python.

I have yet to discover a good way of handling that situation.

The problem is compatibility. Lots of these libs add stuff left and right without proper documentation or care about compatibility. If it breaks during compile time you can fix it. If it breaks because eg. optional parameter c is now no longer optional and using in code path y every now and then you have fun. Been there and had fun at least once with nss. In an ideal world I would love to...

...have only system libs.

in other words, welcome to hell

vendoring is hard to avoid in monsters like web browsers

theregister.com/2023/09/26/cloudflare_fnnts piss off, Clownflare

so..

wrote a thing

frg_Away tomman

CaptainTobin do you want to use it as a replace ment for the preprocessor in moz.build?

no tho i am gonna port this version of the preprocessor to py3 so we all have one that still isn't slaved into mozbuild

This is still along the same research I have always been conducting into build systems preprocessing file transformation etc

This script tho was written as an expression of an idea I once had that I abanadoned because uxp took priority and this didn't serve it yet

i needed it again so i found and rewrote it and decided it should be a full on project

for the benefit of all

what am I using it for tho frg_Away .. config generation like i used to in 2018 because I don't HAVE to do flat file cause some wolfbeast can't deal with literally the same shit as being done in mozilla

true story

frg_Away: Are there preprocessor deficiencies or behavior you might want added to the preprocessor?

fixed/added*

I know mozilla has dropped a few features

the state my script is in now is topsrcdir plus subdirs but not full traversal and it only copies and preprocesses.. so I basically have the core concept of mozbuild that does some things without full traversal in 300 some lines

that's pretty neat

add custom commands some modularity and you could easily have yourself a full on build system

and That is what my eventual aim is

CaptainTobin I really take it as a black box. Suite code is simple and does not need more. For mozilla and the other stuff I just take the patches apply them and forget about them soon :) When the time comes that I have time to optimize this I am probably too old or 6ft under. But probably never unless more people show up porting stuff and fixing things.

just make a resolution that if you all quit it all just falls to me

except any outstanding debts

:P

but yeah I am CURRENTLY and REVIVED this thingy so i could get back to generating my configuration cause I am SICK of hand rewriting everything and I hate that I ever agreed to go back to flat file because of moonmen

frg_Away: the options for me was to continue stripping down esr45's build system or just write 300 lines and create the core of a thing I wanted years ago

CaptainTobin well I tried a central build yesterday and I am sure I will not take this code. Basically downloads the Windows toolkit and the msvc compiler core during a normal build . Gigabytes of stuff already installed...

what code is it?

oh yeha

i know

i did a trunk build of firefox

as an experiment

and it has lead to some twisted thoughts

frg_Away:

twisted xhyperxul (not-xul xhtml) stuff

Do you want to know how all that works?

cause it will piss you off

Well now counted 487 external rust carates as dependencies.

to no end if you still have any real love for xul left

^crates

Hey frg_Away how would you like a seamonkey on central

it won't be compatible with anything

CaptainTobin I like xul and wish mozilla had kept it as the frontend interfacer langauge. All the html and xhtml stuff s*cks.

yes but I found a common point of reference that has a near perfect history from an fe developer's perspective of the transition..

Firefox's Page Info Dialog Window

is almost untouched stylistically from its aviary toolkit design

CaptainTobin Credge now is so bad in 117 that I downloaded Vivaldi. Only used it in one Linux vm before. It is basically what a Central SeaMonkey would be.

I think there is more that can be done with the technology that is left and currently exists

plus a little help from some of the failed waterfox appstore plans

and their post-quantum bootstrap shims

If I need to give up this is the update path for me.

still won't help you update the fe

nope

what we need is first and foremost a xulrunner example

yes i know shut up it is still internally is a stub and supports -app to boot unless it was recently removed

someone needs to build a central app from scratch using current day techniques referenced from failurefox

frg_Away:

a non-firefox/thunderbird reference toolkit application

firefox and thunderbird are FAR TOO specialized at this point to reference dick without knowing the history and finding common points of reference

this was the final cost of the xul add-ons system being removed

today no one who doesn't already work on current day mozilla code has any idea how any of it fucking works

or even how it relates to what was

and I think this was intentional by some

to get people to STOP using mozilla as a platform

which has SEEMINGLY been a trend ever since everyone was kicked out of mozilla-central because you were all old and insecure

CaptainTobin well we are still in comm-central and building at least.