RT @benmorss: SQLite, now available in the browser!
Wasm binary is ~300K and speed is comparable to Web SQL.
Now lots of databases can add…
Educated myself about micro frontends via @AnfibiaCreativa’s site https://t.co/jmg7xXH3g4. Reading @martinfowler’s example alongside (https://t.co/39bNOJUImF) helped my understanding on top.
@RReverser @jaffathecake I made a similar remark about `response.ok` to Jake, and usually have a check like you in my code when I `fetch()`.
RT @jaffathecake: 🔠The gotchas of unhandled promise rejections, and how to work around them.
https://t.co/YLYsNBFwhU
RT @tunetheweb: After a lot of analysis we’ve published “Our top Core Web Vitals recommendations for 2023†- the 9 things (3 per CWV) that…
RT @igalia: Igalia Brings MathML Back to Chromium: Now shipping in stable (109)!
Learn more + find links to our podcast and more in
http…
RT @csswizardry: 🔖 Why Not document.write()? I’ve written up everything I currently know about what exactly makes document.write() *so* bad…
@pesterhazy @ChromiumDev See https://t.co/bizNYIxlRP: […] multi-threaded use of a single database handle is not possible in the JS environment. […] The exception is if a database is stored in persistent storage, but concurrent access to a single datab
@nelapilled @ChromiumDev In the SQLite team’s measurements, this technology was actually _faster_ than Web SQL in many cases. Be sure to check back with the team if you’re interested in learning more. They may be willing to share their benchmarks.
RT @ricmac: I check in with @slightlylate, @tomayac and @mtomweb from @OpenWebAdvocacy on three key issues for the web: 1) JavaScript perfo…
RT @ChromiumDev: The official ðŸ›¢ï¸ SQLite Wasm port, backed by the Origin Private File System for 💨 maximum performance:
https://t.co/05mEgO 
Web Audio developers rejoice: starting from Chrome 110, you can now choose the audio destination programmatically. @quicksave2k has documented the details in https://t.co/rX40SLcsUp and created a neat demo at https://t.co/5ycLSTGzCZ.
Audio to Sink B! ↘
RT @GoogleDevEurope: 💻 🌠What are the next use cases to unlocking on the web platform?
Ask @tomayac at the upcoming web meetup @GDGBerlin…
@erickoleda @ChromeDevTools Hard same, just that I built up my SOAP experience as a Google intern: I created the first AdWords PHP client library—called APIlity (word play on “ability” & “API”, no one got it)—as part of my ad-hoc self-created intern p
(If you read the source code https://t.co/Xyx9GHKBHj, don’t judge me for lack of error handling and parsing XML with RegEx in the response, because this was just a demo and also: YOLO!)
Triggered by a question regarding XML request logging in @ChromeDevTools, I created a small 🧼 SOAP API client demjagged-abrupt-baritone.glitch.meeQZ. It’s incredible we tended to do Web services this way. I used `fetch()`, but what a missed opportunity to dig opic.twitter.com/uetKv9of9n