It was not very long ago when Ryan McCue, the lead developer of the Rest API of this platform discussed in his blog the possible merger of REST API with WordPress core. He didn’t really say that they are going to be blended for sure but he imagined what might happen in case the merger does really take place. With the merger, he feels that more real-time features will be introduced. Here’s more:
- Presence of WordPress.org sites on major platforms like YouTube
- Easier theme development
- Addition of app directory for WordPress
Experts opine that the introduction of dependency management mechanism is inevitable – not as a fancy update but definitely because the Content Management System needs it. We are no strangers to the fact that other CMS platforms like PHP have already adopted this kind of mechanism. PHP has a Composer which can manage and resolve several libraries as a single library may require. Each PHP library which backs a Composer has a distinctive set of dependencies. The single library or Composer brings all these libraries together as a means to ensure that all these composers are well-matched with each other.
WordPress needs a Composer-like mechanism because designers and developers do not really have to work on the rediscovery of the wheel every time they want to make a new theme or plugin. The experts opine that every time they are writing a code for this purpose they are actually wasting time. Instead, they could have easily made use of the library packages out there and get over with their task in a jiffy.
The introduction of the dependency manager will actually open floodgates for the development of more and more WordPress-specific plugins. Try out some of the most popular plugins like Woocommerce, Meta slider, page builder, etc.