3 ms·
As a somewhat fad averse engineer who has more or less settled into his own preferred toolchain for FE and BE JavaScript, I plan to invest some time in next.js,
by davedx 6y ago
As a somewhat fad averse engineer who has more or less settled into his own preferred toolchain for FE and BE JavaScript, I plan to invest some time in next.js, tailwind and emotion soon ish. Great to see the state of the art still being pushed. Might see how feasible porting my existing nodejs projects to deno is too.
- christophilus 6y agoI tried a deno port, but lack of crypto support was a showstopper. I think I could’ve done it if not for that. It’s quite a lot nicer than node, though, and I definitely will give it another go when it’s further along.
- qudat 6y agoWe use tailwind in production at the company I work for and it works well enough. I'd also recommend looking into https://chakra-ui.com/ https://chakra-ui.com/
- ljoshua 6y agoI quite enjoy Tailwind, and have used it in several production projects. When using Tailwind, don't forget that it is not only to be used as a utility-like CSS framework, but is also intended to build your own CSS systems. You can customize it and build your own classes using the `@apply` directive and other tools so that you don't copy/paste the same utility classes all over the place, but instead use CSS as we used to back in the good ol' days, with custom classes. :)
- cuddlecake 6y agoI personally would recommend against making a lot of custom classes via @apply, especially when pairing with a component based framework like React. React makes it easy to avoid the need for duplicate naming such as 'btn' css class and a <Button> component. I would also recommend twin.macro, though I'm still on the fence about using it. At the very least, it helps with difficult things like style overwrites, ensuring utilities are spelled correctly, conditionally applying utilities and bailwind (one-off styles)