OmniPay VS React

Seems like it’s unrelated to OMNY. Looks like it’s just a gateway for payment https://omnipay.thephpleague.com/. Someone more dev-minded might be able to explain more, but might be worth calling your card company

check out https://omnipay.thephpleague.com/ a very extensive library supporting many multiple popular gateways like Stripe. There are many Laravel examples on github for its use.

> If their site is already Wordpress and they ask you to fix it, then your job is to fix their Wordpress site. Where is the shame and disrespect in that?

None. I just finished up such a contract myself earlier this month. I was speaking of building new sites from scratch.

> I agree about the spammy notifications and PHP code snippets. But sometimes code snippets can save time.

Put code in code files, under version control. Not in the database. Not in a blob field that gets eval()ed and is editable by users. This is sane web dev 101.

> I'd be interested to hear what good replacements there are for Wordpress+WooCommerce?

Drupal 7 + Drupal Commerce was very nice back in the day. I don't know the current state of Commerce under Drupal 9 but it's what I'd start looking at first if someone wanted me to build them a store from the ground up. Magento is still around, though I've heard that its code is incomprehensible. And if you're not afraid to take the thin framework or frameworkless route, the Omnipay library [1] combined with standard CRUD for the products should get you pretty far.

1: https://omnipay.thephpleague.com

I didn't know about this project for payment gateways from the article: https://github.com/thephpleague/omnipay

ReactPHP is a library that allows you to turn PHP into something like Go or Node.js so that tasks can be performed asynchronously. Note that ReactPHP is just a library that you install with Composer. It doesn’t have cumbersome requirements, such as installing a custom PHP extension; it just works as intended.

ReactPHP is categorized as a low-level dependency for event-driven programming. It features an event loop that supports low-level utilities, such as HTTP client/server, async DNS resolver, streams abstraction, and network client/servers.

So you could either skip the framework entirely and shave of these 10ms per request, or you could turn to something like Laravel Octane or ReactPHP to have a long running application that answers requests without bootstrapping the whole framework each time (which is what Node.js, Python or .NET applications do, the practice of restarting the whole app with every request is quite unique to the PHP community).

I remember calling out the movement to serverside of the frontend framework as reactPHP (I think it's when the remix hype first surfaced) on twitter and realized there's a literal php framework called reactPHP (https://reactphp.org/) since they liked my tweet lol.

https://reactphp.org/ of course.

You could also use something like EventMachine (In ruby), Twisted (Python), Node (JS) or ReactPHP (for PHP) that will use the language and turn it into a web application server, and then you'll have only one long running process that handle all your requests with shared memory. You could even use something more fancy like RoadRunner in the case of PHP.

Comparing PHP to NodeJS is completely wrong to begin with. If you want to compare NodeJS to something in the PHP ecosystem it would be ReactPHP.

Dunno about PHP core, but there is also ReactPHP. https://reactphp.org/

There are many micro-frameworks available like Slim, Mezzio(with Swoole may be), or if you are into async then you can also try Framework X(from core maintainer of ReactPHP). This frameworks have small footprints compare to Laravel, Symfony, etc. Yes, you can't get things like authentication, routing and other out of the box but they can easily be installed and configured to be used.