Code Climate vs PhpStorm

Need advice about which tool to choose?Ask the StackShare community!

Code Climate

661
495
+ 1
285
PhpStorm

13.9K
10.8K
+ 1
1.6K
Add tool

Code Climate vs PhpStorm: What are the differences?

1. Cost: Code Climate offers various pricing tiers based on the size of the codebase and the features required, while PhpStorm requires a one-time purchase or a yearly subscription. This makes PhpStorm more cost-effective in the long run for individual developers or small teams. 2. Integration: Code Climate integrates seamlessly with popular version control systems like GitHub and GitLab, providing real-time feedback on code quality and test coverage. In contrast, PhpStorm has built-in version control systems support but may require additional plugins for certain integrations. 3. Code Analysis: PhpStorm features in-built static code analysis tools, while Code Climate provides a dedicated platform for code quality evaluation, security vulnerabilities detection, and code duplication detection. Code Climate offers more comprehensive code analysis features compared to PhpStorm. 4. Collaboration: Code Climate allows team members to collaboratively work on code quality improvements, set goals, and track progress, fostering a culture of continuous improvement. PhpStorm lacks robust collaboration tools specifically designed for code quality enhancement within teams. 5. Community Support: PhpStorm benefits from a strong community of developers who provide plugins, extensions, and support, enhancing the overall development experience. Code Climate, while having community support, may not offer the same level of community-driven plugins and extensions as PhpStorm. 6. IDE Features: PhpStorm is a full-fledged Integrated Development Environment (IDE) offering a wide range of features beyond code quality analysis, such as debugging, refactoring tools, and database management. Code Climate mainly focuses on code quality evaluation and lacks the comprehensive IDE features of PhpStorm.

In Summary, Code Climate and PhpStorm differ significantly in cost, integration capabilities, code analysis depth, collaboration tools, community support, and IDE features.

Advice on Code Climate and PhpStorm
Johnny Bell

When I switched to Visual Studio Code 12 months ago from PhpStorm I was in love, it was great. However after using VS Code for a year, I see myself switching back and forth between WebStorm and VS Code. The VS Code plugins are great however I notice Prettier, auto importing of components and linking to the definitions often break, and I have to restart VS Code multiple times a week and sometimes a day.

We use Ruby here so I do like that Visual Studio Code highlights that for me out of the box, with WebStorm I'd need to probably also install RubyMine and have 2 IDE's going at the same time.

Should I stick with Visual Studio Code, or switch to something else? #help

See more
Replies (15)
Erik Ostrom
Recommends
on
RubyMineRubyMine

If you're working with both Ruby and JavaScript, buy RubyMine and shut down the other two. It's much better for Ruby than Visual Studio Code is. It can also do everything WebStorm does, if you install the plugins you need from JetBrains, and they all work together nicely.

See more
Marc Swikull
Recommends
on
RubyMineRubyMine

If you install RubyMine, you shouldn't need WebStorm, as all the functionality of WebStorm appears to be included in RubyMine. (See here: https://softwareengineering.stackexchange.com/a/132950).

I've used PhpStorm for several years and have never needed to open (or even download) WebStorm for anything front-end or JavaScript related.

See more
Russel Werner
Lead Engineer at StackShare · | 6 upvotes · 262.3K views
Recommends
on
WebStormWebStorm
at

I work at the same company as you and I use WebStorm for 99% of my tasks. I also have RubyMine installed and use that when I have to tweak some backend code. I tried using RubyMine for JavaScript but was unhappy with how it felt and I believe that WebStorm is faster because it has less plugins and language extensions running. Summary: Buy and use WebStorm for primary development and keep VS Code around for when you have to touch Ruby.

See more
Danny Battison
Recommends
on
PhpStormPhpStorm

JetBrains all the way - my entire team uses PhpStorm and none of us would even consider switching.

The availability of IDEs for other languages along with consistency in environment and keyboard shortcuts is also a godsend, which is the reason I'd also choose Rider over Visual Studio (but also VS for Mac is trash, but I digress...)

See more
Recommends
on
Visual Studio CodeVisual Studio Code

I've never had much issue running multiple IDEs and generally pick them based on the languages they best support. For front end work where I mainly use TypeScript, I stick heavily with Visual Studio Code. However, for backend work which we do primarily in Python, PyCharm is my go-to editor. The one thing that I do however is I do remap keyboard shortcuts so I get consistent keyboard ability even when I switch IDEs.

See more
Recommends
on
Visual Studio CodeVisual Studio Code

Visual Studio Code is a text editor. And this is best option in my opinion. For Ruby, I cannot say how VS Code is good. If you wanna choose IDE, RubyMine should fit your needs. Because IDEs are more compatible with major needs. But text editors are just text editor. You can do same things with also text editors. I recommend to try both VS Code and RubyMine. And you will be able to find which fits better for your needs

See more
Recommends
on
Visual Studio CodeVisual Studio Code

If I have to choose one I would go with VS Code; it’s become pretty mature and keeps getting better. If those plugins are creating problems for you then just uninstall them, find an alternative, or make a PR to fix. But at the end of the day these are IDE’s and they are meant to save you time. I would go with whatever helps you develop code faster. If restarting VS code slows you down then make a switch, that personally would annoying the crap out of me. Else maybe it’s a quick restart, not the end of the word, hopefully someone will fix at some point.

See more
Recommends
on
PhpStormPhpStorm

So here is the deal man, bottom line you want to write code. All of these tools are built in a mouse-driven world, they are designed not for engineers, but office monkeys. If you want a real workflow that gives you ultimate performance, customization and speed you need to use a modal editor, I suggest NeoVim. Start using it 20% of the time on single file edits, watch youtube videos about it and teach yourself vim gestures. It will infuriate you for 6 weeks, make you cry for another 2 months. But as you use it more, as long as your usage goes over 40% of the time, in 6 months you will understand why most of the world's too engineers use it. Settling on lesser editors out of laziness is exactly the attitude that results in shitty the engineering. Yeah it's hard. You're smart. You do hard things. Once it isn't hard anymore you will blow yourself away at how much more efficiently you edit files.

Also vim keybindings in a mouse driven editor does not cut it. Managing files, buffers and workflow is half of the value of vim/neovim. It is OK if you have to use an IDE (currently I only use an IDE for java development, so I have little choice)

So use VSCode while you teach yourself vim.

See more
Lungu Alexandru-Mihai
Recommends
on
VimVim

Well you can try for a while MacVim because it is already configured with tons of plugins. My favourite text editors are Sublime Text and TextMate which are lightweight and speedy. My feeling is that JetBrains IDEs are making you brainless.

See more
Kyle Schoonover
Senior Software Engineer at Nordstrom · | 2 upvotes · 225K views
Recommends
on
Visual Studio CodeVisual Studio Code

I'm personally a Visual Studio Code fan. I've used it for both Go and Java. It really depends on the quality and support of the plugins. Typically VS Code doesn't crash as much as a bad plugin causes an unforeseen error. Make sure you stay up to date and look at alternative plugins.

See more
Recommends
at

Visiual Studio is the best

See more
Recommends
on
Visual Studio CodeVisual Studio Code

If you find something that works and are comfortable with it, stay with it. Changing IDE's and learning their idiosyncrasies takes valuable time away from programming while learning setups and keyboard short cuts. I personally use VS Code for cost and decent multiple language support. I've had issues occasionally with it locking up, but it is under heavy development and continually improving. I have also found it more intuitive for new programmers. ** Having profiles for different languages can reduce the amount of plugins running and issues they can cause.

See more
Recommends
on
PhpStormPhpStorm

I usually have both running but do the bulk of my language work in the appropriate JetBrains flavor. One thing to watch out for in VS is that under the hood it is running the tools needed for whatever language you are working with. This is where tools like JetBrains shine. While I am sure you can tune the heck out of what you use in VS, the provides context and clarity...

See more
Recommends

An integrated development environment software with huge potential in the future is VS Code. So I would personally say you can use VS code.

See more
Recommends
on
Visual Studio CodeVisual Studio Code

Are you using the prettier-vscode VSCode extension or prettier via prettier-eslint? The prettier-vscode extension recommends you...

Use prettier-eslint instead of prettier. Other settings will only be fallbacks in case they could not be inferred from ESLint rules.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Code Climate
Pros of PhpStorm
  • 71
    Auto sync with Github
  • 49
    Simple grade system that motivates to keep code clean
  • 45
    Better coding
  • 30
    Free for open source
  • 21
    Hotspots for quick refactoring candidates
  • 15
    Continued encouragement to a have better / cleaner code
  • 13
    Great UI
  • 11
    Makes you a better coder
  • 10
    Duplication Detection
  • 5
    Safe and Secure
  • 2
    Private
  • 2
    Extremely accurate in telling you the errors
  • 2
    GitHub only
  • 2
    Python inspection
  • 2
    Great open community
  • 2
    GitHub integration, status inline in PRs
  • 2
    Uses rubocop
  • 1
    Locally Installable API
  • 287
    Best ide for php
  • 232
    Easy to use
  • 218
    Functionality
  • 166
    Plugins
  • 160
    Code analysis
  • 87
    Integrated version control
  • 76
    Great php ide for mac
  • 73
    All-round php ide
  • 62
    Local history
  • 53
    Themes
  • 18
    Best PHP IDE
  • 11
    Database control
  • 10
    Easy to find anything and everything in your code
  • 9
    Best bebugging
  • 9
    Best inspection variable
  • 7
    Command line integration
  • 7
    Great frameworks integration
  • 7
    PHPUnit integration
  • 7
    Getting Better
  • 7
    UX
  • 6
    Composer integration
  • 6
    Performance
  • 6
    Coolest IDE
  • 5
    Real time code validation
  • 5
    Easy to use and github interaction
  • 5
    Neat does the job and easy
  • 5
    Best ide for advanced php and symfony
  • 4
    Best ide for php
  • 4
    TypeScript support
  • 4
    Code indexing
  • 4
    It has no match. it filled one of the biggest void
  • 4
    Fast and relevant auto-complete
  • 4
    Great refactoring support
  • 4
    Cross platform
  • 3
    Integration with Vagrant and Docker
  • 3
    Debugger for Javascript
  • 3
    Good
  • 3
    Very good
  • 2
    Debugging in the Just-In-Time Mode
  • 2
    Perfect locahost / host sync
  • 2
    Awesome debugging features

Sign up to add or upvote prosMake informed product decisions

Cons of Code Climate
Cons of PhpStorm
  • 2
    Learning curve, static analysis comparable to eslint
  • 1
    Complains about small stylistic decisions
  • 14
    Uses a lot of memory
  • 10
    Does not open large files
  • 9
    Slow
  • 8
    Uses Java machine
  • 3
    No way to change syntax highlight for files without ext
  • 2
    No save prompt or asterisk on file change

Sign up to add or upvote consMake informed product decisions

What is Code Climate?

After each Git push, Code Climate analyzes your code for complexity, duplication, and common smells to determine changes in quality and surface technical debt hotspots.

What is PhpStorm?

PhpStorm is a PHP IDE which keeps up with latest PHP & web languages trends, integrates a variety of modern tools, and brings even more extensibility with support for major PHP frameworks.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Code Climate?
What companies use PhpStorm?
See which teams inside your own company are using Code Climate or PhpStorm.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Code Climate?
What tools integrate with PhpStorm?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

GitHubPythonNode.js+26
29
15975
GitHubMySQLSlack+44
109
50680
What are some alternatives to Code Climate and PhpStorm?
Codacy
Codacy automates code reviews and monitors code quality on every commit and pull request on more than 40 programming languages reporting back the impact of every commit or PR, issues concerning code style, best practices and security.
Codecov
Our patrons rave about our elegant coverage reports, integrated pull request comments, interactive commit graphs, our Chrome plugin and security.
Coveralls
Coveralls works with your CI server and sifts through your coverage data to find issues you didn't even know you had before they become a problem. Free for open source, pro accounts for private repos, instant sign up with GitHub OAuth.
SonarQube
SonarQube provides an overview of the overall health of your source code and even more importantly, it highlights issues found on new code. With a Quality Gate set on your project, you will simply fix the Leak and start mechanically improving.
GitPrime
GitPrime uses data from GitHub, GitLab, BitBucket—or any Git based code repository—to help engineering leaders move faster, optimize work patterns, and advocate for engineering with concrete data.
See all alternatives