Alternatives to Crucible logo

Alternatives to Crucible

Bitbucket, GitHub, Forge, Fisheye, and Git are the most popular alternatives and competitors to Crucible.
57
118
+ 1
12

What is Crucible and what are its top alternatives?

Crucible is a collaborative code review tool that helps development teams to improve code quality and collaboration by allowing them to review code, share feedback, and track changes in real-time. Its key features include inline commenting, custom workflows, integration with Jira, and detailed reports. However, one limitation of Crucible is that it may feel overwhelming for small teams or individual developers.

  1. Bitbucket Code Insights: Bitbucket Code Insights provides robust code review features like inline commenting, pull request approvals, and integration with Bitbucket Pipelines for continuous integration. Pros of Bitbucket Code Insights include seamless integration with other Atlassian tools, while some cons compared to Crucible are limited customization options.
  2. GitHub: GitHub offers built-in code review features like pull requests, inline comments, and code suggestions. The platform is widely used and integrates well with other GitHub features such as Actions and Packages. A major advantage of GitHub is its large community and marketplace for extensions, but a limitation compared to Crucible is the lack of built-in reporting capabilities.
  3. GitLab Code Review: GitLab Code Review allows teams to improve code quality through features like inline commenting, code review workflows, and easy collaboration. One advantage of GitLab Code Review is its all-in-one platform for project management, CI/CD, and code review, but it may have a steep learning curve compared to Crucible.
  4. Upsource: Upsource by JetBrains is a comprehensive code review tool with features like code browsing, discussions, and integration with IntelliJ IDEA. Upsource offers smart code suggestions and integrations with major version control systems, but it may be more resource-intensive compared to Crucible.
  5. Review Board: Review Board is an open-source code review tool that supports features like diff viewing, file attachments, and issue tracking. A benefit of Review Board is its flexibility and customization options, while a downside compared to Crucible may be the lack of seamless integration with other development tools.
  6. Phabricator: Phabricator is an open-source suite of tools for code review, repository hosting, and project management. It offers features like auditing, push notifications, and code search capabilities. One advantage of Phabricator is its extensibility and integration options, but it may require more setup and maintenance compared to Crucible.
  7. Reviewable: Reviewable is a lightweight code review tool focused on simplicity and ease of use. It offers features like multi-file reviews, side-by-side diffs, and integration with GitHub and Bitbucket. Pros of Reviewable include a streamlined user interface, while a limitation compared to Crucible may be the lack of advanced customization options.
  8. Gerrit: Gerrit is an open-source code review tool specifically designed for Git repositories. It provides features like access controls, branch permissions, and inline commenting. One advantage of Gerrit is its strong focus on code quality and code review processes, but it may have a steeper learning curve compared to Crucible.
  9. RhodeCode: RhodeCode is a self-hosted platform for code collaboration and version control with features like pull requests, code review, and repository management. RhodeCode offers enterprise-grade security and compliance features, but it may require more maintenance compared to Crucible.
  10. Sider: Sider is an AI-powered code review tool that helps teams automate code quality analysis, identify issues, and improve code reviews. Pros of Sider include its AI-driven recommendations and integration with GitHub and Bitbucket, while a limitation compared to Crucible may be the reliance on AI technology for code review suggestions.

Top Alternatives to Crucible

  • Bitbucket
    Bitbucket

    Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users. ...

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

  • Forge
    Forge

    Fastest possible way to host lighting-fast static websites for small businesses, web startups, and app developers. ...

  • Fisheye
    Fisheye

    FishEye provides a read-only window into your Subversion, Perforce, CVS, Git, and Mercurial repositories, all in one place. Keep a pulse on everything about your code: Visualize and report on activity, integrate source with JIRA issues, and search for commits, files, revisions, or people. ...

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

  • Visual Studio Code
    Visual Studio Code

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

  • Docker
    Docker

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

  • npm
    npm

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

Crucible alternatives & related posts

Bitbucket logo

Bitbucket

40.7K
2.8K
One place to plan projects, collaborate on code, test and deploy, all with free private repositories
40.7K
2.8K
PROS OF BITBUCKET
  • 905
    Free private repos
  • 397
    Simple setup
  • 349
    Nice ui and tools
  • 342
    Unlimited private repositories
  • 240
    Affordable git hosting
  • 123
    Integrates with many apis and services
  • 119
    Reliable uptime
  • 87
    Nice gui
  • 85
    Pull requests and code reviews
  • 58
    Very customisable
  • 16
    Mercurial repositories
  • 14
    SourceTree integration
  • 12
    JIRA integration
  • 10
    Track every commit to an issue in JIRA
  • 8
    Deployment hooks
  • 8
    Best free alternative to Github
  • 7
    Automatically share repositories with all your teammates
  • 7
    Source Code Insight
  • 7
    Compatible with Mac and Windows
  • 6
    Price
  • 5
    Login with Google
  • 5
    Create a wiki
  • 5
    Approve pull request button
  • 4
    Customizable pipelines
  • 4
    #2 Atlassian Product after JIRA
  • 3
    Unlimited Private Repos at no cost
  • 3
    Also supports Mercurial
  • 3
    Continuous Integration and Delivery
  • 2
    Mercurial Support
  • 2
    Multilingual interface
  • 2
    Teamcity
  • 2
    Open source friendly
  • 2
    Issues tracker
  • 2
    IAM
  • 2
    Academic license program
  • 2
    IAM integration
CONS OF BITBUCKET
  • 19
    Not much community activity
  • 17
    Difficult to review prs because of confusing ui
  • 15
    Quite buggy
  • 10
    Managed by enterprise Java company
  • 8
    CI tool is not free of charge
  • 7
    Complexity with rights management
  • 6
    Only 5 collaborators for private repos
  • 4
    Slow performance
  • 2
    No AWS Codepipelines integration
  • 1
    No more Mercurial repositories
  • 1
    No server side git-hook support

related Bitbucket posts

Michael Kelly
Senior Software Engineer at StackShare · | 14 upvotes · 959.3K views

I use GitLab when building side-projects and MVPs. The interface and interactions are close enough to those of GitHub to prevent cognitive switching costs between professional and personal projects hosted on different services.

GitLab also provides a suite of tools including issue/project management, CI/CD with GitLab CI, and validation/landing pages with GitLab Pages. With everything in one place, on an #OpenSourceCloud GitLab makes it easy for me to manage much larger projects on my own, than would be possible with other solutions or tools.

It's petty I know, but I can also read the GitLab code diffs far more easily than diffs on GitHub or Bitbucket...they just look better in my opinion.

See more
Shared insights
on
GitHubGitHubGitLabGitLabBitbucketBitbucket

A bit difference in GitHub and GitLab though both are Version Control repository management services which provides key component in the software development workflow. A decision of choosing GitHub over GitLab is major leap extension from code management, to deployment and monitoring alongside looking beyond the code base hosting provided best fitted tools for developer communities.

  • Authentication stages - With GitLab you can set and modify people’s permissions according to their role. In GitHub, you can decide if someone gets a read or write access to a repository.
  • Built-In Continuous Integrations - GitLab offers its very own CI for free. No need to use an external CI service. And if you are already used to an external CI, you can obviously integrate with Jenkins, etc whereas GitHub offers various 3rd party integrations – such as Travis CI, CircleCI or Codeship – for running and testing your code. However, there’s no built-in CI solution at the moment.
  • Import/Export Resources - GitLab offers detailed documentation on how to import your data from other vendors – such as GitHub, Bitbucket to GitLab. GitHub, on the other hand, does not offer such detailed documentation for the most common git repositories. However, GitHub offers to use GitHub Importer if you have your source code in Subversion, Mercurial, TFS and others.

Also when it comes to exporting data, GitLab seems to do a pretty solid job, offering you the ability to export your projects including the following data:

  • Wiki and project repositories
  • Project uploads
  • The configuration including webhooks and services
  • Issues with comments, merge requests with diffs and comments, labels, milestones, snippets, and other project entities.

GitHub, on the other hand, seems to be more restrictive when it comes to export features of existing GitHub repositories. * Integrations - #githubmarketplace gives you an essence to have multiple and competitive integrations whereas you will find less in the GitLab.

So go ahead with better understanding.

See more
GitHub logo

GitHub

288.2K
10.3K
Powerful collaboration, review, and code management for open source and private development projects
288.2K
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
Forge logo

Forge

9
1
Static web hosting made simple
9
1
PROS OF FORGE
  • 1
    Fgfgf
CONS OF FORGE
    Be the first to leave a con

    related Forge posts

    Fisheye logo

    Fisheye

    41
    0
    Search, track, and visualize code changes
    41
    0
    PROS OF FISHEYE
      Be the first to leave a pro
      CONS OF FISHEYE
        Be the first to leave a con

        related Fisheye posts

        Shared insights
        on
        JiraJiraFisheyeFisheyeCrucibleCrucible

        I need a tool to review. So when I searched, I saw Crucible and Fisheye. I have e few questions:

        1. Are Crucible and Fisheye start without Jira integration?
        2. Only for document review, which one should be preferred? What do you think about it?
        3. Am I doing import word document and export same word format? Well, when I upload a document to crucible, Is it possible to output in which format I enter? İs there a fixed format?
        See more
        Git logo

        Git

        299.1K
        6.6K
        Fast, scalable, distributed revision control system
        299.1K
        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
        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
        Docker logo

        Docker

        175.8K
        3.9K
        Enterprise Container Platform for High-Velocity Innovation.
        175.8K
        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
          Easy setup
        • 6
          Fast and Portable
        • 5
          Because its fun
        • 4
          Makes shipping to production very simple
        • 3
          Highly useful
        • 3
          It's dope
        • 2
          Package the environment with the application
        • 2
          Super
        • 2
          Open source and highly configurable
        • 2
          Simplicity, isolation, resource effective
        • 2
          MacOS support FAKE
        • 2
          Its cool
        • 2
          Does a nice job hogging memory
        • 2
          Docker hub for the FTW
        • 2
          HIgh Throughput
        • 2
          Very easy to setup integrate and build
        • 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 · 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
        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