1. 10
  1. 15

    Now we can use Python to download a 43M binary from Github that contains some version of node.js and bundles tailwindcss.

    Is this the future we wanted?

    1. 11

      As much as I don’t agree with the philosophy behind Tailwind CSS, in this case, the bundling of node.js is explicitly a stepping-stone towards a completely Python solution, and I like solutions that are stepping stones towards better.

    2. 5

      I’m not really in the frontend world. Could someone please explain to me why a .css file needs installing?

      1. 5

        I’m not, but I’ll try to explain: Tailwind has several classes, and post-processes the ones you don’t use out of your site.

        1. 3

          It isn’t a CSS file. It’s a system for generating a CSS file.

        2. 4

          unfortunately python is still required

          1. 7

            Now we just need someone to package python + pip into a zip on GitHub and setup a bash script to install that to install tailwind. (kidding, I do get that the goal is to get everything to also be implemented in python)

            I’m not really sure I understand the desire to port projects that were relying on Node into Python, Ruby, etc. Node “won” the competition around how to compile front-end assets years ago. If Node requires too much fiddling around, why not improve the Node ecosystem, instead of porting a bunch of the logic to another platform?

            It is open source code though, so people should work on whatever makes them happy inside.

            1. 6

              https://deno.land/ is a great alternative to node