Interop Tokyo 2025、6月11〜13日に幕張メッセで開催。「社会に浸透するAIとインターネット」をテーマに基調講演や来場の受付中
https://internet.watch.impress.co.jp/docs/news/2017552.html

#internet_watch_impress #イベント #Interop #Interop_Tokyo_2025

check out the Interop 2025 dashboard! wpt.fyi/interop-2025 #web #webdev #css #html #javascript #interop

RE: https://bsky.app/profile/did:plc:q7suwaz53ztc4mbiqyygbn43/post/3lpn74gnk4c25

tables paper cut #interop

My colleague Alexander Zautke gave an amazing presentation this morning on the #FHIR journey from AdapCare, from complying to regulation to wild innovation.

He also gave a sneak peek of the upcoming #StateOfFHIR survey: FHIR is entering health it regulation everywhere 🐙

#HealthIT #Interop

#Chrome and #Firefox need to support margin-trim, like… yesterday.

It makes things sooooo much easier. A single property applied to the container, rather than stuffing around with multiple :first-child and :last-child rules to try to create the right behaviour.

It’s a shame it didn't make it into #Interop2025 because it’s such a useful property and elegantly deals with a layout situation that occurs all the time.

#Interop #CSS

https://webkit.org/blog/16854/margin-trim/

Steps Forward in Long-form Text

https://socialwebfoundation.org/2025/05/01/steps-forward-in-long-form-text/

FHIR version R6 is going to be the first big new normative release after the widely adopted R4.

🗳️ The 3rd ballot release of R6 for the May working group meeting is available now: https://hl7.org/fhir/6.0.0-ballot3/ballot-intro.html

🗓️ After that, the first normative ballot in Jan 2026!

#FHIR #Interop #HealthIT #HealthTech

バイナリーで6桁の時代に突入する「Interop Tokyo」、よりディープな有料カンファレンスの来場登録も受付開始　6月11日～13日に幕張メッセで開催
https://internet.watch.impress.co.jp/docs/news/2007408.html

#internet_watch_impress #経済 #イノベーション #テクノロジー #産業 #イベント #Interop

Dear browser makers, please fix LCH. The promise of LCH was that the L could be trusted: no matter what the hue is, the lightness would always be the same perceived lightness. In your current implementations this is completely broken. It’s even worse than HSL

☞ https://issues.chromium.org/issues/40909194

☞ https://bugs.webkit.org/show_bug.cgi?id=255939

☞ https://bugzilla.mozilla.org/show_bug.cgi?id=1847421

#browser #interop #css #chromium #webkit #gecko

「Interop Tokyo 2025」6月11日～13日に開催、展示会・基調講演の入場登録の受付開始　1994年の日本初開催から32回目となるインターネットテクノロジー専門イベント
https://internet.watch.impress.co.jp/docs/news/2005125.html

#internet_watch_impress #経済 #イノベーション #テクノロジー #産業 #イベント #Interop

tldr: everything in pieces on the shop floor, but....

I'm trying towards an implementation of Babashka Pods in Haxe.

Given Haxe is a polyglot language, it makes sense to go for a polyglot interop solution.

There's things like built in async handling, client side code and platform awareness, very much the inverted pyramid that's good for adoption by keeping complexity at the base low.

A Haxe Pod implementation would transpile to around 10 different languages, and could be a base for a repl implementation, certainly of HScript, and or KissLang or some of the other languages and dialects cropping up.

Looking at what I did with Stig this week it probably bears some explanation.

I wanted a structured data format that doesn't rely on reflection, doesn't require the heavyness of the internal runtime representation of tagged unions (enums/gadts) but can be pattern matched on.

The external StigForm is neither here nor there, the internal StigNode is the important bit. There's probably a few minor adjustments so it can sit well in most languages.

I might well use it to build a Bencode output, as it fits perfectly.

The inclusion of Stx, or the dead-code eliminated version of it is for parsing is unavoidable, but the generated loc is only around 5k at present.

It's based on Stephan Le Dorze's mix of Haskell Parsex plus Alex Worth's Phd work on linear time left recursive packrat parsing, and I've been tinkering with it for years.

Work on Go2Hx by PXShadow means there's the opening to cross compile CueLang, meaning that there's an opening for language native type generations from Cue, which is pretty exciting, and Haxe has an extremely compact and well designed internal type representation, and the new completion algorithm is very snappy.

Still work to do though, I'm in the middle of a rebuild atm.

#Haxe #Programming #Babashka #Edn #Pods #CueLang #GoLang #OMeta #Parsex #Interop #DevOps #OMeta

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?

#WebDev #Interop

🔴 Interop 2025: another year of web platform improvements
by Rachel Andrew @rachelandrew @rachelandrew.bsky.social
#WebDev #css #webperf #Interop

https://web.dev/blog/interop-2025

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/

[Перевод] Кофе и крабы. Вызов Rust-кода из Java

Java — один из наиболее часто используемых языков программирования, который мы еще не обсуждали в нашем Rust Interop Guide . В этой статье мы рассмотрим три различных метода вызова кода Rust из Java : JNI , JNR-FFI и Project Panama . Мы покажем различия между этими методами и проведем базовый бенчмаркинг для сравнения их производительности. Эти методы работают не только для Java , но и для других языков JVM, таких как Kotlin . Здесь мы в основном сосредоточимся на Java , но примеры Kotlin доступны в ветке Kotlin нашего репозитория GitHub . Эта статья является частью нашего Rust Interop Guide .

https://habr.com/ru/articles/884150/

#rust #java #interop #ffi #project_panama #jni #jnr

Interop 2025 Announced

https://fed.brid.gy/r/https://frontendmasters.com/blog/interop-2025-announced/

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

#MicrosoftEdge and #Interop2025 #Edge #Interop
https://www.elevenforum.com/t/microsoft-edge-and-interop-2025.33414/