IBM i modernization, even from a strategy perspective, can be convoluted and complicated. In this blog, our expert looks at efficient and cost-effective ways to modernize your IBM i applications.
Get an overview of PHP job queueing, including commonly used tools, and ZendPHP JobQueue — a new tool that can help make PHP queueing easier than ever before.
The term “technical debt” gets thrown around a lot. Way too much, in fact. Part of that is because it has become a euphemism for “code I don’t like” or “code that predates me.” While there are reasons to dislike such code (both good and bad), that’s not what the term “technical debt” was invented to refer to.
So what does it mean? There’s several different kinds of “problematic code,” all of which come from different places.
Continue reading this post on PeakD.
Considering hiring PHP developers vs. PHP outsourcing? Want to train your team to be experts? See the benefits of each approach in this blog.
Today Xdebug turned 21.
Over these last twenty-one years Xdebug grew from a little hack to make sure PHP wouldn’t segfault when having infinite recursion, to a tool that is used by tens of thousands, if not hundreds of thousands, PHP developers.
This has mostly been the work by myself, with very few external contributions. That makes sense, as it hard to both understand the PHP engine well enough, as well as programming in C. Especially because lots of PHP internals are not actually documented.
Beyond a brief period in early 2020 when I was rewriting Xdebug to version 3, this amounts to funding for about 25 hours a month, with a steady decline.
Twenty-five hours a month is about the minimum needed to maintain Xdebug for newer versions of PHP, including support for new features, as well as triaging and fixing bugs.
If you have been following my monthly reports, you probably have noticed that there is less activity, including in creating the reports and work logs.
But there are plenty of things that should be done, and several that would make Xdebug even more powerful in streamlining debugging and improving your applications. These are also things I would like to work on.
Current features that (in my opinion) need improvement are:
The profiler is old code, and fairly messy. It is only possible to start the profiler for the whole of the request, and not only a part of it.
There are also bugs with cycle detection (function A calls function B calls function A) that need investigating.
It should be rewritten, which is luckily easier to do after Xdebug’s new modes architecture.
The current code coverage feature keeps static information about which functions have lines and paths in the same data structure as the dynamic data collection that is recorded when the script runs. This causes problems.
I have a fix, but it slows down coverage by 50%. Before I can merge it, that needs addressing.
Among the new features that I like to contribute to Xdebug are:
Native Path Mappings
Currently Xdebug does not map paths between local files, and remote and/or generated files. There are some frameworks which rewrite developer-written-classes to a new version with additional functionality, but as a different file name.
Similarly Xdebug can not translate between local and remote paths, which causes confusion such as in this PhpStorm ticket.
Introducing native path mapping would address both these issues.
An implementation could also make it possible to debug generated PHP files, say from templates. Although PhpStorm has some capabilities for this for Twig and Blade templates, it is not supported for other template systems.
A native implementation in Xdebug also could make this working better and faster for what PhpStorm already does.
Time Travel Debugging
My tongue-in-cheek April Fools’ post hinted at this already.
Time Travel Debugging would allow somebody that runs a PHP request (either you as developer, or a customer running your on-premise application) to record its whole execution, including all intermediate states (variable contents, etc.), and source files.
By having this available in one file, a wrapper could then play this back pretending it was running a live request, through already existing debugging front-ends, such as the one in PhpStorm, the PHP Debug Adapter for Visual Studio Code,
Truncated by Planet PHP, read more at the original (another 1745 bytes)