Tailwind CSS VS esbuild

Go to the Tailwind website

I also installed Tailwind CSS to create most of the layout for the page, with the prefix option of tw- (this is to prevent clashing classes between Tailwind and Vuetify).

The other major frameworks I use are tailwindcss for styling and Fable.Lit for the views.

I made this with VueJS (CDN), Tailwindcss and Flowbite components.

Using Tailwind CSS, you don't have to write custom CSS to style your application because it's a utility-first framework. These days it is widely used among developers to build complex UI because of its simplicity. You can check out their official docs for more information.

Tailwind CSS: A utility-first CSS framework

I decided to choose jigsaw as I am familiar with the technologies it's built with (PHP , Tailwind for styling and Blade as template engine) as it will be easy to customize if needed besides that, it comes with decent amount of features out of the box, I barely did any customization to it, just followed the installation instructions and got started.

I'd use Tailwind - the ready-made CSS classes make it really simple to get a nice-looking UI...

Tailwind was perfect for this. It is a simple utility css library with classes for the smallest things, like width or background color. It also allows you to create custom themes with classes such as color-primary, where you can define what that ends up meaning. This combined with Vue components means you can create small components that look nice and are reusable.

When your worker script becomes very long and complex, developers like you and me find it very hard to manage the code itself. Using esbuild with Cloudflare Worker, you can separate your code into different files.

React is first choice, because of it's many web3 libs. Vercel is the easiest place deploying Next.js with Turborepo. However, by using vercel's useful features (Edge functions, ISR, etc.), it is more difficult to deploy to IPFS and make dApp fully decentralized. Vite or esbuild are also suitable for smaller applications and tools.

I have just started experimenting with the esbuild bundler as a package to use for go:generate, and go:embed.

esbuild https://esbuild.github.io/ I usually write my bundling progmatically with it now.

esbuild for using & bundling npm packages

integration with state-of-the-art JavaScript bundler - esbuild

The so-called 'next generation compilers' have been gaining more and more momentum recently. The revolution started with the Go language powering ESBuild and now it's mainly focused on Rust and tools like SWC. What's the point?  - one may ask. Well, back in the past, JavaScript was used to build small or medium-sized web pages. However, this changed years ago and there are huge applications composed of hundreds of views and thousands of files available on the market.

Packaging - turning all your code, CSS, assets, etc. into the files you'll actually stick on your host server. e.g. webpack, maybe esbuild, etc..

Where do you begin if the code was in hundreds of separate modules? It's not clear if it's easier. You would take time to load the code into your brain regardless of the structure.

By the way, JavaScript parser in esbuild is a 16 thousand lines of code module too:

https://github.com/evanw/esbuild/blob/0db0b46399de81fb29f6fc...