Menu

#Interop

8 posts

Feed·
8 of 8 posts
Postmortem: How a Bun 1.2 Runtime Bug and Node.js 22 Interop Caused Our API to Return Incorrect JSON for 30 Minutes
🖼️
0Read More

Postmortem: How a Bun 1.2 Runtime Bug and Node.js 22 Interop Caused Our API to Return Incorrect JSON for 30 Minutes

DEV Community·ANKUSH CHOUDHARY JOHAL·6 months ago
#EqhImi4N
#postmortem#runtime#node#interop#json

From Dev.to - nodejs: Postmortem: How a Bun 1.2 Runtime Bug and Node.js 22 Interop Caused Our API to Return Incorrect JSON for 30 Minutes

15s
Anatomy of a Shared Memory Bridge: How .NET Calls Java In-Process
📰
0Read More

Anatomy of a Shared Memory Bridge: How .NET Calls Java In-Process

DEV Community·JNBridge·6 months ago
#UJs1Bwyu
#java#dotnet#csharp#interop#side

A lot of Java/.NET integration advice starts with “just make it an API.” That works until the call...

15s
Chris’ Corner: Browser Feature Testing
📰
0Read More

Chris’ Corner: Browser Feature Testing

CodePen·@HashtagPLUS·6 months ago
#ttIkNkNU
#docs#browser#browsers#tests#interop

It’s interesting to me to think about during a lot of the web’s evolution, there were many different browser engines (more than there are now) and they mostly just agreed-on-paper to do…

15s
Launching Interop 2025 – Mozilla Hacks - the Web developer blog
📰
0Read More

Launching Interop 2025 – Mozilla Hacks - the Web developer blog

Mozilla Hacks – the Web developer blog·James Graham·7 months ago
#2tOLzp
#newsletterform#interop#focus#areas#platform

Interop 2025 continues the mission to make the web more consistent across browsers, building on 2024’s 95% interoperability score.

15s