About

TL;DR: it's a wiki for any kind of software development tool. The content and its organization are up to the community. Have fun!

Tool TL;DR was created to help people of all levels of expertise get a grasp of the growing software tool landscape. Whether you're a beginner who doesn't know what's out there, or a senior dev who just wants a quick rundown of a particular framework/library/tool, you will find answers here. The explanations are not comprehensive by any means (hence the name), but they provide a quick, clear, and helpful description without having to dig through the documentation. And, if you feel like a particular description could be improved, feel free to edit! Tool TL;DR is, and will always be, a community-first place.

Javascript Frameworks

Organization & Formatting

The wiki is broken down by categories and tools. Tools and categories can go in other categories. You can rearrange this structure to find the best fit for information.

Categories

Categories have three main parts: the what, why, and where.

What

The TL;DR of the category. Explain what the category's tools do.

Why

Why is the category of tools is needed in the first place? For those just starting out, this can be valuable when you don't know what you don't know. It also aims to answer why someone would need to start using the type of tool. Again, for those exploring the landscape for the first time, this can provide a great explanation to a question that they didn't even know they might have.

You don't know what you don't know

Where

Where, in an application, would the category of tools go? This isn't talking about physical location, instead, you can also think about it like describing a pipeline, each part playing a role at a certain time and place. For example, the Web Server category would describe tools that go (virtually/logically) in front of an Application Server and would be the first in line to handle incoming web traffic. This question exists simply to help people create a mental image of all the pieces in the puzzle.

Naming

Some simple guidelines for naming categories:

  • Don't spell out acronyms in the title, it takes up too much space. Instead, spell them out and put the acronym in parentheses at the end of the name in the What section when describing the category.
  • You don't need to repeat words from the parent category's name, this also takes up space.

Tools

Tools have one main question: why use this tool over one of its alternatives in the same category?

What

The tl;dr of the tool. Also describes how the tool deviates from its category's description.

Why

Tools will often have neighbors in the same space, but when exploring what's out there in a TL;DR fashion, you probably want answers as to what separates the tools in a quick and concise way. This section, just like the others, cuts out the jargon and clears up any blurred lines.

Tool Details

There are several other descriptors for tools on their pages.

  • Environment: the type of programming environment this tool is found. This is usually a programming language, but can also be something like a protocol.
  • Created: the year this tool was launched.
  • Version: the latest version of the tool.
  • Actively Developed: the status of the tool (yes or no).
  • Project URL: the link to the home of the project.

Contact & Discussion

Have a question, comment, feature request, or bug to report? Go to the GitHub issues page here.

If you want to create a discussion on one of the pages here, then click on the extra (...) menu button at the top of a category or tool page next to the edit buttons and click "Discuss."


If the site helps you and you want to show some love, give the site some more uptime by donating.