Nuclide vs WebStorm: What are the differences?
What is Nuclide? An open IDE for web and native mobile development, built on top of Atom (by Facebook). A unified developer experience for web and mobile development, built as a suite of packages on top of Atom to provide hackability and the support of an active community.
Nuclide and WebStorm can be categorized as "Integrated Development Environment" tools.
Some of the features offered by Nuclide are:
- Remote development. At Facebook, our web and back-end engineers work on remote development servers in our data centers. Nuclide provides a pair of packages that allow connections over SSH to a lightweight node daemon on the server, making possible remote file editing and syntax/type validation. Of course, this also works for VMs, enabling local development on HHVM, for example.
- Hack language support. The Hack codebase is one of the largest at Facebook. First-class Hack support — including syntax highlighting, type-checking, autocomplete, and click-to-symbol features — has been an important requirement on Nuclide from the start. We're also excited that the growing Hack community outside the company will be able to enjoy dedicated IDE support.
On the other hand, WebStorm provides the following key features:
- Support for React and Angular
"Remote development with SSH" is the primary reason why developers consider Nuclide over the competitors, whereas "Intelligent ide " was stated as the key factor in picking WebStorm.
Nuclide is an open source tool with 8K GitHub stars and 747 GitHub forks. Here's a link to Nuclide's open source repository on GitHub.
According to the StackShare community, WebStorm has a broader approval, being mentioned in 463 company stacks & 435 developers stacks; compared to Nuclide, which is listed in 8 company stacks and 5 developer stacks.
What is Nuclide?
What is WebStorm?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Nuclide?
What are the cons of using WebStorm?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
We use Prettier because when we rebooted our front-end stack, I decided that it would be an efficient use of our time to not worry about code formatting issues and personal preferences during peer review. Prettier eliminates this concern by auto-formatting our code to a deterministic output. We use it along with ESLint and have 1st-class support in our WebStorm and Visual Studio Code editors.
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
For all our team's coding because of its support of core libraries like angular and ruby on rails
IDE used for development of various web applications and services at Promethean.