What is this? Read:
I get frustrated by the number of tools/frameworks/etc. in the tech stack that don't have a good elevator pitch. This is especially annoying in the web-dev world, where the stack is growing at an exponential rate, and new tools are being introduced on an hourly basis.
I don't need boasts about how your tool is better than all the others, or two pages of bullet point features; I need a couple of sentences that tell me what your tool actually IS. That is what this page tries to be (at least for myself).
This is a long page, and I keep adding to it, so don't be afraid to CTR+F to find something!
|Name & Link||What|
|Sass (or SASS)||From wikipedia: "Sass is a preprocessor scripting language that is interpreted or compiled into Cascading Style Sheets (CSS)."
There are a bunch of features that Sass has that CSS does not - most notably nesting, mixins, extending, imports, and variables (although CSS now has variables).
There are two major syntaxes - the original, which uses indentation as the major rule, and SCSS, which uses blocks/braces, and is similar to CSS in rules.
|Less (or LESS, or less.js)||Very similar to Sass (see above row). Main difference is that Less can be transpiled to CSS in-browser, with their JS lib.|
|PostCSS||In my mind, it is closer to webpack or babel than it is to something like SASS. It is not a replacement for CSS, but rather a pipeline (built with JS) that takes in CSS (
Popular example: Write your CSS without concern for browser version, and then use PostCSS
|Styled-Components||A CSS-in-JS tool that lets you write CSS in JS for components with the normal CSS syntax; no need for the camelCase variant.
Uses tagged template literals so you can still easily pull JS variables into the CSS, despite using the non-js syntax.
Utility focused (little or no pre-built components)
- Tailwind *
- Browse, view, and develop UI components in isolation, without needing to load your entire app.
- Supports React, Vue, and even plain HTML
|Name & Link||What||Free Tier?|
|Cloudinary||Image host with advanced transformation and processing features||Yes|
|Github||Technically, you can use Github to serve images by dropping an image into a "new issue" area, and copying the generated link.
Not exactly "fair use"...
- Grunt (kinda, since it is a generic task runner, but has plugins/integrations for bundling)
- Analyzes and generates an analysis/graph of dependencies used in your projects / files, and even detect circular dependencies!
- Can output an image visualization of what the dependency resolution / chain looks like
|Name & Link||What||Anonymous Sharing Supported?|
|CodePen||Sandbox. Supports pre-processors and some JS transpiling. Community oriented (comments, featured pens, etc). Private pens are pro.||No|
|JSFiddle||Very similar to CodePen, with maybe less glamour, but more dev features.||Yes|
|SassMeister||Just for Sass (shows Sass Input -> CSS Output)||No|
|Glitch||Advanced code playground, with more of a 'project' or 'app' scope rather than a small snippet. The idea is you can build entire multi-file apps within Glitch, share, and remix others'.
Also loves to be quirky and fun.
|CodeSandbox||Probably the most powerful multi-file sandbox. Basically like your own VSCode IDE + Node, in a shareable online environment. Supports
|Gitpod||Open any Github or Gitlab repo instantly in an online IDE, with built-in advanced support for things like Docker, build processes, etc. Extremely fast and powerful.||NA|
|Repl||Similar to CodeSandbox; top-tier online IDE, which supports dozens of languages and complicated setups. Extra angle is collaboration; built-in "multiplier" mode.||Yes|
|StackBlitz||Similar to CodeSandbox or Repl.||Yes|
|fiddles.io||Collection of links to other fiddles. Seems out of date...||NA|
|sqlfiddle.com||Online **SQL sandbox (MySQL, PostgreSQL, etc.)||Yes|
|RunKit||Playground to run and test specific NPM packages, in a NodeJS environment. For example, to play around with moment.js.||No|
|Katacoda||Dozens of different playground types, including NodeJS, Dotnet, and more.||NA|
|Name||What||Input Types||Output Types|
|Gatsby (gatsby.js)||JS-powered, extensible, static PWA generator that is focused around React + GraphQL||Unique: Flexible, and can take data from almost anywhere, including a CMS like WordPress. Uses GraphQL APIs. Themes.||React based static site with PWA features.
Flexible and not limited to blogs.
|11ty / Elventy||JS-powered, static site generator that is rather un-opinionated and does not include boilerplate client-side JS.||Markdown, HTML, JS, etc.||Vanilla HTML, no boilerplate JS by default.
Easy to augment to preference though.
|Hugo||Go-powered, markdown-based static site generator. Main focus is on generation speed, and running as single binary with no dependencies. Themes||Markdown||Standard static site.
Lots of pre-built themes to pick from.
|Jekyll||Ruby-powered, markdown-based static site generator. Used for Github pages.||Markdown or Liquid||Standard static site. Focused around blogs.|
date-fns - Date/time utility library
- Benefit over moment.js is tree-shakability, smaller bundle size, and immutability
- Says it's "like lodash for dates"
- hueniverse.com: On Node Framework Popularity
Server Side IO Performance, by Brad Peabody
- Good read on how server IO processing works with different languages
|Name & Link||What||Stack|
|Ember||Front-end framework. Syntax seems similar to Vue. Has more baked-in stuff than Vue and React, versus leaving it up to Dev to decide.||Ember|
|Svelte||Front-end slim framework. It is in a weird position; kind of halfway between Vue and just using handlebars.js and a little bit of custom JS. Kind of harkens back to how a lot of people hand-built their first sites without frameworks.
Aims to be as minimal as possible.
|Svelte syntax, simple HTML + JS + CSS|
|Alpine||Front-end slim framework / templating. Similar to Svelte, and uses an HTML attribute / directive driven syntax (e.g.
||Alpine syntax, simple HTML + JS|
|Angular||Front-end framework. Out of all the front-end frameworks, this one is usually known for being the most "out-of-the-box" full package; pretty much everything is built-in already. But that also makes it big and complicated.||Angular. Now supports Dart too!|
|Name & Link||What||Stack||ORM||Stars / Contributors|
|Laravel||All-in-one PHP backend. Comes with DB ORM, migrations, middleware, auth, boilerplate scaffolding, etc. - All out of the box. Mature framework, heavily MVC based.||PHP, specialized methods, ORM, Blade Template files||Eloquent|
|Lumen||Literally a slimmed down version of Laravel, maintained by the same team and sharing the same core features. Focused around APIs and microservices, so has higher throughput and lower latency, but less overall features.||PHP||Eloquent||
|Symfony||Not exactly a framework as much as a collection of components that can be used to build a framework. Laravel uses several components from Symfony and adds on top of it. As such, using Symfony directly can often result in better performance||PHP||Doctrine|
|ubiquity||Slimmed down MVC PHP framework, focused on performance (particularly in ORM). Faster than Symfony and Laravel||PHP||Built-in, Annotation powered|
|Yii||MVC PHP framework. Looks like it has slightly better perf than Laravel/Lumen or Symfony.||PHP||Yii Query / Yii Active Record / etc|
|Hapi||Slim NodeJS framework focused on speed and security (no dependencies). Kind of a micro-framework, so probably best for things like APIs, services, etc.
Also, see hapi-pal
|Feathers||Unique in that it does not use the MVC pattern - instead it uses hooks and services, designed to reduce boilerplate code writing and make scaling easier.
Personally, I find the syntax a little off-putting and the balance of "what comes out of the box" to be off.
|FoalTS||Full featured, with controllers, services, hooks, etc. Uses a lot of dependency injection, which might make it a more comfortable choice for .NET users.||TS||Default integration is TypeORM|
|Sails||NodeJS MVC framework, with lots of built-ins. On the slower side (slower than Hapi, RingoJS and Fastify)
I've heard it shares a lot of commonality with Ruby on Rails
|NestJS||NodeJS framework that is a wrapper around Express. Focused on being modular (install what you need), dependency injection, and building APIs. Built with TypeScript, so plays extra nice with it.
Lots of DI, decorators, and annotations.
|ASP.NET Core MVC||ASP.NET based MVC framework. A little confusing in that it is now based on .net core, but there is a different version based on .net 4.x. Furthermore, they share some features and codebase; it looks like both versions use
But then for EF, there are two versions - EF 6, which uses .NET 4.x, therefore only running on Windows, or EF Core, which of course runs on .NET Core, and can run anywhere.
|C#, Razor (templating, like Laravel Blade)||BYO, top choices being either Entity Framework (EF), or Dapper||
Fastify is an honorable mention, but I'm not sure I would qualify it as a full traditional framework (at least not an MVC one). Although it has things like middleware and logging, its main focus is just on being a very fast request handler, as a replacement for express. Same goes for VertX, even though they are super unique in that they allow languages other than Java to run on the multithreaded JVM.
ASP.NETversioning: With the bump from version 4.6 to ASP.NET version 5 (ASP.NET 5), MS decided to rename v5 to ASP.NET Core and there will no longer be two versions moving forward. It looks like MVC-6 uses the new Core 1.0 and it plus web api / core are just called ".NET Core", whereas MVC-5 uses the traditional ASP.NET 4.6. See this and this post for details. A further note is that this is really a merge of .NET Core and regular ASP.NET - Although this will be V1.0 of the merged name, technically it will kind of be .NET Core 4.0 (current release is 3.x) merged with ASP.NET 5 (current release is 4.x).
Nuxt (Nuxt.js) is also an exception to this list. I am reluctant to call it a framework (maybe a framework for a framework), since really it is more of an plug-n-play build/serve system around Vue. In this way, it might almost be comparable to Gatsby, since they share a lot of common objectives - such as serving both a JS powered reactive version, as well as static rendering / SSR version of the same codebase, automatically.
- actix (Rust)
- reqwest is more user-friendly wrapper around it (Rust)
- Swoole (PHP / C++)
- atreugo (Go)
- Vert.X (JVM, Cross-Lang) (** See notes)
- Fastify (JS)
These are frameworks / libraries that typically sit between the DB and the client, and handle a large part of the API generation and query handling.
In the case of GraphQL, these libraries also often include UI clients (aka consumers, resolvers, etc) - which bind the UI layer to the data layer in a way where you, the developer, does not have to handle manually coding the data fetching.
Apollo (JS) - GraphQL Wrapper
- Main features are clients, which go in the UI, and the server, which generates GraphQL endpoints
- Has automatic freebies: caching, etc.
- Good intro guide by Flavio Copes
Prisma (JS / TS) - GraphQL Wrapper
- Similar to Apollo, but with better Type-Safety in the client
- Also exposes a more traditional ORM syntax (e.g.
Several headless CMS solutions also fall under the umbrella of "automatic API generator"
- See list under relevant heading
- For example, you often see Strapi recommended for building APIs, despite it branding itself as a headless CMS
Short answer: A CMS that does not care about presentation (templates) or anything to do with the user-facing part of your site, and is only concerned with the backend content-editing and admin management part.
One example is the NetlifyCMS. It provides a GUI editor for editing the site content, which is then synced to a Git repo (serves as database). You then have to use it with something like Gatsby, which turns the actual files stored in that synced repo into front-end HTML, CSS, and JS.
The misleading part is that there tends to be a lot of overlap between headless-CMS and non-headless-CMS. I mean, technically, if you uninstall all your themes from Wordpress and only use the built-in APIs to pass strings from
MySQL to Gatsby, then WordPress is actually acting as a headless CMS!
|Name & Link||What||Free|
|jsonbox.io||Simple POST/GET temp API endpoint for playing around||Yes|
|mocky.io||Quickly get a single URL you can mock response from||Yes|
|req|res||Dummy rest API||Yes|
|mailtrap.io||Test sending email!||Yes (50 emails at a time)|
|RequestBin||Instant endpoint you can use to capture and review HTTP requests||Yes|
|JSONPlaceholder||Fake mock REST API||Yes|
|JSON Generator||Generate dummy JSON data, with structured templates||Yes|
I'm not sure if there is a more specific name for these types of tools, but basically, these are web pages (or small pieces of software) that analyze a user's tech stack and generate a shareable report based on the findings; it might include things such as screen resolution, browser user-agent, internet speed, IP address, etc. These reports can help you (or your IT team) troubleshoot related issues.
|Name & Link||What||Share by URL||Free|
|What Is My Browser||Spits out a report of browser basics, plus a little extra. Examples: OS, IP, resolution, etc. Browser version is included, but full UA string is not.||Yes||Yes|
|MyBrowser.fyi||Minimal browser report, designed to be as minimal (privacy considerate) and readable as possible.||Yes||Yes|
|testRTC Network Test||Designed to test browser capabilities that are essential to Web RTC and remote collaboration software. Full explanation here.
Example Report: here
|WebRTC Troubleshooter||Designed to test Web RTC related browser capabilities and network performance. Report shows pass / fails, but you can click to expand with a little more detail.||*Yes||Yes|
|Twilio WebRTC Diagnostics||Same as WebRTC Troubleshooter - pass / fail test for Web RTC tech stack. However, pass/fail requirements are specific to Twilio.||No||Yes|
|Belarc Advisor||Installed software (not browser-based) that scans the computer and generates a full report, with info such as OS, CPU, Memory, Security Patches, etc.||*No (But exportable reports)||*Yes (non-commercial)|
- Stanford SLAC - Network Monitoring Tools
- Google: Before you call support: Gather key information
Built in browser support report pages:
- browser "report" "support" OR "IT" OR "diagnostics" OR "diagnostic" OR "troubleshooter" "speed" OR "bandwidth" "jitter" OR "lag" "resolution" OR "browser size" "operating system" OR "OS" -requirements -google -books
- generate browser "report" OR "summary" OR "export" "for support" OR "for it support"
|Name & Link||What||Free|
|CyberChef||Online web-app for string manipulation.
You can chain together multiple complex transformations, and save as a "recipe", which you can then reuse later or share!
|globster.xyz||Glob tester with visual preview and explanations||Yes|
|World Time Buddy||Quickly convert between timezones with interactive slider||Yes|
||Preview and test
|strftime.net||Preview and test
|Mockaroo||Quickly generate some fake data sets||Yes|
|Desmos graphic calculator||A nice visual way to look at equations, play around with input sliders, etc.||Yes|
|brumm.af/shadows||CSS Shadow Generator||Yes|
|larsenwork.com/easing-gradients||CSS gradient generator||Yes|
|colors-and-fonts||Collection of Palettes, fonts, etc.||Yes|
|Resolution Scale Calculator||Calculate downscale (or upscale) options, limiting to integer resolutions.||Yes|
|Git History||View a timeline / slideshow of a single file's Git history.||Yes|
|QuickType||A quick web-app tool for instantly turning JSON into code, even with nested types. Supports TypeScript, Dart, C++, and more!||Yes|
|Name & Link||What||Free|
|tota11y||Accessibility analyzer / debugger.||Yes|
|Requestly||Redirect network requests, swap headers, etc.||*Yes|
|Name & Link||What||Free Tier||My Opinion|
|IFTTT||"If This, Than That" - visually set up small flows (trigger + execution). Many different native integrations.||Yes (basically everything)||Honestly? I'm amazed that this is ever talked about positively; extremely limited capabilities, the UI is a mess (why is "create" hidden under a menu?), and it seems unreliable at best.|
|Zapier||Visual flow / automation builder. Has offerings for both technical and non-technical users; you can stick to simple steps, or you can also make use of scripts and advanced steps.||Yes (100 executions / month, max of 5 flows total)||Good UI and overall feel, but extremely pricey; even paying $20/month limits you to 750 executions a month, which you would burn through in just 5 days if you have a zap that runs once every 10 minutes.|
|Microsoft Power Automate (Previously Flow)||Visual flow builder and pipeline designer. Growing number of integrations, especially with other MS business products.||Maybe? The licensing for this seems like a nightmare...||I haven't used this at all, so I can't really give an opinion. I like that they are adding some "intelligence" to flows, with some sort of AI. That alone puts them a bit above some competitors. I really wish this had simplified pricing and licensing - as it is, it seems like they are only interested in catering to business employees, and not individuals.|
|Huginn||Open-Source "agent based" work flow automation platform. Ruby-based, and extensible with gems.
- here is a brief overview
|Yes (self-hosted)||N/A - no experience|
|n8n||Open-Source WYSIWYG workflow automation builder platform, based on nodes and the connections between them. Built with Node.js and TypeScript.||Yes (self-hosted)||No experience with it, but the GUI looks really impressive, and there is an extensive list of integrations for a project like this.|