@lanodan People are still contributing to the repositories, but there hasn't been a release since 2020. It seems like they really need help with parsers and supporting more W3C standards. Their JS engine in particular is still barebones which is why it's disabled by default.
@lanodan The NetSurf team said that they plan on adding support for dynamic changes to web pages. They want to be compatible with all web standards, even if they are still far off.
@icedquinn Well… Mozilla is shrinking hard anyway but that was predictable even pre-Eich.
(And I don't give a flying fuck about either, it's like talking about rockstars)
@lanodan orgs reflect their masters. (or i guess i should say project, but there is a heavy dose of how a company functions has a lot to do with how the helm behaves.)
@lanodan as far as i can tell management actively wants to destroy the company. they gave the CEO full bonus for firing the infosec and servo teams.
i can't think of reasonable explanations why you would fire core competencies--and get a full bonus--unless the stakeholders actively want the company to fail.
@lanodan their old internals were pretty anarchic though. they sort of loosely put together projects with goals and relied on people more or less self assembling in to working groups to work on those and then management would provision some budget for the working group to do it. they made a lot of wild stuff that way but i don't think could ever figure out how to market them (like the whole Firefox OS project that spawned a lot of fonts/code/weird shit that management chunked in the trash for some reason i forgar.)
i don't know how it works now. it used to work very similarly to Valve.
@ch0ccyra1n I'd say WebKit because it's daily-drivable.
But much more importantly being aware enough to support/join an organisation or campaigns to actually defends your rights.
Because as seen in the past, Mozilla won't actively do anything against DRM.
And DRM is a legal mean first and foremost, from the software point of view it cannot ever work, but it's made illegal to make and use workarounds.
So there should be law changes to at the very least reduce the applicable scope of DRM.
@tusooa@ch0ccyra1n Yeah, quite expected, cog has the same kind of issue.
WPE is pretty much letting your use a raw engine, which is great for embedded devices because inputs are often weird on those, but for desktops it's quite meh.
@lanodan@ch0ccyra1n@tusooa weren't aware that there are rough edges when trying to use WPE as an engine for a “full” browser on desktop style environments, and while we would like to improve in that regard, embedded usage has more priority because that's what sponsors the overall work on the engine and also a non trivial amount of work on the GTK port. The latter is partly because of the shared architecture of both ports, and in part because the GTK port is often used as test mule for WPE work (it is more convenient like that sometimes).
@aperezdc@ch0ccyra1n@tusooa Oh, that's pretty nice to hear that you would wish it to improve, at least patches welcome rather than "possibly out of scope 🤷️".
And yeah the sponsor part makes a lot of sense, at least from Igalia.
Add comment