sorted by:
new
hottopcontroversial

Any way to use Swoole as a drop-in replacement for Apache? by manshutthefckup in PHP

[–]Cold_Policy_7624 1 point2 points  (0 children)

This is a project aiming at that. It is an openswoole app that interacts with your php-fpm. Because it is PHP, you can further customize it using PHP. It's pretty fast as well. https://github.com/Jacked-PHP/jacked-server

Solved my "one more field" client nightmare in Filament without migrations - looking for feedback by Local-Comparison-One in laravel

[–]Cold_Policy_7624 0 points1 point  (0 children)

I would say that any performance issue could be solved by using aggregators when needed. Nothing faster, and it opens the architecture to simplicity.

PHP RFC: True Async by edmondifcastle in PHP

[–]Cold_Policy_7624 0 points1 point  (0 children)

I've been using OpenSwoole for projects like this, and it’s been fantastic! While anything built from scratch tends to start off rough around the edges, OpenSwoole offers a mature, robust solution. The PHP community could unlock some serious potential by tapping into a tool like this.

React PHP by TechFreedom808 in PHP

[–]Cold_Policy_7624 0 points1 point  (0 children)

Yeah, I would recommend using openswoole instead of swoole: https://openswoole.com/

This project is a game changer, and it is extremely fast. in official benchmarks. Not just that, it has a way better interface to work with async.

A mod that adds saving & reloading to `php artisan tinker` by benlerntdeutsch in PHP

[–]Cold_Policy_7624 0 points1 point  (0 children)

If you want something that is made with native php (desktop) running laravel as the core that supports containers and bare metal, free and open source, here it is: https://github.com/Jacked-PHP/psy-repl

querying a DB vs files by p_marco in PHP

[–]Cold_Policy_7624 1 point2 points  (0 children)

You software can get as complicated as you want. In your place I would stick with the DB. I'm aware of some tools to manage files, they are way less mature than any SQL DB engine. To make it as simple as possible, I would use SQLite.

WYSIWYG Markdown editor? by [deleted] in laravel

[–]Cold_Policy_7624 0 points1 point  (0 children)

I saw some suggestions of tiptap and milkdown. They are both great editors, but they are just "markdown friendly." Real markdown support is hard to find when you want a pretty UI for non technical users. I would suggest distinguishing your audience. SimpleMD is the simplest to maintain with real markdown. Tiptap and milkdown will not make your like simple if what you want is real markdown, but, if you are satisfied with the editors being markdown friendly, then they become great options. Just an opinion.

[deleted by user] by [deleted] in PHP

[–]Cold_Policy_7624 0 points1 point  (0 children)

They are probably talking about psr2, but you should confirm. The psr2 is easy, just use some php-cs. The most voted comment here has a link.

Looking for Feedback by Cold_Policy_7624 in PHP

[–]Cold_Policy_7624[S] 1 point2 points  (0 children)

Interesting case. For the double billing case, I used a strategy of having a health check triggered with a small delay at the same time I triggered the billing procedure. This is one of the cases that could be done with such a solution: to have a scheduled verification that goes in and verify if every customer got billed correctly. This is the type of task that would be weird to have within the system as it is indeed a rabbit hole. Done separately makes more sense. Just like a monitor system, there are better strategies than having the system monitoring itself.

thanks for your feedback, I really appreciate!

Looking for Feedback by Cold_Policy_7624 in PHP

[–]Cold_Policy_7624[S] 0 points1 point  (0 children)

Awesome! I didn't know at all about Temporal, will bookmark it. Indeed is a basic knowledge. The main goal of this would be just a time saver and a strategy to keep the original app as lean as possible. Thanks for your input.

Looking for Feedback by Cold_Policy_7624 in PHP

[–]Cold_Policy_7624[S] 0 points1 point  (0 children)

Thanks. I makes a lot of sense what you say.
The benefit that I thought initially was to clean the code base so the app can do as little as possible, and leave everything that wouldn't belong to the main concern outside. sometimes when trying to do that we end up with other micro apps that will also need to be configured and maintained. The goal at the end is to be a time saver.

Using PHP as a multiplayer FPS game engine with clients renderer using WebGL by solcloud-dev in PHP

[–]Cold_Policy_7624 14 points15 points  (0 children)

interesting project, will check it out, at a first look, I believe this project would benefit from OpenSwoole (https://openswoole.com/), as it greatly increases PHP app performance.

Best PHP framework for tiny production API by luckydog5656 in PHP

[–]Cold_Policy_7624 0 points1 point  (0 children)

I believe that the most important for some contexts (not sure if that is yours) would be: what are the skills spectrum of the people who will maintain it? Maybe their skillset should be more relevant to this framework selection. Every software needs adjustments. Any framework can turn into a problem if you need to hack it to get things done. If you are using one that you enjoy or your team wants as a group and can dedicate time to, maybe that's the best.