Last week, some niche streaming platform decided to drop support for #Firefox, which was odd to me as it still works fine once I set my User Agent to Chrome.

Turns out, they were planning a new "Premium" subscription with HDR, which Firefox does not support yet.

I get that they probably want to avoid users complaining that the feature they paid for does not work, but could they not just have put a banner that reads "HDR not supported on your browser" instead?

Is introducing Rust to Linux kernel making it safer and less bug prone or causing interop hell?
WDYT?

#Linux #rust #rustlang #OpenSource #interop #RustBindings

https://arstechnica.com/gadgets/2025/02/linux-leaders-pave-a-path-for-rust-in-kernel-while-supporting-c-veterans/

Interop revient pour améliorer la compatibilité de Safari, Chrome et Firefox http://dlvr.it/THz99l #Interop #Interopérabilité

As usual it seems #Interop is all about the shiny-shiny. Maybe I just don't get the criteria. Maybe it's just sour grapes. But...

Yes I'd love to see Anchor Positioning implemented as much as the next person, but there are actual harmful bugs that need to be fixed. Rightly or wrongly I see Interop as a way of pressurising browser makers into prioritising them, including these old chestnuts:

https://github.com/web-platform-tests/interop/issues/749
https://github.com/web-platform-tests/interop/issues/748

Yes! CSS anchor positioning is part of Interop 2025. The focus areas were just announced! Can't wait to have cross-browser support for it! https://wpt.fyi/interop-2025
#webdev #css #interop

Redefining enterprise transformation in the age of intelligent ecosystems

https://buff.ly/40luSPB

"Pivoting our architectural design assumptions away from systems of record that are abstracted by integration layers and redundant data stores to systems of intelligence that can enable fully autonomous process automation with agents is the nature of modern transformation."

The New New Moats | Greylock

https://buff.ly/42OC99W

"Large language models like GPT-4, PaLM2, and LlaMA are tangible examples of the way AI is becoming the enabling technology of this moment. "

Interoperability’s Role in Digital Transformation Success

https://buff.ly/4jjKfkp

"Interoperability is essential for businesses aiming to remain agile by integrating flexible, composable technologies across digital ecosystems."

Le succès renouvelé d’Interop, la compétition amicale pour améliorer Safari, Chrome et Firefox http://dlvr.it/THMl7M #Interop #Navigateur

Various #ThingUmbrella and #GenArtAPI updates from this week:

- Added null pointer checks & guards in https://thi.ng/wasm-api. This also includes support for structs with fields using Zig-style optional pointers.
- Updated the https://thi.ng/wasm-api-bindgen code generator for #TypeScript to produce smaller code for structs using many string fields
- Did major ground work on #Zig #WebAssembly bindings of core https://thi.ng/genart-api functionality (see small demo below)
- Fixed/updated/simplified time provider logic
- Updated the debug time provider with its FPS analytics/visualization overlay, now computing moving min/max and moving average (default period = 200 frames) and the viz is dynamically/smoothly rescaling to current peak
- Released new GenArtAPI v0.9.0

As for the Zig/WASM example: This is only interesting from a technical POV, no visuals here! All canvas drawing and parameter declarations/evaluations are done via Zig, using the aforementioned https://thi.ng/wasm-api infrastructure to provide a new API module which can be seamlessly used with the other hybrid WASM API modules, here for DOM creation (https://thi.ng/wasm-api-dom) and to handle Canvas2D drawing (https://thi.ng/wasm-api-canvas).

At the moment, this GenArtAPI WASM module is still a fixed part of this example, but will eventually be extracted & distributed as separate package.

Demo (with param editor):
https://demo.thi.ng/genart-api/param-editors/?url=https://demo.thi.ng/genart-api/zig-test/

Choose one of the two GUI implementations, then make any parameter changes and you should see the new values applied immediately (btw. the demo is likely not very usable on mobile)...

Source code (TypeScript in `/src`, Zig in `/zig` directories):
https://github.com/thi-ng/genart-api/tree/main/examples/zig-test/

#lazyweb #dotnet #interop #nodejs #typescript

I have a module written in typescript that does some complex proprietary logic. It's consumed by several clients using it in node.

I have a new client who are dotnet based, specifically F# but language shouldn't matter, right?

Is there an accepted interop approach that would allow the typescript module to be consumed in dotnet?

Are you excited about better formula support in browsers? Help us with 30 seconds of your time.

You can give a Github thumbs up to MathML's 2025 interoperability requests:

Math Rendering:
https://github.com/web-platform-tests/interop/issues/787

Math+CSS Styling:
https://github.com/web-platform-tests/interop/issues/861

I've been toying with #SVG filters a lot lately. If you like this stuff, please vote for them to get more from browsers

https://github.com/web-platform-tests/interop/issues/756

While CSS has progressed a lot lately, SVG got left behind. Filter perf can be abysmal & there are bugs in all browsers, some opened in the 2000s.

This is an opportunity to improve #interop and #webcompat across browsers.

Read carefully the blog post and specifically the section "What Makes a Great Proposal?"

PS: Si vous êtes francophone et que vous aimeriez contribuer mais que vous avez du mal avec l'anglais, je peux vous aider.

https://webkit.org/blog/15942/get-ready-for-interop-2025-your-chance-to-shape-the-web/

If you're like me and have been publishing your computational/code-based/parametric/generative art for a long time, you'll likely have run into issues of having to revisit and re-edit/re-configure your pieces for different usage scenarios (e.g. preparing for an exhibition), which can become quite time-consuming & annoying for those pieces which originally had been created for a single publishing platform only (e.g. fxhash, highlight, etc.) and whose integration mechanics become a hindrance for such repurposing (or have changed themselves in the meantime and require updating)...

For that reason (and several other sanity-related aspects), over the past 6 months I've been refactoring most of my own pieces from the past 3-4 years to use a new platform independent API to deal with all parameter related aspects, obtaining/seeding PRNGs, configuring resolutions, time providers/schedulers (e.g. for realtime/non-realtime animation), transport control (i.e. start/stop/resume), exposing "art features" (e.g. for rarity calculation), triggering preview/thumbnail generation etc.

Now my art works only depend on this generalized API and any platform-specifics can be injected via small "platform plugins" (which means simply adding another script tag to your HTML)

I wrote about this all a few months ago already, but just added a first tiny public example, started updating the project Readme and also been doing some more documentation work on this x-platform API & workflow options.

The benefit to artists working in this field is very clear to me already, but also publish platforms/markets can benefit from adopting (and helping to shape) this API more (with very little integration effort required on their end). Mostly they'd just need some minor glue code, event handlers for their platform-specific param encoding/decoding. On the other hand, they can delegate things like param validation, coercion, randomization etc.

If you want to have an early look at the example:
https://demo.thi.ng/umbrella/genart-api/

- the "art" running in an iframe has zero knowledge of anything other than the x-platform API
- some of the supported param types have no GUI widget in this demo
- the GUI widgets are auto-generated from exposed param specs
- updating widgets and propagating these changes is done via IPC messages (via the genart API)
- not all features are shown in this example!

Repo:
https://thi.ng/genart-api

Since I've been working on a bunch of other things, progress on this has rather been slow, but I'll be actively looking for feedback and will post another update once I'm more ready to receive/address this...

I just wanted to publish this blog post, but I found 2 new bugs!

Will file them later, but its reminding me of what happens when using bleeding edge* technology and how there are still #interop issue to iron out!

ok, so mastodon and wordpress have been federating for a while but often using them together i'm finding new issues!

"It’s time to stop playing defense. It's time to go on the offensive. To restore #competition, #regulation, #interop and tech worker power so that we can create the new, good internet we’ll need to fight fascism, the climate emergency, and genocide.

To build a digital nervous system for a 21st century in which our children can thrive and prosper."

@pluralistic says it's time to "Hack the planet!"

https://pluralistic.net/2024/08/17/hack-the-planet/

Sometimes a CSS bug interoperability inconsistency will manifest for different size parameters depending on the browser. Using a CSS animation to vary automatically the parameters will help show when the difference occurs. #css #webcompat #interop