Alternatives to TortoiseSVN logo

Alternatives to TortoiseSVN

TortoiseGit, SVN (Subversion), Git, TortoiseHg, and GitHub are the most popular alternatives and competitors to TortoiseSVN.
49
1

What is TortoiseSVN and what are its top alternatives?

It is an Apache™ Subversion (SVN)® client, implemented as a Windows shell extension. It's intuitive and easy to use, since it doesn't require the Subversion command line client to run. And it is free to use, even in a commercial environment.
TortoiseSVN is a tool in the Visual Version Control category of a tech stack.

Top Alternatives to TortoiseSVN

  • TortoiseGit
    TortoiseGit

    It is a Git revision control client, implemented as a Windows shell extension and based on TortoiseSVN. It is free software released under the GNU General Public License. ...

  • SVN (Subversion)
    SVN (Subversion)

    Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. ...

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

  • TortoiseHg
    TortoiseHg

    It is a Windows shell extension and a series of applications for the Mercurial distributed revision control system. It also includes a Gnome/Nautilus extension and a CLI wrapper application so the TortoiseHg tools can be used on non-Windows platforms. ...

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

  • Slack
    Slack

    Imagine all your team communication in one place, instantly searchable, available wherever you go. That’s Slack. All your messages. All your files. And everything from Twitter, Dropbox, Google Docs, Asana, Trello, GitHub and dozens of other services. All together. ...

  • Jira
    Jira

    Jira's secret sauce is the way it simplifies the complexities of software development into manageable units of work. Jira comes out-of-the-box with everything agile teams need to ship value to customers faster. ...

  • Trello
    Trello

    Trello is a collaboration tool that organizes your projects into boards. In one glance, Trello tells you what's being worked on, who's working on what, and where something is in a process. ...

TortoiseSVN alternatives & related posts

TortoiseGit logo

TortoiseGit

50
90
5
The Power of Git in a Windows Shell
50
90
+ 1
5
PROS OF TORTOISEGIT
  • 4
    Turns Explorer into a git client
  • 1
    Free
CONS OF TORTOISEGIT
    Be the first to leave a con

    related TortoiseGit posts

    SVN (Subversion) logo

    SVN (Subversion)

    802
    630
    43
    Enterprise-class centralized version control for the masses
    802
    630
    + 1
    43
    PROS OF SVN (SUBVERSION)
    • 20
      Easy to use
    • 13
      Simple code versioning
    • 5
      User/Access Management
    • 3
      Complicated code versionioning by Subversion
    • 2
      Free
    CONS OF SVN (SUBVERSION)
    • 7
      Branching and tagging use tons of disk space

    related SVN (Subversion) posts

    I use Visual Studio Code because at this time is a mature software and I can do practically everything using it.

    • It's free and open source: The project is hosted on GitHub and it’s free to download, fork, modify and contribute to the project.

    • Multi-platform: You can download binaries for different platforms, included Windows (x64), MacOS and Linux (.rpm and .deb packages)

    • LightWeight: It runs smoothly in different devices. It has an average memory and CPU usage. Starts almost immediately and it’s very stable.

    • Extended language support: Supports by default the majority of the most used languages and syntax like JavaScript, HTML, C#, Swift, Java, PHP, Python and others. Also, VS Code supports different file types associated to projects like .ini, .properties, XML and JSON files.

    • Integrated tools: Includes an integrated terminal, debugger, problem list and console output inspector. The project navigator sidebar is simple and powerful: you can manage your files and folders with ease. The command palette helps you find commands by text. The search widget has a powerful auto-complete feature to search and find your files.

    • Extensible and configurable: There are many extensions available for every language supported, including syntax highlighters, IntelliSense and code completion, and debuggers. There are also extension to manage application configuration and architecture like Docker and Jenkins.

    • Integrated with Git: You can visually manage your project repositories, pull, commit and push your changes, and easy conflict resolution.( there is support for SVN (Subversion) users by plugin)

    See more
    rishig
    Head of Product at Zulip · | 8 upvotes · 193.1K views
    Shared insights
    on
    GitGitSVN (Subversion)SVN (Subversion)
    at

    I use Git instead of SVN (Subversion) because it allows us to scale our development team. At any given time, the Zulip open source project has hundreds of open pull requests from tens of contributors, each in various stages of the pipeline. Git's workflow makes it very easy to context switch between different feature branches.

    See more
    Git logo

    Git

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

    related Git posts

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

    Our whole DevOps stack consists of the following tools:

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

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

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

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

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

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

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

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

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

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

    See more
    TortoiseHg logo

    TortoiseHg

    8
    12
    0
    A set of graphical tools and a shell extension for the Mercurial distributed revision control system
    8
    12
    + 1
    0
    PROS OF TORTOISEHG
      Be the first to leave a pro
      CONS OF TORTOISEHG
        Be the first to leave a con

        related TortoiseHg posts

        GitHub logo

        GitHub

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

        related GitHub posts

        Johnny Bell

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

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

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

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

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

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

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

        See more

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

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

        Check Out My Architecture: CLICK ME

        Check out the GitHub repo attached

        See more
        Slack logo

        Slack

        119.6K
        96.1K
        6K
        Bring all your communication together in one place
        119.6K
        96.1K
        + 1
        6K
        PROS OF SLACK
        • 1.2K
          Easy to integrate with
        • 876
          Excellent interface on multiple platforms
        • 849
          Free
        • 694
          Mobile friendly
        • 690
          People really enjoy using it
        • 331
          Great integrations
        • 315
          Flexible notification preferences
        • 198
          Unlimited users
        • 184
          Strong search and data archiving
        • 155
          Multi domain switching support
        • 82
          Easy to use
        • 40
          Beautiful
        • 27
          Hubot support
        • 22
          Unread/read control
        • 21
          Slackbot
        • 19
          Permalink for each messages
        • 17
          Text snippet with highlighting
        • 15
          Quote message easily
        • 14
          Per-room notification
        • 13
          Awesome integration support
        • 12
          Star for each message / attached files
        • 12
          IRC gateway
        • 11
          Good communication within a team
        • 11
          Dropbox Integration
        • 10
          Slick, search is great
        • 10
          Jira Integration
        • 9
          New Relic Integration
        • 8
          Great communication tool
        • 8
          Combine All Services Quickly
        • 8
          Asana Integration
        • 7
          This tool understands developers
        • 7
          XMPP gateway
        • 7
          Google Drive Integration
        • 7
          Awesomeness
        • 6
          Replaces email
        • 6
          Twitter Integration
        • 6
          Google Docs Integration
        • 6
          BitBucket integration
        • 5
          Jenkins Integration
        • 5
          GREAT Customer Support / Quick Response to Feedback
        • 5
          Guest and Restricted user control
        • 4
          Clean UI
        • 4
          Excellent multi platform internal communication tool
        • 4
          GitHub integration
        • 4
          Mention list view
        • 4
          Gathers all my communications in one place
        • 3
          Perfect implementation of chat + integrations
        • 3
          Easy
        • 3
          Easy to add a reaction
        • 3
          Timely while non intrusive
        • 3
          Great on-boarding
        • 3
          Threaded chat
        • 3
          Visual Studio Integration
        • 3
          Easy to start working with
        • 3
          Android app
        • 2
          Simplicity
        • 2
          Message Actions
        • 2
          It's basically an improved (although closed) IRC
        • 2
          So much better than email
        • 2
          Eases collaboration for geographically dispersed teams
        • 2
          Great interface
        • 2
          Great Channel Customization
        • 2
          Markdown
        • 2
          Intuitive, easy to use, great integrations
        • 1
          Great Support Team
        • 1
          Watch
        • 1
          Multi work-space support
        • 1
          Flexible and Accessible
        • 1
          Better User Experience
        • 1
          Archive Importing
        • 1
          Travis CI integration
        • 1
          It's the coolest IM ever
        • 1
          Community
        • 1
          Great API
        • 1
          Easy remote communication
        • 1
          Get less busy
        • 1
          API
        • 1
          Zapier integration
        • 1
          Targetprocess integration
        • 1
          Finally with terrible "threading"—I miss Flowdock
        • 1
          Complete with plenty of Electron BLOAT
        • 1
          I was 666 star :D
        • 1
          Dev communication Made Easy
        • 1
          Integrates with just about everything
        • 1
          Very customizable
        • 0
          Platforms
        • 0
          Easy to useL
        CONS OF SLACK
        • 13
          Can be distracting depending on how you use it
        • 6
          Requires some management for large teams
        • 6
          Limit messages history
        • 5
          Too expensive
        • 5
          You don't really own your messages
        • 4
          Too many notifications by default

        related Slack posts

        Lucas Litton
        Founder & CEO at Macombey · | 24 upvotes · 319K views

        Sentry has been essential to our development approach. Nobody likes errors or apps that crash. We use Sentry heavily during Node.js and React development. Our developers are able to see error reports, crashes, user's browsers, and more, all in one place. Sentry also seamlessly integrates with Asana, Slack, and GitHub.

        See more
        Jakub Olan
        Node.js Software Engineer · | 17 upvotes · 443.1K views

        Last time we shared there information about our decision about using YouTrack over Jira actually we found much better solution that our team have loved. Linear is a minimalistic issue tracker that integrates well with Sentry, GitHub, Slack and Figma which are our basic tools. I would like to recommend checking out Linear as a potential alternative to "heavy" issue trackers, maybe at enterprises that may not work but when we're a startup that works awesome!

        See more
        Jira logo

        Jira

        61.5K
        48.6K
        1.2K
        The #1 software development tool used by agile teams to plan, track, and release great software.
        61.5K
        48.6K
        + 1
        1.2K
        PROS OF JIRA
        • 310
          Powerful
        • 254
          Flexible
        • 149
          Easy separation of projects
        • 113
          Run in the cloud
        • 105
          Code integration
        • 58
          Easy to use
        • 53
          Run on your own
        • 39
          Great customization
        • 39
          Easy Workflow Configuration
        • 27
          REST API
        • 12
          Great Agile Management tool
        • 7
          Integrates with virtually everything
        • 6
          Confluence
        • 6
          Complicated
        • 3
          Sentry Issues Integration
        • 2
          It's awesome
        CONS OF JIRA
        • 8
          Rather expensive
        • 5
          Large memory requirement
        • 2
          Slow
        • 1
          Cloud or Datacenter only

        related Jira posts

        Johnny Bell

        So I am a huge fan of JIRA like #massive I used it for many many years, and really loved it, used it personally and at work. I would suggest every new workplace that I worked at to switch to JIRA instead of what I was using.

        When I started at #StackShare we were using a Trello #Kanban board and I was so shocked at how easy the workflow was to follow, create new tasks and get tasks QA'd and deployed. What was so great about this was it didn't come with all the complexity of JIRA. Like setting up a project, user rules etc. You are able to hit the ground running with Trello and get tasks started right away without being overwhelmed with the complexity of options in JIRA

        With a few TrelloPowerUps we were easily able to add GitHub integration and storyPoints to our cards and thats all we needed to get a really nice agile workflow going.

        I'm not saying that JIRA is not useful, I can see larger companies being able to use the JIRA features and have the time to go through all the complex setup to get a really good workflow going. But for smaller #Startups that want to hit the ground running Trello for me is the way to go.

        In saying that what I would love Trello to implement is to allow me to create custom fields. Right now we just have a Description field. So I am adding User Stories & How To Test in the Markdown of the Description if I could have these as custom fields then my #Agile workflow would be complete.

        #StackDecisionsLaunch

        See more
        Jakub Olan
        Node.js Software Engineer · | 17 upvotes · 443.1K views

        Last time we shared there information about our decision about using YouTrack over Jira actually we found much better solution that our team have loved. Linear is a minimalistic issue tracker that integrates well with Sentry, GitHub, Slack and Figma which are our basic tools. I would like to recommend checking out Linear as a potential alternative to "heavy" issue trackers, maybe at enterprises that may not work but when we're a startup that works awesome!

        See more
        Trello logo

        Trello

        43.1K
        33.5K
        3.7K
        Your entire project, in a single glance
        43.1K
        33.5K
        + 1
        3.7K
        PROS OF TRELLO
        • 715
          Great for collaboration
        • 628
          Easy to use
        • 573
          Free
        • 375
          Fast
        • 347
          Realtime
        • 237
          Intuitive
        • 215
          Visualizing
        • 169
          Flexible
        • 126
          Fun user interface
        • 83
          Snappy and blazing fast
        • 30
          Simple, intuitive UI that gets out of your way
        • 27
          Kanban
        • 21
          Clean Interface
        • 18
          Easy setup
        • 18
          Card Structure
        • 17
          Drag and drop attachments
        • 11
          Simple
        • 10
          Markdown commentary on cards
        • 9
          Lists
        • 9
          Integration with other work collaborative apps
        • 8
          Satisfying User Experience
        • 8
          Cross-Platform Integration
        • 7
          Recognizes GitHub commit links
        • 6
          Easy to learn
        • 5
          Great
        • 4
          Better than email
        • 4
          Versatile Team & Project Management
        • 3
          and lots of integrations
        • 3
          Trello’s Developmental Transparency
        • 3
          Effective
        • 2
          Easy
        • 2
          Powerful
        • 2
          Agile
        • 2
          Easy to have an overview of the project status
        • 2
          flexible and fast
        • 2
          Simple and intuitive
        • 1
          Name rolls of the tongue
        • 1
          Customizable
        • 1
          Email integration
        • 1
          Personal organisation
        • 1
          Nice
        • 1
          Great organizing (of events/tasks)
        • 0
          Easiest way to visually express the scope of projects
        CONS OF TRELLO
        • 5
          No concept of velocity or points
        • 4
          Very light native integrations
        • 2
          A little too flexible

        related Trello posts

        Johnny Bell

        So I am a huge fan of JIRA like #massive I used it for many many years, and really loved it, used it personally and at work. I would suggest every new workplace that I worked at to switch to JIRA instead of what I was using.

        When I started at #StackShare we were using a Trello #Kanban board and I was so shocked at how easy the workflow was to follow, create new tasks and get tasks QA'd and deployed. What was so great about this was it didn't come with all the complexity of JIRA. Like setting up a project, user rules etc. You are able to hit the ground running with Trello and get tasks started right away without being overwhelmed with the complexity of options in JIRA

        With a few TrelloPowerUps we were easily able to add GitHub integration and storyPoints to our cards and thats all we needed to get a really nice agile workflow going.

        I'm not saying that JIRA is not useful, I can see larger companies being able to use the JIRA features and have the time to go through all the complex setup to get a really good workflow going. But for smaller #Startups that want to hit the ground running Trello for me is the way to go.

        In saying that what I would love Trello to implement is to allow me to create custom fields. Right now we just have a Description field. So I am adding User Stories & How To Test in the Markdown of the Description if I could have these as custom fields then my #Agile workflow would be complete.

        #StackDecisionsLaunch

        See more
        Francisco Quintero
        Tech Lead at Dev As Pros · | 13 upvotes · 1.8M views

        For Etom, a side project. We wanted to test an idea for a future and bigger project.

        What Etom does is searching places. Right now, it leverages the Google Maps API. For that, we found a React component that makes this integration easy because using Google Maps API is not possible via normal API requests.

        You kind of need a map to work as a proxy between the software and Google Maps API.

        We hate configuration(coming from Rails world) so also decided to use Create React App because setting up a React app, with all the toys, it's a hard job.

        Thanks to all the people behind Create React App it's easier to start any React application.

        We also chose a module called Reactstrap which is Bootstrap UI in React components.

        An important thing in this side project(and in the bigger project plan) is to measure visitor through out the app. For that we researched and found that Keen was a good choice(very good free tier limits) and also it is very simple to setup and real simple to send data to

        Slack and Trello are our defaults tools to comunicate ideas and discuss topics, so, no brainer using them as well for this project.

        See more