999900000999 6 days ago

I've personally implemented Playwright in a large enterprise company. Puppeteer before that.

Generally if you have a lot of legacy selenium scripts it's probably not worth it to switch everything over, but if you're creating a new UI automation framework I've just never seen selenium as a first choice for that.

Don't get me wrong it's still solid technology though.

Reply View 1 reply
  • therunninglight 6 days ago

    yes, i've noticed some tendency for [agentic] qa services to go the puppeteer and then playwright route (sometimes either or). it's almost too easy to get running with pw. and, hence, enticing for any startup that wants to get off the ground asap and break even. seems vibium may tap into that startup market as it matures.

    legacy selenium suites are a strong contender for vibium adoption. i think hugs has been surveying a ton of folks, he may have a better bird's eye view of the potential user base.

    as for academic use of selenium, we have boni garcia - maker/popularizer or selenium webdriver manager teaching at a uni in spain. (maybe an isolated example, but he's rather known in the community)

    Reply View 0 replies
zenmac 6 days ago

Isn't Selenium vs Playwright more a Java vs JS/ES/TS thing?

Reply View 1 reply
  • hugs 6 days ago

    i started the selenium project as just a js and python thing. but it got really popular in java circles.

    vibium will also be a big tent project and support ts/js, python, java, and as many other languages we can support, too. but i started with ts/js because that's what's extremely popular right now. (and i like js!)

    (side-note: i f'ing love nim, we will be supporting nim, too. getting nim on the tiobe top 20 is on my bucket list.)

    Reply View 0 replies