Alternatives to TSLint logo

Alternatives to TSLint

ESLint, React Native, Prettier, SonarLint, and Git are the most popular alternatives and competitors to TSLint.
1.9K
0

What is TSLint and what are its top alternatives?

TSLint is a static analysis tool for TypeScript that checks your TypeScript code for errors, stylistic issues, and inconsistencies. It helps enforce a consistent coding style and finds potential bugs early in the development process. TSLint has key features such as customizable rules, automatic fixing of some issues, and integration with popular code editors. However, TSLint is being deprecated in favor of ESLint, which offers a more robust and flexible alternative for JavaScript and TypeScript linting.

  1. ESLint: ESLint is a widely used static analysis tool for identifying problematic patterns found in JavaScript and TypeScript code. It has a large library of customizable rules, supports various plugins, and integrates with popular code editors. However, transitioning from TSLint to ESLint may require some effort due to differences in rule configurations.
  2. Prettier: Prettier is a code formatter that enforces a consistent code style by automatically formatting your code. It supports TypeScript and integrates well with ESLint for comprehensive linting and formatting capabilities. The main advantage of Prettier is its simplicity and ease of use.
  3. TypeScript ESLint: TypeScript ESLint is a specialized ESLint plugin for TypeScript that provides specific linting rules tailored for TypeScript code. It offers better support for TypeScript-specific features and syntax compared to TSLint.
  4. StandardJS: StandardJS is a JavaScript coding style guide that comes with a command-line tool for enforcing its rules. It focuses on simplicity and readability, making it a popular choice for projects that prioritize consistent code style.
  5. JSHint: JSHint is a lightweight JavaScript code quality tool that helps detect errors and potential issues in JavaScript code. It offers a simple configuration and is suitable for projects that require basic code linting without complex configurations.
  6. SonarQube: SonarQube is a comprehensive code quality and security analysis platform that supports various programming languages, including TypeScript. It provides detailed reports on code issues, vulnerabilities, and code smells, making it a powerful tool for improving code quality.
  7. TypeScript TSLint Plugin: TypeScript TSLint Plugin is an official TypeScript plugin that integrates TSLint within the TypeScript language service. It allows for real-time linting feedback within code editors, enhancing the developer experience.
  8. ts-loader: ts-loader is a TypeScript loader for Webpack that enables TypeScript compilation and type checking during the build process. While not a direct replacement for TSLint, ts-loader helps streamline the development workflow for TypeScript projects.
  9. xo: xo is a JavaScript and TypeScript linter with a focus on simplicity and zero-configuration setup. It enforces a set of predefined rules and integrates seamlessly with popular code editors for a hassle-free linting experience.
  10. TypeCheck: TypeCheck is a lightweight static type checker for JavaScript and TypeScript that helps catch type-related errors in code. It provides additional type safety checks beyond what TSLint offers, enhancing the reliability of TypeScript code.

Top Alternatives to TSLint

  • ESLint
    ESLint

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

  • React Native
    React Native

    React Native enables you to build world-class application experiences on native platforms using a consistent developer experience based on JavaScript and React. The focus of React Native is on developer efficiency across all the platforms you care about - learn once, write anywhere. Facebook uses React Native in multiple production apps and will continue investing in React Native. ...

  • Prettier
    Prettier

    Prettier is an opinionated code formatter. It enforces a consistent style by parsing your code and re-printing it with its own rules that take the maximum line length into account, wrapping code when necessary. ...

  • SonarLint
    SonarLint

    It is an IDE extension that helps you detect and fix quality issues as you write code. Like a spell checker, it squiggles flaws so that they can be fixed before committing code. ...

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

TSLint alternatives & related 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.1M 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
    React Native logo

    React Native

    33.5K
    29K
    1.2K
    A framework for building native apps with React
    33.5K
    29K
    + 1
    1.2K
    PROS OF REACT NATIVE
    • 214
      Learn once write everywhere
    • 174
      Cross platform
    • 168
      Javascript
    • 122
      Native ios components
    • 69
      Built by facebook
    • 65
      Easy to learn
    • 45
      Bridges me into ios development
    • 40
      It's just react
    • 39
      No compile
    • 36
      Declarative
    • 22
      Fast
    • 13
      Virtual Dom
    • 12
      Insanely fast develop / test cycle
    • 12
      Livereload
    • 11
      Great community
    • 9
      It is free and open source
    • 9
      Native android components
    • 9
      Easy setup
    • 9
      Backed by Facebook
    • 7
      Highly customizable
    • 7
      Scalable
    • 6
      Awesome
    • 6
      Everything component
    • 6
      Great errors
    • 6
      Win win solution of hybrid app
    • 5
      Not dependent on anything such as Angular
    • 5
      Simple
    • 4
      Awesome, easy starting from scratch
    • 4
      OTA update
    • 3
      As good as Native without any performance concerns
    • 3
      Easy to use
    • 2
      Many salary
    • 2
      Can be incrementally added to existing native apps
    • 2
      Hot reload
    • 2
      Over the air update (Flutter lacks)
    • 2
      'It's just react'
    • 2
      Web development meets Mobile development
    • 1
      Ngon
    CONS OF REACT NATIVE
    • 23
      Javascript
    • 19
      Built by facebook
    • 12
      Cant use CSS
    • 4
      30 FPS Limit
    • 2
      Slow
    • 2
      Generate large apk even for a simple app
    • 2
      Some compenents not truly native

    related React Native posts

    Collins Ogbuzuru
    Front-end dev at Evolve credit · | 37 upvotes · 248.6K views

    Your tech stack is solid for building a real-time messaging project.

    React and React Native are excellent choices for the frontend, especially if you want to have both web and mobile versions of your application share code.

    ExpressJS is an unopinionated framework that affords you the flexibility to use it's features at your term, which is a good start. However, I would recommend you explore Sails.js as well. Sails.js is built on top of Express.js and it provides additional features out of the box, especially the Websocket integration that your project requires.

    Don't forget to set up Graphql codegen, this would improve your dev experience (Add Typescript, if you can too).

    I don't know much about databases but you might want to consider using NO-SQL. I used Firebase real-time db and aws dynamo db on a few of my personal projects and I love they're easy to work with and offer more flexibility for a chat application.

    See more
    Vaibhav Taunk
    Team Lead at Technovert · | 31 upvotes · 4.2M 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
    Prettier logo

    Prettier

    7.7K
    1.1K
    7
    Prettier is an opinionated code formatter.
    7.7K
    1.1K
    + 1
    7
    PROS OF PRETTIER
    • 2
      Customizable
    • 1
      Open Source
    • 1
      Atom/VSCode package
    • 1
      Follows the Ruby Style Guide by default
    • 1
      Runs offline
    • 1
      Completely free
    CONS OF PRETTIER
      Be the first to leave a con

      related Prettier posts

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

      SonarLint

      172
      350
      16
      An IDE extension to detect and fix issues as you write code
      172
      350
      + 1
      16
      PROS OF SONARLINT
      • 13
        IDE Integration
      • 3
        Free
      CONS OF SONARLINT
      • 3
        Non contextual warnings
      • 3
        Not Very User Friendly

      related SonarLint posts

      Git logo

      Git

      297.1K
      178.4K
      6.6K
      Fast, scalable, distributed revision control system
      297.1K
      178.4K
      + 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.1M 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.7M 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.3K
      249.2K
      10.3K
      Powerful collaboration, review, and code management for open source and private development projects
      285.3K
      249.2K
      + 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

      179K
      163.3K
      2.3K
      Build and debug modern web and cloud applications, by Microsoft
      179K
      163.3K
      + 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.1M 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.2K
      140K
      3.9K
      Enterprise Container Platform for High-Velocity Innovation.
      174.2K
      140K
      + 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.1M 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.7M 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