Alternatives to WebStorm logo

Alternatives to WebStorm

PhpStorm, Atom, Visual Studio Code, Sublime Text, and PyCharm are the most popular alternatives and competitors to WebStorm.
13.3K
10.5K
+ 1
985

What is WebStorm and what are its top alternatives?

WebStorm is a popular integrated development environment (IDE) for web development, offering features such as code completion, refactoring, and debugging tools. It supports a wide range of web technologies and frameworks, making it a versatile choice for web developers. However, WebStorm can be resource-intensive and may have a steeper learning curve compared to other IDEs.

  1. Visual Studio Code: Visual Studio Code is a lightweight, open-source IDE with a wide range of extensions and support for multiple programming languages. Its key features include code debugging, version control integration, and an active community for support. Pros include its speed and customizable interface, while cons may include occasional instability.
  2. IntelliJ IDEA: IntelliJ IDEA is another IDE developed by JetBrains, the same company behind WebStorm. It offers advanced code analysis, refactoring tools, and support for various languages and frameworks. Pros include its robust feature set and excellent performance, while cons may include its price for the ultimate edition.
  3. Sublime Text: Sublime Text is a popular text editor known for its speed and efficiency. It offers a distraction-free writing environment, customizable interface, and a wide range of third-party packages. Pros include its speed and extensive plugin ecosystem, while cons may include lack of built-in debugging tools.
  4. Atom: Atom is a free, open-source text editor developed by GitHub. It features a user-friendly interface, package manager, and support for various programming languages. Pros include its flexibility and community-driven development, while cons may include occasional performance issues.
  5. Eclipse: Eclipse is a versatile IDE with support for multiple languages and platforms. It offers features such as code completion, refactoring, and a plugin system for extending functionality. Pros include its flexibility and extensive plugin ecosystem, while cons may include a steep learning curve for beginners.
  6. NetBeans: NetBeans is an open-source IDE for Java development, offering features such as code templates, refactoring tools, and support for multiple languages. Pros include its ease of use and robust debugging capabilities, while cons may include occasional performance issues.
  7. Komodo IDE: Komodo IDE is a cross-platform IDE with support for multiple languages and frameworks. It offers features such as code intelligence, debugging tools, and version control integration. Pros include its comprehensive feature set and flexible customization options, while cons may include its price.
  8. Brackets: Brackets is an open-source text editor focused on web development, with features such as live preview, preprocessor support, and inline editing. Pros include its lightweight and user-friendly interface, while cons may include limited extensibility compared to other IDEs.
  9. Code::Blocks: Code::Blocks is a free and open-source IDE for C, C++, and Fortran development, offering features such as code completion, debugging tools, and project management capabilities. Pros include its simplicity and cross-platform support, while cons may include a less polished user interface.
  10. Aptana Studio: Aptana Studio is an open-source IDE for web development, offering features such as code editing, debugging tools, and project deployment capabilities. Pros include its integration with popular web technologies and strong community support, while cons may include occasional stability issues.

Top Alternatives to WebStorm

  • PhpStorm
    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. ...

  • Atom
    Atom

    At GitHub, we're building the text editor we've always wanted. A tool you can customize to do anything, but also use productively on the first day without ever touching a config file. Atom is modern, approachable, and hackable to the core. We can't wait to see what you build with it. ...

  • Visual Studio Code
    Visual Studio Code

    Build and debug modern web and cloud applications. Code is free and available on your favorite platform - Linux, Mac OSX, and Windows. ...

  • Sublime Text
    Sublime Text

    Sublime Text is available for OS X, Windows and Linux. One license is all you need to use Sublime Text on every computer you own, no matter what operating system it uses. Sublime Text uses a custom UI toolkit, optimized for speed and beauty, while taking advantage of native functionality on each platform. ...

  • PyCharm
    PyCharm

    PyCharm’s smart code editor provides first-class support for Python, JavaScript, CoffeeScript, TypeScript, CSS, popular template languages and more. Take advantage of language-aware code completion, error detection, and on-the-fly code fixes! ...

  • Eclipse
    Eclipse

    Standard Eclipse package suited for Java and plug-in development plus adding new plugins; already includes Git, Marketplace Client, source code and developer documentation. Click here to file a bug against Eclipse Platform. ...

  • JavaScript
    JavaScript

    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles. ...

  • Git
    Git

    Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. ...

WebStorm alternatives & related posts

PhpStorm logo

PhpStorm

14K
10.9K
1.6K
Professional IDE for PHP and Web Developers
14K
10.9K
+ 1
1.6K
PROS OF PHPSTORM
  • 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
CONS OF PHPSTORM
  • 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

related PhpStorm posts

Johnny Bell

I've been in the #frontend game for about 7 years now. I started coding in Sublime Text because all of the tutorials I was doing back then everyone was using it. I found the speed amazing compared to some other tools at the time. I kept using Sublime Text for about 4-5 years.

I find Sublime Text lacks some functionality, after all it is just a text editor rather than a full fledged IDE. I finally converted over to PhpStorm as I was working with Magento and Magento as you know is mainly #PHP based.

This was amazing all the features in PhpStorm I loved, the debugging features, and the control click feature when you click on a dependency or linked file it will take you to that file. It was great.

PhpStorm is kind of slow, I found that Prettier was taking a long time to format my code, and it just was lagging a lot so I was looking for alternatives. After watching some more tutorial videos I noticed that everyone was using Visual Studio Code. So I gave it a go, and its amazing.

It has support for everything I need with the plugins and the integration with Git is amazing. The speed of this IDE is blazing fast, and I wouldn't go back to using PhpStorm anymore. I highly recommend giving Visual Studio Code a try!

See more
Denys
Software engineer at Typeform · | 13 upvotes · 1.8M views
  • Go because it's easy and simple, facilitates collaboration , and also it's fast, scalable, powerful.
  • Visual Studio Code because it has one of the most sophisticated Go language support plugins.
  • Vim because it's Vim
  • Git because it's Git
  • Docker and Docker Compose because it's quick and easy to have reproducible builds/tests with them
  • Arch Linux because Docker for Mac/Win is a disaster for the human nervous system, and Arch is the coolest Linux distro so far
  • Stack Overflow because of Copy-Paste Driven Development
  • JavaScript and Python when a something needs to be coded for yesterday
  • PhpStorm because it saves me like 300 "Ctrl+F" key strokes a minute
  • cURL because terminal all the way
See more
Atom logo

Atom

16.8K
14.4K
2.5K
A hackable text editor for the 21st Century
16.8K
14.4K
+ 1
2.5K
PROS OF ATOM
  • 529
    Free
  • 449
    Open source
  • 343
    Modular design
  • 321
    Hackable
  • 316
    Beautiful UI
  • 147
    Backed by github
  • 119
    Built with node.js
  • 113
    Web native
  • 107
    Community
  • 35
    Packages
  • 18
    Cross platform
  • 5
    Nice UI
  • 5
    Multicursor support
  • 5
    TypeScript editor
  • 3
    Open source, lots of packages, and so configurable
  • 3
    cli start
  • 3
    Simple but powerful
  • 3
    Chrome Inspector works IN EDITOR
  • 3
    Snippets
  • 2
    Code readability
  • 2
    It's powerful
  • 2
    Awesome
  • 2
    Smart TypeScript code completion
  • 2
    Well documented
  • 1
    works with GitLab
  • 1
    "Free", "Hackable", "Open Source", The Awesomness
  • 1
    full support
  • 1
    vim support
  • 1
    Split-Tab Layout
  • 1
    Apm publish minor
  • 1
    Consistent UI on all platforms
  • 1
    User friendly
  • 1
    Hackable and Open Source
  • 0
    Publish
CONS OF ATOM
  • 19
    Slow with large files
  • 7
    Slow startup
  • 2
    Most of the time packages are hard to find.
  • 1
    No longer maintained
  • 1
    Cannot Run code with F5
  • 1
    Can be easily Modified

related Atom posts

Jerome Dalbert
Principal Backend Software Engineer at StackShare · | 13 upvotes · 920.2K views

I liked Sublime Text for its speed, simplicity and keyboard shortcuts which synergize well when working on scripting languages like Ruby and JavaScript. I extended the editor with custom Python scripts that improved keyboard navigability such as autofocusing the sidebar when no files are open, or changing tab closing behavior.

But customization can only get you so far, and there were little things that I still had to use the mouse for, such as scrolling, repositioning lines on the screen, selecting the line number of a failing test stack trace from a separate plugin pane, etc. After 3 years of wearily moving my arm and hand to perform the same repetitive tasks, I decided to switch to Vim for 3 reasons:

  • your fingers literally don’t ever need to leave the keyboard home row (I had to remap the escape key though)
  • it is a reliable tool that has been around for more than 30 years and will still be around for the next 30 years
  • I wanted to "look like a hacker" by doing everything inside my terminal and by becoming a better Unix citizen

The learning curve is very steep and it took me a year to master it, but investing time to be truly comfortable with my #TextEditor was more than worth it. To me, Vim comes close to being the perfect editor and I probably won’t need to switch ever again. It feels good to ignore new editors that come out every few years, like Atom and Visual Studio Code.

See more
Julian Sanchez
Lead Developer at Chore Champion · | 9 upvotes · 774.3K views

We use Visual Studio Code because it allows us to easily and quickly integrate with Git, much like Sublime Merge ,but it is integrated into the IDE. Another cool part about VS Code is the ability collaborate with each other with Visual Studio Live Share which allows our whole team to get more done together. It brings the convenience of the Google Suite to programming, offering something that works more smoothly than anything found on Atom or Sublime Text

See more
Visual Studio Code logo

Visual Studio Code

176.2K
160.7K
2.3K
Build and debug modern web and cloud applications, by Microsoft
176.2K
160.7K
+ 1
2.3K
PROS OF VISUAL STUDIO CODE
  • 340
    Powerful multilanguage IDE
  • 308
    Fast
  • 193
    Front-end develop out of the box
  • 158
    Support TypeScript IntelliSense
  • 142
    Very basic but free
  • 126
    Git integration
  • 106
    Intellisense
  • 78
    Faster than Atom
  • 53
    Better ui, easy plugins, and nice git integration
  • 45
    Great Refactoring Tools
  • 44
    Good Plugins
  • 42
    Terminal
  • 38
    Superb markdown support
  • 36
    Open Source
  • 35
    Extensions
  • 26
    Awesome UI
  • 26
    Large & up-to-date extension community
  • 24
    Powerful and fast
  • 22
    Portable
  • 18
    Best editor
  • 18
    Best code editor
  • 17
    Easy to get started with
  • 15
    Lots of extensions
  • 15
    Good for begginers
  • 15
    Crossplatform
  • 15
    Built on Electron
  • 14
    Open, cross-platform, fast, monthly updates
  • 14
    Extensions for everything
  • 14
    All Languages Support
  • 13
    Easy to use and learn
  • 12
    Extensible
  • 12
    "fast, stable & easy to use"
  • 11
    Ui design is great
  • 11
    Useful for begginer
  • 11
    Totally customizable
  • 11
    Git out of the box
  • 11
    Faster edit for slow computer
  • 10
    SSH support
  • 10
    Great community
  • 10
    Fast Startup
  • 9
    Great language support
  • 9
    It has terminal and there are lots of shortcuts in it
  • 9
    Works With Almost EveryThing You Need
  • 9
    Powerful Debugger
  • 8
    Can compile and run .py files
  • 8
    Python extension is fast
  • 7
    Great document formater
  • 7
    Features rich
  • 6
    He is not Michael
  • 6
    Awesome multi cursor support
  • 6
    She is not Rachel
  • 6
    Extension Echosystem
  • 5
    VSCode.pro Course makes it easy to learn
  • 5
    SFTP Workspace
  • 5
    Very proffesional
  • 5
    Language server client
  • 5
    Easy azure
  • 4
    Has better support and more extentions for debugging
  • 4
    Supports lots of operating systems
  • 4
    Virtualenv integration
  • 4
    Excellent as git difftool and mergetool
  • 3
    Emmet preinstalled
  • 3
    More tools to integrate with vs
  • 3
    Has more than enough languages for any developer
  • 3
    Better autocompletes than Atom
  • 3
    'batteries included'
  • 2
    Microsoft
  • 2
    Light
  • 2
    Big extension marketplace
  • 2
    CMake support with autocomplete
  • 2
    Fast and ruby is built right in
  • 2
    VS Code Server: Browser version of VS Code
  • 2
    Customizable
CONS OF VISUAL STUDIO CODE
  • 46
    Slow startup
  • 29
    Resource hog at times
  • 20
    Poor refactoring
  • 13
    Poor UI Designer
  • 11
    Weak Ui design tools
  • 10
    Poor autocomplete
  • 8
    Super Slow
  • 8
    Huge cpu usage with few installed extension
  • 8
    Microsoft sends telemetry data
  • 7
    Poor in PHP
  • 6
    It's MicroSoft
  • 3
    Poor in Python
  • 3
    No Built in Browser Preview
  • 3
    No color Intergrator
  • 3
    Very basic for java development and buggy at times
  • 3
    No built in live Preview
  • 3
    Electron
  • 2
    Bad Plugin Architecture
  • 2
    Powered by Electron
  • 1
    Terminal does not identify path vars sometimes
  • 1
    Slow C++ Language Server

related Visual Studio Code posts

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 4M views

I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

See more
Yshay Yaacobi

Our first experience with .NET core was when we developed our OSS feature management platform - Tweek (https://github.com/soluto/tweek). We wanted to create a solution that is able to run anywhere (super important for OSS), has excellent performance characteristics and can fit in a multi-container architecture. We decided to implement our rule engine processor in F# , our main service was implemented in C# and other components were built using JavaScript / TypeScript and Go.

Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.

After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...

See more
Sublime Text logo

Sublime Text

33.3K
27.3K
4K
A sophisticated text editor for code, markup and prose.
33.3K
27.3K
+ 1
4K
PROS OF SUBLIME TEXT
  • 720
    Lightweight
  • 652
    Plugins
  • 641
    Super fast
  • 468
    Great code editor
  • 442
    Cross platform
  • 280
    Nice UI
  • 260
    Unlimited trial
  • 153
    Cmd + d is the best command ever
  • 92
    Great community
  • 46
    Package control, modules
  • 26
    Mac OS X support
  • 23
    Easy to get started with
  • 22
    Monokai
  • 21
    Everything you need without the bloat
  • 21
    Built in Python
  • 18
    Easy
  • 14
    Speed
  • 12
    Session & edit resuming
  • 10
    Package Control
  • 9
    Well Designed
  • 8
    Multiple selections
  • 7
    ALT + CMD + DOWN is the best command ever
  • 7
    Nice
  • 7
    Fast, simple and lightweight
  • 5
    It's easy to use, beautiful, simple, and plugins rule
  • 5
    So futuristic and convenient
  • 5
    ALT + F3 the best command ever
  • 5
    Great
  • 4
    Find anything fast within entire project
  • 4
    Easy to use
  • 4
    Free
  • 4
    Simple and clean design
  • 3
    Hackable
  • 3
    Pretty
  • 3
    UI + plugins
  • 3
    Sublime Merge (Git Integration)
  • 2
    Totally customizable
  • 2
    Color schemes and cmd+d
  • 2
    Material theme best theme forever
  • 0
    Const
CONS OF SUBLIME TEXT
  • 8
    Steep learning curve
  • 6
    Everything
  • 4
    Flexibility to move file
  • 4
    Number of plugins doing the same thing
  • 4
    Doesn't act like a Mac app
  • 3
    Not open sourced
  • 2
    Don't have flutter integration
  • 2
    Forces you to buy license

related Sublime Text posts

Johnny Bell

I've been in the #frontend game for about 7 years now. I started coding in Sublime Text because all of the tutorials I was doing back then everyone was using it. I found the speed amazing compared to some other tools at the time. I kept using Sublime Text for about 4-5 years.

I find Sublime Text lacks some functionality, after all it is just a text editor rather than a full fledged IDE. I finally converted over to PhpStorm as I was working with Magento and Magento as you know is mainly #PHP based.

This was amazing all the features in PhpStorm I loved, the debugging features, and the control click feature when you click on a dependency or linked file it will take you to that file. It was great.

PhpStorm is kind of slow, I found that Prettier was taking a long time to format my code, and it just was lagging a lot so I was looking for alternatives. After watching some more tutorial videos I noticed that everyone was using Visual Studio Code. So I gave it a go, and its amazing.

It has support for everything I need with the plugins and the integration with Git is amazing. The speed of this IDE is blazing fast, and I wouldn't go back to using PhpStorm anymore. I highly recommend giving Visual Studio Code a try!

See more
Labinator Team

At labinator.com, we use HTML5, CSS 3, Sass, Vanilla.JS and PHP when building our premium WordPress themes and plugins. When writing our codes, we use Sublime Text and Visual Studio Code depending on the project. We run Manjaro and Debian operating systems in our office. Manjaro is a great desktop operating system for all range of tasks while Debian is a solid choice for servers.

WordPress became a very popular choice when it comes to content management systems and building websites. It is easy to learn and has a great community behind it. The high number of plugins as well that are available for WordPress allows any user to customize it depending on his/her needs.

For development, HTML5 with Sass is our go-to choice when building our themes.

Main Advantages Of Sass:

  • It's CSS syntax friendly
  • It offers variables
  • It uses a nested syntax
  • It includes mixins
  • Great community and online support.
  • Great documentation that is easy to read and follow.

As for PHP, we always thrive to use PHP 7.3+. After the introduction of PHP 7, the WordPress development process became more stable and reliable than before. If you a developer considering PHP 7.3+ for your project, it would be good to note the following benefits.

The Benefits Of Using PHP:

  • Open Source.
  • Highly Extendible.
  • Easy to learn and read.
  • Platform independent.
  • Compatible with APACHE.
  • Low development and maintenance cost.
  • Great community and support.
  • Detailed documentation that has everything you need!

Why PHP 7.3+?

  • Flexible Heredoc & Nowdoc Syntaxes - Two key methods for defining strings within PHP. They also became easier to read and more reliable.
  • A good boost in performance speed which is extremely important when it comes to WordPress development.
See more
PyCharm logo

PyCharm

27.6K
23.4K
451
The Most Intelligent Python IDE
27.6K
23.4K
+ 1
451
PROS OF PYCHARM
  • 112
    Smart auto-completion
  • 93
    Intelligent code analysis
  • 77
    Powerful refactoring
  • 60
    Virtualenv integration
  • 54
    Git integration
  • 22
    Support for Django
  • 11
    Multi-database integration
  • 7
    VIM integration
  • 4
    Vagrant integration
  • 3
    In-tool Bash and Python shell
  • 2
    Plugin architecture
  • 2
    Docker
  • 1
    Django Implemented
  • 1
    Debug mode support docker
  • 1
    Emacs keybinds
  • 1
    Perforce integration
CONS OF PYCHARM
  • 10
    Slow startup
  • 7
    Not very flexible
  • 6
    Resource hog
  • 3
    Periodic slow menu response
  • 1
    Pricey for full features

related PyCharm posts

christy craemer

UPDATE: Thanks for the great response. I am going to start with VSCode based on the open source and free version that will allow me to grow into other languages, but not cost me a license ..yet.

I have been working with software development for 12 years, but I am just beginning my journey to learn to code. I am starting with Python following the suggestion of some of my coworkers. They are split between Eclipse and IntelliJ IDEA for IDEs that they use and PyCharm is new to me. Which IDE would you suggest for a beginner that will allow expansion to Java, JavaScript, and eventually AngularJS and possibly mobile applications?

See more

I am a QA heading to a new company where they all generally use Visual Studio Code, my experience is with IntelliJ IDEA and PyCharm. The language they use is JavaScript and so I will be writing my test framework in javaScript so the devs can more easily write tests without context switching.

My 2 questions: Does VS Code have Cucumber Plugins allowing me to write behave tests? And more importantly, does VS Code have the same refactoring tools that IntelliJ IDEA has? I love that I have easy access to a range of tools that allow me to refactor and simplify my code, making code writing really easy.

See more
Eclipse logo

Eclipse

2.6K
2.2K
392
IDE for Java EE Developers
2.6K
2.2K
+ 1
392
PROS OF ECLIPSE
  • 131
    Does it all
  • 76
    Integrates with most of tools
  • 64
    Easy to use
  • 63
    Java IDE
  • 32
    Best Java IDE
  • 9
    Open source
  • 3
    Hard for newbews
  • 2
    Great gdb integration
  • 2
    Professional
  • 2
    Good Git client allowing direct stage area edit
  • 2
    True open source with huge contribution
  • 2
    Great code suggestions
  • 2
    Extensible
  • 2
    Lightweight
  • 0
    Works with php
CONS OF ECLIPSE
  • 14
    2000 Design
  • 9
    Bad performance
  • 4
    Hard to use

related Eclipse posts

christy craemer

UPDATE: Thanks for the great response. I am going to start with VSCode based on the open source and free version that will allow me to grow into other languages, but not cost me a license ..yet.

I have been working with software development for 12 years, but I am just beginning my journey to learn to code. I am starting with Python following the suggestion of some of my coworkers. They are split between Eclipse and IntelliJ IDEA for IDEs that they use and PyCharm is new to me. Which IDE would you suggest for a beginner that will allow expansion to Java, JavaScript, and eventually AngularJS and possibly mobile applications?

See more
Dean Stringer

Have been a Visual Studio Code user since just after launch to the general public, having used the likes of Eclipse and Atom previously. Was amazed how mature it seemed off the bat and was super intrigued by the bootstrapped nature of it having been written/based on Electron/TypeScript, and of course being an open-source app from Microsoft. The features, plugin ecosystem and release frequency are very impressive. I do dev work on both Mac and Windows and don't use anything else now as far as IDEs go.

See more
JavaScript logo

JavaScript

354.5K
269.6K
8.1K
Lightweight, interpreted, object-oriented language with first-class functions
354.5K
269.6K
+ 1
8.1K
PROS OF JAVASCRIPT
  • 1.7K
    Can be used on frontend/backend
  • 1.5K
    It's everywhere
  • 1.2K
    Lots of great frameworks
  • 897
    Fast
  • 745
    Light weight
  • 425
    Flexible
  • 392
    You can't get a device today that doesn't run js
  • 286
    Non-blocking i/o
  • 237
    Ubiquitousness
  • 191
    Expressive
  • 55
    Extended functionality to web pages
  • 49
    Relatively easy language
  • 46
    Executed on the client side
  • 30
    Relatively fast to the end user
  • 25
    Pure Javascript
  • 21
    Functional programming
  • 15
    Async
  • 13
    Full-stack
  • 12
    Setup is easy
  • 12
    Future Language of The Web
  • 12
    Its everywhere
  • 11
    Because I love functions
  • 11
    JavaScript is the New PHP
  • 10
    Like it or not, JS is part of the web standard
  • 9
    Expansive community
  • 9
    Everyone use it
  • 9
    Can be used in backend, frontend and DB
  • 9
    Easy
  • 8
    Most Popular Language in the World
  • 8
    Powerful
  • 8
    Can be used both as frontend and backend as well
  • 8
    For the good parts
  • 8
    No need to use PHP
  • 8
    Easy to hire developers
  • 7
    Agile, packages simple to use
  • 7
    Love-hate relationship
  • 7
    Photoshop has 3 JS runtimes built in
  • 7
    Evolution of C
  • 7
    It's fun
  • 7
    Hard not to use
  • 7
    Versitile
  • 7
    Its fun and fast
  • 7
    Nice
  • 7
    Popularized Class-Less Architecture & Lambdas
  • 7
    Supports lambdas and closures
  • 6
    It let's me use Babel & Typescript
  • 6
    Can be used on frontend/backend/Mobile/create PRO Ui
  • 6
    1.6K Can be used on frontend/backend
  • 6
    Client side JS uses the visitors CPU to save Server Res
  • 6
    Easy to make something
  • 5
    Clojurescript
  • 5
    Promise relationship
  • 5
    Stockholm Syndrome
  • 5
    Function expressions are useful for callbacks
  • 5
    Scope manipulation
  • 5
    Everywhere
  • 5
    Client processing
  • 5
    What to add
  • 4
    Because it is so simple and lightweight
  • 4
    Only Programming language on browser
  • 1
    Test
  • 1
    Hard to learn
  • 1
    Test2
  • 1
    Not the best
  • 1
    Easy to understand
  • 1
    Subskill #4
  • 1
    Easy to learn
  • 0
    Hard 彤
CONS OF JAVASCRIPT
  • 22
    A constant moving target, too much churn
  • 20
    Horribly inconsistent
  • 15
    Javascript is the New PHP
  • 9
    No ability to monitor memory utilitization
  • 8
    Shows Zero output in case of ANY error
  • 7
    Thinks strange results are better than errors
  • 6
    Can be ugly
  • 3
    No GitHub
  • 2
    Slow
  • 0
    HORRIBLE DOCUMENTS, faulty code, repo has bugs

related JavaScript posts

Zach Holman

Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

See more
Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 11.2M views

How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

https://eng.uber.com/distributed-tracing/

(GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

See more
Git logo

Git

293.7K
175.8K
6.6K
Fast, scalable, distributed revision control system
293.7K
175.8K
+ 1
6.6K
PROS OF GIT
  • 1.4K
    Distributed version control system
  • 1.1K
    Efficient branching and merging
  • 959
    Fast
  • 845
    Open source
  • 726
    Better than svn
  • 368
    Great command-line application
  • 306
    Simple
  • 291
    Free
  • 232
    Easy to use
  • 222
    Does not require server
  • 27
    Distributed
  • 22
    Small & Fast
  • 18
    Feature based workflow
  • 15
    Staging Area
  • 13
    Most wide-spread VSC
  • 11
    Role-based codelines
  • 11
    Disposable Experimentation
  • 7
    Frictionless Context Switching
  • 6
    Data Assurance
  • 5
    Efficient
  • 4
    Just awesome
  • 3
    Github integration
  • 3
    Easy branching and merging
  • 2
    Compatible
  • 2
    Flexible
  • 2
    Possible to lose history and commits
  • 1
    Rebase supported natively; reflog; access to plumbing
  • 1
    Light
  • 1
    Team Integration
  • 1
    Fast, scalable, distributed revision control system
  • 1
    Easy
  • 1
    Flexible, easy, Safe, and fast
  • 1
    CLI is great, but the GUI tools are awesome
  • 1
    It's what you do
  • 0
    Phinx
CONS OF GIT
  • 16
    Hard to learn
  • 11
    Inconsistent command line interface
  • 9
    Easy to lose uncommitted work
  • 7
    Worst documentation ever possibly made
  • 5
    Awful merge handling
  • 3
    Unexistent preventive security flows
  • 3
    Rebase hell
  • 2
    When --force is disabled, cannot rebase
  • 2
    Ironically even die-hard supporters screw up badly
  • 1
    Doesn't scale for big data

related Git posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 10M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Tymoteusz Paul
Devops guy at X20X Development LTD · | 23 upvotes · 8.9M views

Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

See more