As any other archiving solution, it is very well suited for environments with a large footprint of unstructured data (CIFS / NFS shares for user data) with a large amount of unused/old files and a need to keep those unused files for long term. In our scenario, due to some legal and contractual constraints we need to keep these files for 15 years. Archiving is a good choice to move the unused files to a cheaper storage tier, both on-prem or cloud.
PhpStorm is well suited for any project that utilizes PHP. I have used it on Windows, Ubuntu, and Mac OS and it works great on all those platforms. Having a solution that keeps the developer from having to constantly switch tools to do their job is invaluable. Whether you're a junior developer, front end engineer or a senior developer, PhpStorm is a great product that will help you get your work done.
Database browsing, Remote host browsing, and all the deep seated customizations for both the UI and Technical feasability are the result of an amazing integrity and compatibility with most components and technologies.
The built-in shell is insanely helpful for traversing code in order to debug scripts with ease, and the plug-in system makes this software quite extensible.
Not to mention the variety of options and settings (divided into global settings and per-project settings) are both intuitive & easy to use, especially the fact that I can export and import them across my workstations while maintaining my spacing & indentation, highlighting, inspection patterns and syntax styling.
Some of the newest github copilot features lag behind what's being done in vs code and would be nice if more of the newer features were brought over though this has greatly improved recently
Interface can be a little overwhelming for newcomers
Some features like rainbow brackets should be native rather than addon
PhpStorm is very easy to use, once you get the hang of it. It can take a while to get the hang of it because there's so many options, some of which are buried in the imposing settings panel. It could use some help with multi-cursor, especially multi-file editing but that's a minor gripe.
The JetBrains community is all about helping others succeed, even in the most obscure setups. I have never had a question go unanswered, or I have never been able to come up with empty results in searching for the answer. My questions or concerns are typically address from other users in the community, so timing is pretty quick for a response
We have used Veritas Enterprise Vault in the past, and besides its being a well-known player on the data archiving market, their tool is far more complex to implement, to manage and to keep working. Komprise is very robust and also very easy to implement, as most part of the job is done on Komprise side. The management console is delivered through a public URL as a SaaS platform. You only need to deploy a few VMs for scan/archiving/user access, which they call "Observer VMs." Komprise also doesn't uses Stub files, which is a poor implementation adopted by the competitor for file access. We had a lot of issues in the past with stub files. Komprise has implemented 'bread crumbs', which are CIFS symlinks to the files on the Observer. It is a very good implementation and it works really well.
Easier to use, more features, more reliable. Much more purpose built with specific integrations aimed directly at php code instead of the broad generic interfaces the other software have that are aiming to support many different languages.
PhpStorm decreased the time to market of new features - we are following the Agile SCRUM methodology with 2 weeks sprints. Using PhpStorm helped with releasing UI features even faster than 2 weeks.
Considering the price of the license and the cost of the server where we run it, the ROI is still high due to less time spent by developers with writing code, debugging, refactoring etc. Especially when you have highly paid developers.
Increased people's happiness - by using a modern tool with lots of features which has made their work easier.
