Well, I probably won't be too helpful as beta tester as I'm not using anything too specific (profiler I do though), but if you can please share a pre-release with especially Fibers support, would be happy to get hands on it, thanks!

Sorry for asking - but what's the use case for me to use built-in chromium instead of 3rd party tool?
Does it somehow better integrate for javascript or PHP testing with chrome/Edge/Opera/Brave browsers ? (all based on chromium core)

I see the primary value of PhpEd in it's debugging capabilities.
It's really a pity to hold back whole release and support for PHP 8.1 for weeks - just for one single-purpose third party tool.
I believe many users are waiting for PHP 8.1 support, while upgrade for chromium v99 is not of primary value & can be done in any following release.

In many cases built-in browsers improve productivity. After all what is an IDE? Isn't in an integrated something? Technically you can use notepad-alike editor, external browsers, external cli debugging tools etc. But they wouldn't bring the same value even if they bring the same features. This value all about level of comfort and productivity.
As of delay, it's not the only feature that blocks the release. We have some unfinished work related to openssl 1.1.1 upgrade and built-in ssh client. As of Chromium, I hope to resolve it soon.

I do enjoy using the built-in Chrome browser as well so having that be upgraded is good to hear.

An annoying issue I've had for several versions now ends up occurring whenever virtual memory usage increases on my machine (I tend to run a lot of web browser tabs in my regular Chrome instance for various things I'm looking at, and even with 32 GB of RAM things still end up needing to get swapped into virtual memory after having my machine on for several weeks).

The problem with virtual memory and phpEd however is that it causes a popup to appear within the program (informing you about virtual memory getting low) and typically once it pops up it will then persistently start popping up every few seconds. Also, it's difficult to tell but sometimes if it started popping up after I've stepped away from my machine for the day and come back to it later, it feels like there have been many popups that have been queued and then start getting displayed after I click ok on the first popup (although this could simply be the internal check within phpEd running again and resulting in the subsequent popups). Suffice to say, it's pretty annoying since it makes it difficult to do any sort of work in phpEd once this starts happening and I tend to have to close it and maybe even go through the extra effort of rebooting my machine as well to get things back to normal.

A separate request I had shared some years back which fell on deaf ears is related to a small UI improvement (there was a time where I had to make use of the To Upper Case and To Lower Case options within the Edit menu and I wanted to use the the keyboard shortcuts instead (which are hidden in the manual somewhere). I don't know why it would be so hard to list the needed keyboard shortcut there in the Edit menu for users, but it's those types of small improvements that can probably be implemented without too much effort by the team that long-time users of phpEd would love to have implemented as well as the "bigger" features that are generally focused on instead.

What I generally find difficult when continuing to want to use phpEd for my future projects is that tools like PHP Storm or VS Code are being used by the top PHP developers in all of their online videos/talks, and the various open source tooling around them aren't tailored for phpEd's debugger, and there really isn't an active effort being made to blog about the ways you can implement or use the same tools and workflow with phpEd (it's kind of a complicated topic, but it would be nice to see support for that type of tooling I guess but in the integrated way we've come to enjoy from phpEd).

For example, I'd love to write more PHP packages, but I don't really feel super comfortable with the process and managing the process afterwards, so having some nice tooling for things like that and ensuring that some of the different PSRs are being followed correctly (e.g. PSR-12 let's say) might be handy to have as built-in things?

A faster development cycle would be helpful too, but might be difficult if the team size is limited right now.

I still look forward to new releases from phpEd, but in general there doesn't seem to be a ton of new awesomeness that comes in the newer releases (or it's hard to know how to use the newer features) so I just wish there was more reason to renew license subscriptions other than minor version updates of the things that come bundled with phpEd (for example, right now my license is out of renewal but I didn't renew because there hadn't been a significant new release that's arrived since I renewed early last year).

I still love phpEd because it was the main PHP IDE I started to use that made it finally easy to get started with debugging a PHP project way back when when I first tried it out (the wizard functionality that helps make that easy is a big part of that now).

What I don't like about debugging from a recent project, is that with a Laravel Livewire project it got difficult to track things using my regular phpEd debugging workflow (possibly because all of the Livewire requests resulted in AJAX calls that started up new debugging sessions) so I ended up having to make use of the Laravel dd() ("dump and die") functionality a lot more, which kind of defeated the purpose of having the more powerful phpEd debugger available.

So... can we expect the PHP 8.1 support any time soon?

Thanks again.

Seems like .. NO

@dmitri

Any idea when PHP 8.1 will be supported - are we talking weeks or months?

Thanks

@dmitri

can we please have an update? this is becoming worrying.

Thank you all for questioning. Now once I recovered and returned back to normal life, we can move forward. Let's catch up where we are:
- 19.5 will get it's update in next 1-2 days
- next version is still in beta. Haven't figured out why Chromium browser is calling google and what it is passing. The theory is it calls to check Internet status and therefore it's harmless but I need a strong confirmation and/or a way to turn this off. Any volunteers who want to check/investigate protocols and traffic created by Chromium?

@dmitri

hope everything is ok with you.

let me ask you a question - why do you care at all about Chrome? I've been using PHPEd for more than a decade and NOT ONCE I needed it.

if you explain what it is for - I'll be happy to give it a try

Until today I have only read the postings here, because my version expires in October. But have always been annoyed by the excuses of you.
With all respeckt for the very good PhpEd, but why should suffer all users who do not use Chrome?
Just write an IF clause in the installer. Chrome users are then excluded, but all others get their update to 8.1, and there are more updates needed in the future. You have enough time to work on the implementation of Chrome.
PHP is already at version 8.2 beta 1 and here Chrome is used as an excuse.

My English is not good and to avoid misunderstandings I always attach the German text as I mean it.

Bis heute habe ich hier die Postings nur gelesen, da meine Version erst im Oktober abläuft. Habe mich aber immer über die Ausflüchte von Ihnen geärgert.
Bei allem respeckt für das sehr gute PhpEd, aber warum sollen alle benutzer darunter leiden die kein Chrome benutzen?
Schreiben Sie einfach eine IF Klausel ins Installationsprogramm. Chrome benutzer sind dann ausgeschlossen, aber alle anderen bekommen ihr Update auf 8.1, und es sind ja in der Zukuft weitere Updates erforderlich. Da haben Sie genug Zeit an die Implementation von Chrome zu arbeiten.
PHP ist bereits bei Version 8.2 beta 1 und hier wird Chrome als Ausrede benutzt.

Mein englisch ist nicht gut und um Mißverständnisse zu vermeiden hänge ich immer den deutschen Text an, so wie ich es meine.

Thanks, sounds reasonable. The point is -- Chrome or more precisely Chromium, a built-in browser, is the only almost up-to-date built-in browser in PhpED. Many customers use it because it's easier to use built-in browser to debug web pages rather than external browsers that open new tab each time you click run.

As of 8.2, I'll try to include support for php-8.2beta, I mean only debugger into forthcoming version.