Alternatives to Prettier logo

Alternatives to Prettier

EditorConfig, ESLint, TSLint, Git, and GitHub are the most popular alternatives and competitors to Prettier.
7.7K
7

What is Prettier and what are its top alternatives?

Prettier is a popular code formatter that automatically formats your code for consistency and eliminates debates over coding styles. It supports multiple languages and has pre-configured defaults for various code styles. However, it may lack flexibility in customization and may not suit all coding standards.

  1. ESLint: ESLint is a static code analysis tool for identifying problematic patterns in JavaScript code. It offers highly customizable linting rules that can catch style guide violations and potential errors. Pros: Extensive plugin ecosystem, highly customizable. Cons: Requires manual configuration for code formatting.
  2. TSLint: TSLint is a static analysis tool for TypeScript code that provides a wide range of rules to ensure readability and maintainability of the codebase. Pros: Type-aware linting, straightforward configuration. Cons: Deprecated in favor of ESLint for TypeScript linting.
  3. JSHint: JSHint is a community-driven tool that detects errors and potential problems in JavaScript code. It offers a simple way to enforce coding standards and styling conventions. Pros: Lightweight, easy to set up. Cons: Limited customization compared to ESLint.
  4. Black: Black is a Python code formatter that reformats Python code to adhere to a consistent style. It aims for minimalistic and readable code, automatically enforcing the PEP 8 style guide. Pros: Opinionated formatting, seamless integration. Cons: Limited configuration options.
  5. RuboCop: RuboCop is a Ruby static code analyzer and formatter that helps detect and correct style violations in your Ruby code. It provides a variety of built-in rules for improving code quality. Pros: Rich set of rules, customizable. Cons: Steeper learning curve for beginners.
  6. SonarQube: SonarQube is an open-source platform for continuous inspection of code quality to perform automatic reviews with static analysis of code. It covers a wide range of programming languages and detects bugs, vulnerabilities, and code smells. Pros: Comprehensive code review capabilities, support for various languages. Cons: Requires setup and maintenance of the SonarQube server.
  7. SwiftLint: SwiftLint is a tool to enforce Swift style and conventions in your projects. It can catch problematic patterns and enforce code style guidelines. Pros: Integrates seamlessly with Xcode, customizable rules. Cons: Limited to Swift projects only.
  8. Clang-Format: Clang-Format is a tool to automate the formatting of C, C++, Objective-C, and JavaScript code using Clang’s format style. It offers a variety of options and configuration settings for code styling. Pros: Integrated with Clang toolchain, robust formatting capabilities. Cons: Limited to specific languages.
  9. Pylint: Pylint is a Python static code analysis tool that checks for errors in Python code and enforces a coding standard. It provides functionalities like checking code's quality, identifying syntax errors, and maintaining a consistent coding style. Pros: Detailed reporting, configurable. Cons: Requires initial setup and configuration.
  10. PHP_CodeSniffer: PHP_CodeSniffer is a set of two PHP scripts; the main phpcs script that tokenizes PHP, JavaScript, and CSS files to detect violations of a defined coding standard, and a second phpcbf script to automatically correct coding standard violations. Pros: Flexible coding standard support, automatic code fixing. Cons: May require additional plugins for specific coding standards.

Top Alternatives to Prettier

  • EditorConfig
    EditorConfig

    It is a file format and collection of text editor plugins. It helps maintain consistent coding styles for multiple developers working on the same project across various editors and IDEs. ...

  • ESLint
    ESLint

    A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease. ...

  • TSLint
    TSLint

    An extensible static analysis tool that checks TypeScript code for readability, maintainability, and functionality errors. It is widely supported across modern editors & build systems and can be customized with your own lint rules, configurations, and formatters. ...

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

  • GitHub
    GitHub

    GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together. ...

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

  • Docker
    Docker

    The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere ...

  • npm
    npm

    npm is the command-line interface to the npm ecosystem. It is battle-tested, surprisingly flexible, and used by hundreds of thousands of JavaScript developers every day. ...

Prettier alternatives & related posts

EditorConfig logo

EditorConfig

177
60
2
A file format and collection of text editor plugins for maintaining consistent coding styles
177
60
+ 1
2
PROS OF EDITORCONFIG
  • 2
    Y6y
CONS OF EDITORCONFIG
    Be the first to leave a con

    related EditorConfig posts

    ESLint logo

    ESLint

    30K
    13.7K
    28
    The fully pluggable JavaScript code quality tool
    30K
    13.7K
    + 1
    28
    PROS OF ESLINT
    • 8
      Consistent javascript - opinions don't matter anymore
    • 6
      Free
    • 6
      IDE Integration
    • 4
      Customizable
    • 2
      Focuses code review on quality not style
    • 2
      Broad ecosystem of support & users
    CONS OF ESLINT
      Be the first to leave a con

      related ESLint posts

      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 11.2M 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
      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 24 upvotes · 4.9M views

      Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

      • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
      • Vue Styleguidist as our style guide and pool of developed Vue.js components
      • Vuetify as Material Component Framework (for fast app development)
      • TypeScript as programming language
      • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
      • ESLint, TSLint and Prettier for coding style and code analyzes
      • Jest as testing framework
      • Google Fonts and Font Awesome for typography and icon toolkit
      • NativeScript-Vue for mobile development

      The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

      • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
      • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
      • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
      • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
      • Large scaling. Vue.js can help to develop pretty large reusable templates.
      • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
      See more
      TSLint logo

      TSLint

      1.9K
      234
      0
      An extensible linter for the TypeScript language
      1.9K
      234
      + 1
      0
      PROS OF TSLINT
        Be the first to leave a pro
        CONS OF TSLINT
          Be the first to leave a con

          related TSLint posts

          Simon Reymann
          Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 11.2M 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
          Simon Reymann
          Senior Fullstack Developer at QUANTUSflow Software GmbH · | 24 upvotes · 4.9M views

          Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

          • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
          • Vue Styleguidist as our style guide and pool of developed Vue.js components
          • Vuetify as Material Component Framework (for fast app development)
          • TypeScript as programming language
          • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
          • ESLint, TSLint and Prettier for coding style and code analyzes
          • Jest as testing framework
          • Google Fonts and Font Awesome for typography and icon toolkit
          • NativeScript-Vue for mobile development

          The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

          • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
          • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
          • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
          • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
          • Large scaling. Vue.js can help to develop pretty large reusable templates.
          • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
          See more
          Git logo

          Git

          297.5K
          178.7K
          6.6K
          Fast, scalable, distributed revision control system
          297.5K
          178.7K
          + 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
          • 8
            Worst documentation ever possibly made
          • 5
            Awful merge handling
          • 3
            Unexistent preventive security flows
          • 3
            Rebase hell
          • 2
            Ironically even die-hard supporters screw up badly
          • 2
            When --force is disabled, cannot rebase
          • 1
            Doesn't scale for big data

          related Git posts

          Simon Reymann
          Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 11.2M 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 · 9.8M 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
          GitHub logo

          GitHub

          285.9K
          249.7K
          10.3K
          Powerful collaboration, review, and code management for open source and private development projects
          285.9K
          249.7K
          + 1
          10.3K
          PROS OF GITHUB
          • 1.8K
            Open source friendly
          • 1.5K
            Easy source control
          • 1.3K
            Nice UI
          • 1.1K
            Great for team collaboration
          • 867
            Easy setup
          • 504
            Issue tracker
          • 487
            Great community
          • 483
            Remote team collaboration
          • 449
            Great way to share
          • 442
            Pull request and features planning
          • 147
            Just works
          • 132
            Integrated in many tools
          • 122
            Free Public Repos
          • 116
            Github Gists
          • 113
            Github pages
          • 83
            Easy to find repos
          • 62
            Open source
          • 60
            Easy to find projects
          • 60
            It's free
          • 56
            Network effect
          • 49
            Extensive API
          • 43
            Organizations
          • 42
            Branching
          • 34
            Developer Profiles
          • 32
            Git Powered Wikis
          • 30
            Great for collaboration
          • 24
            It's fun
          • 23
            Clean interface and good integrations
          • 22
            Community SDK involvement
          • 20
            Learn from others source code
          • 16
            Because: Git
          • 14
            It integrates directly with Azure
          • 10
            Standard in Open Source collab
          • 10
            Newsfeed
          • 8
            Fast
          • 8
            Beautiful user experience
          • 8
            It integrates directly with Hipchat
          • 7
            Easy to discover new code libraries
          • 6
            Smooth integration
          • 6
            Integrations
          • 6
            Graphs
          • 6
            Nice API
          • 6
            It's awesome
          • 6
            Cloud SCM
          • 5
            Quick Onboarding
          • 5
            Remarkable uptime
          • 5
            CI Integration
          • 5
            Reliable
          • 5
            Hands down best online Git service available
          • 4
            Version Control
          • 4
            Unlimited Public Repos at no cost
          • 4
            Simple but powerful
          • 4
            Loved by developers
          • 4
            Free HTML hosting
          • 4
            Uses GIT
          • 4
            Security options
          • 4
            Easy to use and collaborate with others
          • 3
            Easy deployment via SSH
          • 3
            Ci
          • 3
            IAM
          • 3
            Nice to use
          • 2
            Easy and efficient maintainance of the projects
          • 2
            Beautiful
          • 2
            Self Hosted
          • 2
            Issues tracker
          • 2
            Easy source control and everything is backed up
          • 2
            Never dethroned
          • 2
            All in one development service
          • 2
            Good tools support
          • 2
            Free HTML hostings
          • 2
            IAM integration
          • 2
            Very Easy to Use
          • 2
            Easy to use
          • 2
            Leads the copycats
          • 2
            Free private repos
          • 1
            Profound
          • 1
            Dasf
          CONS OF GITHUB
          • 55
            Owned by micrcosoft
          • 38
            Expensive for lone developers that want private repos
          • 15
            Relatively slow product/feature release cadence
          • 10
            API scoping could be better
          • 9
            Only 3 collaborators for private repos
          • 4
            Limited featureset for issue management
          • 3
            Does not have a graph for showing history like git lens
          • 2
            GitHub Packages does not support SNAPSHOT versions
          • 1
            No multilingual interface
          • 1
            Takes a long time to commit
          • 1
            Expensive

          related GitHub posts

          Johnny Bell

          I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

          I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

          I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

          Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

          Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

          With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

          If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

          See more

          Context: I wanted to create an end to end IoT data pipeline simulation in Google Cloud IoT Core and other GCP services. I never touched Terraform meaningfully until working on this project, and it's one of the best explorations in my development career. The documentation and syntax is incredibly human-readable and friendly. I'm used to building infrastructure through the google apis via Python , but I'm so glad past Sung did not make that decision. I was tempted to use Google Cloud Deployment Manager, but the templates were a bit convoluted by first impression. I'm glad past Sung did not make this decision either.

          Solution: Leveraging Google Cloud Build Google Cloud Run Google Cloud Bigtable Google BigQuery Google Cloud Storage Google Compute Engine along with some other fun tools, I can deploy over 40 GCP resources using Terraform!

          Check Out My Architecture: CLICK ME

          Check out the GitHub repo attached

          See more
          Visual Studio Code logo

          Visual Studio Code

          179.4K
          163.6K
          2.3K
          Build and debug modern web and cloud applications, by Microsoft
          179.4K
          163.6K
          + 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 code editor
          • 18
            Best editor
          • 17
            Easy to get started with
          • 15
            Lots of extensions
          • 15
            Good for begginers
          • 15
            Crossplatform
          • 15
            Built on Electron
          • 14
            Extensions for everything
          • 14
            Open, cross-platform, fast, monthly updates
          • 14
            All Languages Support
          • 13
            Easy to use and learn
          • 12
            "fast, stable & easy to use"
          • 12
            Extensible
          • 11
            Ui design is great
          • 11
            Totally customizable
          • 11
            Git out of the box
          • 11
            Useful for begginer
          • 11
            Faster edit for slow computer
          • 10
            SSH support
          • 10
            Great community
          • 10
            Fast Startup
          • 9
            Works With Almost EveryThing You Need
          • 9
            Great language support
          • 9
            Powerful Debugger
          • 9
            It has terminal and there are lots of shortcuts in it
          • 8
            Can compile and run .py files
          • 8
            Python extension is fast
          • 7
            Features rich
          • 7
            Great document formater
          • 6
            He is not Michael
          • 6
            Extension Echosystem
          • 6
            She is not Rachel
          • 6
            Awesome multi cursor support
          • 5
            VSCode.pro Course makes it easy to learn
          • 5
            Language server client
          • 5
            SFTP Workspace
          • 5
            Very proffesional
          • 5
            Easy azure
          • 4
            Has better support and more extentions for debugging
          • 4
            Supports lots of operating systems
          • 4
            Excellent as git difftool and mergetool
          • 4
            Virtualenv integration
          • 3
            Better autocompletes than Atom
          • 3
            Has more than enough languages for any developer
          • 3
            'batteries included'
          • 3
            More tools to integrate with vs
          • 3
            Emmet preinstalled
          • 2
            VS Code Server: Browser version of VS Code
          • 2
            CMake support with autocomplete
          • 2
            Microsoft
          • 2
            Customizable
          • 2
            Light
          • 2
            Big extension marketplace
          • 2
            Fast and ruby is built right in
          • 1
            File:///C:/Users/ydemi/Downloads/yuksel_demirkaya_webpa
          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

          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
          Simon Reymann
          Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 11.2M 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
          Docker logo

          Docker

          174.4K
          140.2K
          3.9K
          Enterprise Container Platform for High-Velocity Innovation.
          174.4K
          140.2K
          + 1
          3.9K
          PROS OF DOCKER
          • 823
            Rapid integration and build up
          • 692
            Isolation
          • 521
            Open source
          • 505
            Testa­bil­i­ty and re­pro­ducibil­i­ty
          • 460
            Lightweight
          • 218
            Standardization
          • 185
            Scalable
          • 106
            Upgrading / down­grad­ing / ap­pli­ca­tion versions
          • 88
            Security
          • 85
            Private paas environments
          • 34
            Portability
          • 26
            Limit resource usage
          • 17
            Game changer
          • 16
            I love the way docker has changed virtualization
          • 14
            Fast
          • 12
            Concurrency
          • 8
            Docker's Compose tools
          • 6
            Fast and Portable
          • 6
            Easy setup
          • 5
            Because its fun
          • 4
            Makes shipping to production very simple
          • 3
            It's dope
          • 3
            Highly useful
          • 2
            Does a nice job hogging memory
          • 2
            Open source and highly configurable
          • 2
            Simplicity, isolation, resource effective
          • 2
            MacOS support FAKE
          • 2
            Its cool
          • 2
            Docker hub for the FTW
          • 2
            HIgh Throughput
          • 2
            Very easy to setup integrate and build
          • 2
            Package the environment with the application
          • 2
            Super
          • 0
            Asdfd
          CONS OF DOCKER
          • 8
            New versions == broken features
          • 6
            Unreliable networking
          • 6
            Documentation not always in sync
          • 4
            Moves quickly
          • 3
            Not Secure

          related Docker posts

          Simon Reymann
          Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 11.2M 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 · 9.8M 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
          npm logo

          npm

          124.5K
          80.8K
          1.6K
          The package manager for JavaScript.
          124.5K
          80.8K
          + 1
          1.6K
          PROS OF NPM
          • 647
            Best package management system for javascript
          • 382
            Open-source
          • 327
            Great community
          • 148
            More packages than rubygems, pypi, or packagist
          • 112
            Nice people matter
          • 6
            As fast as yarn but really free of facebook
          • 6
            Audit feature
          • 4
            Good following
          • 1
            Super fast
          • 1
            Stability
          CONS OF NPM
          • 5
            Problems with lockfiles
          • 5
            Bad at package versioning and being deterministic
          • 3
            Node-gyp takes forever
          • 1
            Super slow

          related npm posts

          Simon Reymann
          Senior Fullstack Developer at QUANTUSflow Software GmbH · | 27 upvotes · 5.1M views

          Our whole Node.js backend stack consists of the following tools:

          • Lerna as a tool for multi package and multi repository management
          • npm as package manager
          • NestJS as Node.js framework
          • TypeScript as programming language
          • ExpressJS as web server
          • Swagger UI for visualizing and interacting with the API’s resources
          • Postman as a tool for API development
          • TypeORM as object relational mapping layer
          • JSON Web Token for access token management

          The main reason we have chosen Node.js over PHP is related to the following artifacts:

          • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
          • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
          • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
          • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
          See more
          Johnny Bell

          So when starting a new project you generally have your go to tools to get your site up and running locally, and some scripts to build out a production version of your site. Create React App is great for that, however for my projects I feel as though there is to much bloat in Create React App and if I use it, then I'm tied to React, which I love but if I want to switch it up to Vue or something I want that flexibility.

          So to start everything up and running I clone my personal Webpack boilerplate - This is still in Webpack 3, and does need some updating but gets the job done for now. So given the name of the repo you may have guessed that yes I am using Webpack as my bundler I use Webpack because it is so powerful, and even though it has a steep learning curve once you get it, its amazing.

          The next thing I do is make sure my machine has Node.js configured and the right version installed then run Yarn. I decided to use Yarn because when I was building out this project npm had some shortcomings such as no .lock file. I could probably move from Yarn to npm but I don't really see any point really.

          I use Babel to transpile all of my #ES6 to #ES5 so the browser can read it, I love Babel and to be honest haven't looked up any other transpilers because Babel is amazing.

          Finally when developing I have Prettier setup to make sure all my code is clean and uniform across all my JS files, and ESLint to make sure I catch any errors or code that could be optimized.

          I'm really happy with this stack for my local env setup, and I'll probably stick with it for a while.

          See more