Alternatives to Bundler logo

Alternatives to Bundler

Metro Bundler, Conduit, npm, Webpack, and Rake are the most popular alternatives and competitors to Bundler.
1.1K
64
+ 1
0

What is Bundler and what are its top alternatives?

Bundler is a popular dependency management tool for Ruby that helps developers maintain a consistent set of gems for their projects. It automatically installs the necessary gems and their respective versions specified in a Gemfile, making it easier to manage dependencies. However, Bundler has been criticized for its slow performance when dealing with large dependency trees.

  1. RubyGems: RubyGems is the standard package manager for Ruby that allows users to easily install, publish, and manage gems. One key feature is the ability to install gems with a single command. Pros: Widely used and integrated with Ruby by default. Cons: Less advanced dependency management compared to Bundler.
  2. RVM (Ruby Version Manager): RVM is a command-line tool for managing multiple Ruby environments on a single machine. It allows users to switch between different Ruby versions and gemsets. Pros: Provides a flexible way to manage Ruby environments. Cons: Focuses more on Ruby version management than gem dependency management.
  3. Pipenv: Pipenv is a dependency manager for Python projects that aims to bring the best of all packaging worlds. It automatically creates and manages a virtual environment for projects. Pros: Simplifies dependency management for Python projects. Cons: Limited to Python projects only.
  4. Yarn: Yarn is a package manager for JavaScript that aims to be faster and more reliable than npm. It caches every package it installs, making the installation process faster. Pros: Faster performance compared to npm. Cons: Limited to JavaScript projects.
  5. Composer: Composer is a dependency manager for PHP projects that allows users to declare the libraries their projects depend on. It also manages the dependencies automatically. Pros: Easy to use for PHP projects. Cons: Limited to PHP projects only.
  6. Conda: Conda is an open-source package management system that supports multiple languages, including Python and R. It can be used to manage libraries, dependencies, and environments. Pros: Supports multiple languages. Cons: More complex setup compared to Pipenv.
  7. Docker: Docker is a platform for developing, shipping, and running applications in containers. It provides a way to package dependencies with the application, making it easier to manage dependencies across different environments. Pros: Ensures consistent environments across different machines. Cons: Overkill for small projects.
  8. Lerna: Lerna is a tool for managing JavaScript projects with multiple packages. It optimizes the workflow around managing multi-package repositories with git and npm. Pros: Efficient management of large JavaScript projects. Cons: More suitable for advanced users.
  9. Pants: Pants is a build system for software that replaces Makefiles and other legacy build systems like Bazel. It supports multiple languages and provides features like fine-grained dependency management. Pros: Scalable build system for large projects. Cons: Steeper learning curve compared to Bundler.
  10. Nix: Nix is a powerful package manager for Linux and other Unix systems that makes package management reliable and reproducible. It provides a declarative approach to package management and supports multiple languages. Pros: Reproducible builds and reliable package management. Cons: Steeper learning curve for beginners.

Top Alternatives to Bundler

  • Metro Bundler
    Metro Bundler

    🚅 Fast: We aim for sub-second reload cycles, fast startup and quick bundling speeds. ⚖️ Scalable: Works with thousands of modules in a single application. ⚛️ Integrated: Supports every React Native project out of the box. ...

  • Conduit
    Conduit

    Conduit is a lightweight open source service mesh designed for performance, power, and ease of use when running applications on Kubernetes. Conduit is incredibly fast, lightweight, fundamentally secure, and easy to get started with. ...

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

  • Webpack
    Webpack

    A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows to load parts for the application on demand. Through "loaders" modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff. ...

  • Rake
    Rake

    It is a software task management and build automation tool. It allows the user to specify tasks and describe dependencies as well as to group tasks in a namespace. ...

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

Bundler alternatives & related posts

Metro Bundler logo

Metro Bundler

13
0
🚇 The JavaScript bundler for React Native
13
0
PROS OF METRO BUNDLER
    Be the first to leave a pro
    CONS OF METRO BUNDLER
      Be the first to leave a con

      related Metro Bundler posts

      Conduit logo

      Conduit

      9
      0
      Open-source service mesh for Kubernetes
      9
      0
      PROS OF CONDUIT
        Be the first to leave a pro
        CONS OF CONDUIT
          Be the first to leave a con

          related Conduit posts

          npm logo

          npm

          125.1K
          1.6K
          The package manager for JavaScript.
          125.1K
          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.4M 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
          Webpack logo

          Webpack

          41K
          752
          A bundler for javascript and friends
          41K
          752
          PROS OF WEBPACK
          • 309
            Most powerful bundler
          • 182
            Built-in dev server with livereload
          • 142
            Can handle all types of assets
          • 87
            Easy configuration
          • 22
            Laravel-mix
          • 4
            Overengineered, Underdeveloped
          • 2
            Makes it easy to bundle static assets
          • 2
            Webpack-Encore
          • 1
            Redundant
          • 1
            Better support in Browser Dev-Tools
          CONS OF WEBPACK
          • 15
            Hard to configure
          • 5
            No clear direction
          • 2
            Spaghetti-Code out of the box
          • 2
            SystemJS integration is quite lackluster
          • 2
            Loader architecture is quite a mess (unreliable/buggy)
          • 2
            Fire and Forget mentality of Core-Developers

          related Webpack posts

          Russel Werner
          Lead Engineer at StackShare · | 32 upvotes · 2.9M views

          StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

          Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

          #StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

          See more
          Jonathan Pugh
          Software Engineer / Project Manager / Technical Architect · | 25 upvotes · 3.1M views

          I needed to choose a full stack of tools for cross platform mobile application design & development. After much research and trying different tools, these are what I came up with that work for me today:

          For the client coding I chose Framework7 because of its performance, easy learning curve, and very well designed, beautiful UI widgets. I think it's perfect for solo development or small teams. I didn't like React Native. It felt heavy to me and rigid. Framework7 allows the use of #CSS3, which I think is the best technology to come out of the #WWW movement. No other tech has been able to allow designers and developers to develop such flexible, high performance, customisable user interface elements that are highly responsive and hardware accelerated before. Now #CSS3 includes variables and flexboxes it is truly a powerful language and there is no longer a need for preprocessors such as #SCSS / #Sass / #less. React Native contains a very limited interpretation of #CSS3 which I found very frustrating after using #CSS3 for some years already and knowing its powerful features. The other very nice feature of Framework7 is that you can even build for the browser if you want your app to be available for desktop web browsers. The latest release also includes the ability to build for #Electron so you can have MacOS, Windows and Linux desktop apps. This is not possible with React Native yet.

          Framework7 runs on top of Apache Cordova. Cordova and webviews have been slated as being slow in the past. Having a game developer background I found the tweeks to make it run as smooth as silk. One of those tweeks is to use WKWebView. Another important one was using srcset on images.

          I use #Template7 for the for the templating system which is a no-nonsense mobile-centric #HandleBars style extensible templating system. It's easy to write custom helpers for, is fast and has a small footprint. I'm not forced into a new paradigm or learning some new syntax. It operates with standard JavaScript, HTML5 and CSS 3. It's written by the developer of Framework7 and so dovetails with it as expected.

          I configured TypeScript to work with the latest version of Framework7. I consider TypeScript to be one of the best creations to come out of Microsoft in some time. They must have an amazing team working on it. It's very powerful and flexible. It helps you catch a lot of bugs and also provides code completion in supporting IDEs. So for my IDE I use Visual Studio Code which is a blazingly fast and silky smooth editor that integrates seamlessly with TypeScript for the ultimate type checking setup (both products are produced by Microsoft).

          I use Webpack and Babel to compile the JavaScript. TypeScript can compile to JavaScript directly but Babel offers a few more options and polyfills so you can use the latest (and even prerelease) JavaScript features today and compile to be backwards compatible with virtually any browser. My favorite recent addition is "optional chaining" which greatly simplifies and increases readability of a number of sections of my code dealing with getting and setting data in nested objects.

          I use some Ruby scripts to process images with ImageMagick and pngquant to optimise for size and even auto insert responsive image code into the HTML5. Ruby is the ultimate cross platform scripting language. Even as your scripts become large, Ruby allows you to refactor your code easily and make it Object Oriented if necessary. I find it the quickest and easiest way to maintain certain aspects of my build process.

          For the user interface design and prototyping I use Figma. Figma has an almost identical user interface to #Sketch but has the added advantage of being cross platform (MacOS and Windows). Its real-time collaboration features are outstanding and I use them a often as I work mostly on remote projects. Clients can collaborate in real-time and see changes I make as I make them. The clickable prototyping features in Figma are also very well designed and mean I can send clickable prototypes to clients to try user interface updates as they are made and get immediate feedback. I'm currently also evaluating the latest version of #AdobeXD as an alternative to Figma as it has the very cool auto-animate feature. It doesn't have real-time collaboration yet, but I heard it is proposed for 2019.

          For the UI icons I use Font Awesome Pro. They have the largest selection and best looking icons you can find on the internet with several variations in styles so you can find most of the icons you want for standard projects.

          For the backend I was using the #GraphCool Framework. As I later found out, #GraphQL still has some way to go in order to provide the full power of a mature graph query language so later in my project I ripped out #GraphCool and replaced it with CouchDB and Pouchdb. Primarily so I could provide good offline app support. CouchDB with Pouchdb is very flexible and efficient combination and overcomes some of the restrictions I found in #GraphQL and hence #GraphCool also. The most impressive and important feature of CouchDB is its replication. You can configure it in various ways for backups, fault tolerance, caching or conditional merging of databases. CouchDB and Pouchdb even supports storing, retrieving and serving binary or image data or other mime types. This removes a level of complexity usually present in database implementations where binary or image data is usually referenced through an #HTML5 link. With CouchDB and Pouchdb apps can operate offline and sync later, very efficiently, when the network connection is good.

          I use PhoneGap when testing the app. It auto-reloads your app when its code is changed and you can also install it on Android phones to preview your app instantly. iOS is a bit more tricky cause of Apple's policies so it's not available on the App Store, but you can build it and install it yourself to your device.

          So that's my latest mobile stack. What tools do you use? Have you tried these ones?

          See more
          Rake logo

          Rake

          56
          0
          A software task management and build automation tool
          56
          0
          PROS OF RAKE
            Be the first to leave a pro
            CONS OF RAKE
              Be the first to leave a con

              related Rake posts

              Git logo

              Git

              299.2K
              6.6K
              Fast, scalable, distributed revision control system
              299.2K
              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
              • 28
                Distributed
              • 23
                Small & Fast
              • 18
                Feature based workflow
              • 15
                Staging Area
              • 13
                Most wide-spread VSC
              • 11
                Disposable Experimentation
              • 11
                Role-based codelines
              • 7
                Frictionless Context Switching
              • 6
                Data Assurance
              • 5
                Efficient
              • 4
                Just awesome
              • 3
                Easy branching and merging
              • 3
                Github integration
              • 2
                Compatible
              • 2
                Possible to lose history and commits
              • 2
                Flexible
              • 1
                Team Integration
              • 1
                Easy
              • 1
                Light
              • 1
                Fast, scalable, distributed revision control system
              • 1
                Rebase supported natively; reflog; access to plumbing
              • 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 · 12M 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 · 10.2M 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

              288.3K
              10.3K
              Powerful collaboration, review, and code management for open source and private development projects
              288.3K
              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
              • 868
                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
                It's awesome
              • 6
                Smooth integration
              • 6
                Cloud SCM
              • 6
                Nice API
              • 6
                Graphs
              • 6
                Integrations
              • 5
                Hands down best online Git service available
              • 5
                Reliable
              • 5
                Quick Onboarding
              • 5
                CI Integration
              • 5
                Remarkable uptime
              • 4
                Security options
              • 4
                Loved by developers
              • 4
                Uses GIT
              • 4
                Free HTML hosting
              • 4
                Easy to use and collaborate with others
              • 4
                Version Control
              • 4
                Simple but powerful
              • 4
                Unlimited Public Repos at no cost
              • 3
                Nice to use
              • 3
                IAM
              • 3
                Ci
              • 3
                Easy deployment via SSH
              • 2
                Free private repos
              • 2
                Good tools support
              • 2
                All in one development service
              • 2
                Never dethroned
              • 2
                Easy source control and everything is backed up
              • 2
                Issues tracker
              • 2
                Self Hosted
              • 2
                IAM integration
              • 2
                Very Easy to Use
              • 2
                Easy to use
              • 2
                Leads the copycats
              • 2
                Free HTML hostings
              • 2
                Easy and efficient maintainance of the projects
              • 2
                Beautiful
              • 1
                Dasf
              • 1
                Profound
              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

              181.2K
              2.3K
              Build and debug modern web and cloud applications, by Microsoft
              181.2K
              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 · 12M 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