Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project status #156

Open
bartvanhoutte opened this issue Jan 13, 2020 · 3 comments
Open

Project status #156

bartvanhoutte opened this issue Jan 13, 2020 · 3 comments

Comments

@bartvanhoutte
Copy link

Hello everybody,

I've been doing quite a bit of asynchronous PHP lately, and we could really benefit from more interoperability between ReactPHP and Amp. It looks like a lot of work is being done in both ecospheres while it seems more logical to bundle that development time.

According to the homepage of this repository, the project should be considered a failure. I'm wondering what the reasons for that were and if they still apply today? Maybe it's time to give this another go?

Cheers

@kelunik
Copy link
Member

kelunik commented Jan 13, 2020

Hey @bartvanhoutte,

ReactPHP and Amp are interoperable via amphp/react-adapter now. As stated in the README, the API proposed here has been the base for Amp v2.x.

I'm wondering what the reasons for that were and if they still apply today?

I guess the reasons were mostly two different approaches regarding the API and neither party being fine with the API of the other.

@bartvanhoutte
Copy link
Author

Hey @kelunik,

I saw the adapter but it unless I'm mistaken it does not work the other way round?

Ok, sad to hear there wasn't enough common ground to continue.

@kelunik
Copy link
Member

kelunik commented Jan 13, 2020

Yes, it doesn't, but if you're building an application, it shouldn't matter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants