9 ms·

Interesting tidbit: One of the main contributors of this project[0], was the core contributor (creator?) of Puppeteer[1], but then I guess left Google to join

by syspec 5y ago

Interesting tidbit: One of the main contributors of this project[0], was the core contributor (creator?) of Puppeteer[1], but then I guess left Google to join Microsoft and work on this[2][3]. [0] - https://github.com/aslushnikov https://github.com/aslushnikov [1] - https://github.com/puppeteer/puppeteer/ https://github.com/puppeteer/puppeteer/ [2] - https://github.com/microsoft/playwright/graphs/contributors https://github.com/microsoft/playwright/graphs/contributors [3] - https://github.com/microsoft/playwright/graphs/contributors https://github.com/microsoft/playwright/graphs/contributors

vlunkr 5y ago
I wonder what the story is there. Why wouldn't MS just have him continue to work on Puppeteer? They're both open source, so there's not much point in "owning" their own clone of it.
- fikama 5y ago
  From what I know puppeter works only with chromium, this could be deal breaker for microsoft
  - jahewson 5y ago
    Edge is chromium though.
    - zamadatix 5y ago
      Microsoft's web products run on more than Edge.
      - wizzwizz4 5y ago
        They try very hard to stop you trying, though; Microsoft Teams has removed the “continue without the Teams app” button entirely on Firefox, even though I'm fairly sure it still works fine in Firefox.
        zinekeller 5y ago
        I'm assuming you're not on macOS, right? Even though Firefox supports H.264, it's not really consistent outside of macOS because Firefox doesn't want to deal with patent hassles. This is true of Slack as well, some developers would actually support if Firefox has actually have decent support, but it's inconsistent outside macOS, where it can rely on Apple's good integration. P.S. OpeH264 doesn't help mainly because it's decoding bugs, not encoding bugs.
        wizzwizz4 5y ago
        > Even though Firefox supports H.264, it's not really consistent outside of macOS because Firefox doesn't want to deal with patent hassles. That's only a concern for video chats. Teams does a lot of other stuff too, and there's no reason you shouldn't be able to use that on Firefox.
        zamadatix 5y ago
        You get the same message from macOS Firefox.
  - abraham 5y ago
    Puppeteer has experimental Firefox support. https://pptr.dev/#faq:~:text=What%20is%20the%20status%20of%20cross%2Dbrowser%20support%3F https://pptr.dev/#faq:~:text=What%20is%20the%20status%20of%2...
    - nopenopenopeno 5y ago
      I think that has been the case for a very long time.
- dzhiurgis 5y ago
  I'm exaggerating but Playwright vs Puppeteer is a bit like comparing Puppeteer with Selenium
  - whimsicalism 5y ago
    Not at all true
    - melissalobos 5y ago
      I don't really have a horse in this race, but based on the thread, why would this be wrong. Are any of these automation frameworks really different? What would be the differences? When would I use one versus the others? Especially why would I use puppeteer if it is a dead project as implied?
- throwthrow564 5y ago
  I work at Google, but this is based on stuff I knew before I worked at Google, which I heard from a coworker. I haven't checked on the project since joining. The Puppeteer TL (the guy linked in the grandparent comment) apparently had ambitions to make Puppeteer work cross browser like Playwright does now. However, the Puppeteer project was heavily deprioritized and the TL would basically never be able to achieve their vision. This made it pretty easy for Microsoft to basically take the entire Puppeteer team from Google. That coworker of mine told me also that after all those Puppeteer devs left, Puppeteer is now basically only a 20% project worked on by a few people. The number of open issues/PRs done kinda reflects that (no idea of this is still true or not)
  - whimsicalism 5y ago
    This is also my understanding.
  - hashseed 5y ago
    I manage the team at Google that currently owns the Puppeteer project. The previous team that developed Puppeteer indeed moved to Microsoft and have since started Playwright. While it is true that staffing is tight (isn't it always), the number of open issues does not tell the full story. The team has been busy with addressing technical debt that we inherited (testing, architecture, migrating to Typescript, etc) as well as investing in a standardized foundation to allow Puppeteer to work cross-browser in the future. This differs from the Playwright team's approach of shipping patched browser binaries.
    - capableweb 5y ago
      > The team has been busy with addressing technical debt that we inherited [...] migrating to Typescript Wow, not writing stuff in TypeScript is now considered technical debt? I knew people were already rushing to rewrite everything in TypeScript if they could, but didn't knew we'd come this far along the hype-cycle already.
      - eu 5y ago
pawelbylina 5y ago
[dead]

by syspec 5y ago

vlunkr 5y ago

I wonder what the story is there. Why wouldn't MS just have him continue to work on Puppeteer? They're both open source, so there's not much point in "owning" their own clone of it.

fikama 5y ago
From what I know puppeter works only with chromium, this could be deal breaker for microsoft
- jahewson 5y ago
  Edge is chromium though.
  - zamadatix 5y ago
    Microsoft's web products run on more than Edge.
    - wizzwizz4 5y ago
      They try very hard to stop you trying, though; Microsoft Teams has removed the “continue without the Teams app” button entirely on Firefox, even though I'm fairly sure it still works fine in Firefox.
      - zinekeller 5y ago
        I'm assuming you're not on macOS, right? Even though Firefox supports H.264, it's not really consistent outside of macOS because Firefox doesn't want to deal with patent hassles. This is true of Slack as well, some developers would actually support if Firefox has actually have decent support, but it's inconsistent outside macOS, where it can rely on Apple's good integration. P.S. OpeH264 doesn't help mainly because it's decoding bugs, not encoding bugs.
        wizzwizz4 5y ago
        > Even though Firefox supports H.264, it's not really consistent outside of macOS because Firefox doesn't want to deal with patent hassles. That's only a concern for video chats. Teams does a lot of other stuff too, and there's no reason you shouldn't be able to use that on Firefox.
        zamadatix 5y ago
        You get the same message from macOS Firefox.
- abraham 5y ago
  Puppeteer has experimental Firefox support. https://pptr.dev/#faq:~:text=What%20is%20the%20status%20of%20cross%2Dbrowser%20support%3F https://pptr.dev/#faq:~:text=What%20is%20the%20status%20of%2...
  - nopenopenopeno 5y ago
    I think that has been the case for a very long time.
dzhiurgis 5y ago
I'm exaggerating but Playwright vs Puppeteer is a bit like comparing Puppeteer with Selenium
- whimsicalism 5y ago
  Not at all true
  - melissalobos 5y ago
    I don't really have a horse in this race, but based on the thread, why would this be wrong. Are any of these automation frameworks really different? What would be the differences? When would I use one versus the others? Especially why would I use puppeteer if it is a dead project as implied?
throwthrow564 5y ago
I work at Google, but this is based on stuff I knew before I worked at Google, which I heard from a coworker. I haven't checked on the project since joining. The Puppeteer TL (the guy linked in the grandparent comment) apparently had ambitions to make Puppeteer work cross browser like Playwright does now. However, the Puppeteer project was heavily deprioritized and the TL would basically never be able to achieve their vision. This made it pretty easy for Microsoft to basically take the entire Puppeteer team from Google. That coworker of mine told me also that after all those Puppeteer devs left, Puppeteer is now basically only a 20% project worked on by a few people. The number of open issues/PRs done kinda reflects that (no idea of this is still true or not)
- whimsicalism 5y ago
  This is also my understanding.
- hashseed 5y ago
  I manage the team at Google that currently owns the Puppeteer project. The previous team that developed Puppeteer indeed moved to Microsoft and have since started Playwright. While it is true that staffing is tight (isn't it always), the number of open issues does not tell the full story. The team has been busy with addressing technical debt that we inherited (testing, architecture, migrating to Typescript, etc) as well as investing in a standardized foundation to allow Puppeteer to work cross-browser in the future. This differs from the Playwright team's approach of shipping patched browser binaries.
  - capableweb 5y ago
    > The team has been busy with addressing technical debt that we inherited [...] migrating to Typescript Wow, not writing stuff in TypeScript is now considered technical debt? I knew people were already rushing to rewrite everything in TypeScript if they could, but didn't knew we'd come this far along the hype-cycle already.
    - eu 5y ago

pawelbylina 5y ago

[dead]