esbuild VS Tailwind CSS

esbuild is a general purpose code compiler and build tool that uses golang builds, it is very fast and 1~2 orders of magnitude higher in performance than the existing js toolchain. It's not an out-of-the-box build tool yet, but with its plugin system we can already do a lot of things.

import { Plugin } from 'esbuild' /** * Automatically exclude all dependencies * Some regular expression syntax of js is not supported by golang, see https://github.com/evanw/esbuild/issues/1634 */ export function autoExternal(): Plugin { return { name: 'autoExternal', setup(build) { build.onResolve({ filter: /. */ }, (args) => { if (/^\. {1,2}\//.test(args.path)) { return } return { path: args.path, external: true, } }) }, } }

But then you see stuff like ESBuild, where the Evan Wallace (the author) tried to write in both Rust and Go, and his Go version was faster. According to him, this was probably because Go runs destructors in a parallel thread, whereas Rust runs them in the same thread (source), among other factors. The same performance could theoretically be achieved in Rust, but it would demand a lot more effort.

Use esbuild as a compiler and backend bundler

Will provide an alternative solution for Windows later. (ref: https://github.com/evanw/esbuild/issues/976)

Esbuild is a Javascript build tool written in Go, which pre-bundles dependencies 10-100 times faster than Javascript-based bundlers.

We did this via the npm threads wrapper and esbuild. We first moved all of our compute code into a new file with minimal imports, called imageCompare.worker.js. We then added a pre-compilation step with esbuild to compile this file into a bundle. We then spawn the worker using this generated file as a blob, and interact with it via the threads promise interface.

Though, if you want to use one, do yourself a favor and give esbuild a try. It is orders of magnitude faster, at the cost of less flexibility.

Make my builds faster by forcing myself onto esbuild from the beginning, even if that makes delivering some capabilities harder (like web workers and service workers, Hot Module Replacement, and so on).

I’d also recommend using a CSS framework, to spare yourself the frustration of either trying to tinker with the nitty gritty until things finally look OK or alternatively having to deal with looking at an ugly website the whole time. Milligram is a good starting point here that makes your website look OK literally by just adding one line, Tailwind is more involved to get started with but for me the easiest to use if you’re trying to get a custom look, Bootstrap is kind of a middle ground here - it gives you components to work with so it’s a bit more pluggable than Milligram and it’ll have something for most things you’re trying to do, but it’ll also be pretty hard to achieve a custom look (it can be done, but without putting a ton of effort into it your website will basically look like a “bootstrap website”, which is probably not an issue for you right now but it is a downside).

That said, there is a significant community of developers who choose to use css-in-js tooling (I'm a Chakra UI fan, myself) or things like tailwindcss as a way to avoid hand writing CSS/SCSS. I don't miss it writing SCSS by hand, myself.

In this guide you will learn how to set up Ruby on Rails with Tailwind CSS and install Flowbite to start using the UI components built with the utility classes from Tailwind CSS.

I came across a lint warning of "unknownAtRules". With the help of this link, I was able to resolve it. I just had to ignore it in my vscode settings

TailwindCSS is a utility first framework. It's tiny in comparison to Bootstrap, which includes hundreds of large, clunky, pre-built components.Instead, Tailwind includes hundreds of simple, easy to chain together classes to style your pages. These classes can also be stripped and minified when you’re finished designing, resulting in a tiny css file.

I use https://tailwindcss.com/ for the UI. Thanks for bug report i will fix that :)

Next.js for framework, Tailwind CSS for styling (but I wanted to use CSS in JS, so I used twin.macro this time).

Stitches, vanilla-extract, Tailwind CSS