i wish more people knew or cared about web standards vs proprietary protocols. the webdriver bidi protocol took the good parts of cdp and made it a w3c standard, but no one knows about it. some of the people who do know about it, find one thing they don't like and give up. let's not keep giving megacorporations outsized influence and control over the web and the tools we use with it. let's celebrate standards and make them awesome.
they probably meant desktop. i do browser test automation (selenium, vibium), and the lack of google chrome on arm64 trips up new users frequently. the workaround is to just use chromium, but that's a confusing extra step for some if it's not automated and hidden for you.
on that note, it would have been nice if they also clarified if this means they'll be shipping an official "chrome for testing" for arm64 linux, too.
hi, i'm jason huggins (selenium, appium, now vibium). browser automation and testing have been my jam for a long time. for most of that time, it would be fair to say browser automation was an often forgotten and overlooked corner of the tech landscape. with vibe/agentic coding, things have changed.
the folks at kernel reached out a few weeks ago about adding support for vibium and webdriver bidi on their service. it's now live on kernel.sh's crazy-fast-browsers-as-a-service.
people who have been around long enough know that we're currently in the wild west of networked agentic systems. it's an exciting time to build and explore. (just like napster and early digital music.) eventually some big company will come along and pave the cow paths and make everything safe and secure. but the people who will actually deliver that are likely playing with openclaw (and openclaw-like systems) now.
ignore the haters. this is cool. (and i've been vibe coding with claude code and termux for months. it's good stuff.)
i would highly recommend you add guidance on automated data backups, though. my pixel phone went "black screen of death" on me and one of my projects is trapped in there until i can replace the screen.
i'm vibe coding vibium, a test automation tool in the spirit of playwright and selenium. (was #1 on hn last week for a little bit with a lively discussion.)
google fell victim to one of the classic blunders. the most famous of which is inventing the transformer behind gpt but not productizing it first. but only slightly less well-known is this: letting puppeteer go without a plan.