HN user

tvphan

84 karma
Posts0
Comments31
View on HN
No posts found.

I suspect the person who created this chart probably reckoned that anything less than “using Huawei” is a bad thing

Mate, you gotta chill. You seem very triggered by Tailwind! You don't have to use it if you don't want...

Some comments:

- It's very easy to integrate Sass with Tailwind. You can import the Tailwind classes just like you would Bootstrap: https://tailwindcss.com/docs/using-with-preprocessors#using-...

- You are also allowed to write semantic classes as well: https://tailwindcss.com/docs/extracting-components

I would argue the main point would be you can rapidly build interfaces... like really fast. I worked on a proposal for a client using Tailwind a month ago and we smashed out a whole website in a week. We ended up "extracting components" like buttons and cards and stuff that we found was being reused a lot (kinda like Sass).

As opposed to Styled-Components, the Tailwind classes are very valuable for designers who want to prototype live in the browser.

Also, you were complaining before about design consistency but I would argue that Tailwind allows for very high design consistency. I work with armies of outsourced developers of varying skillsets and I honestly don't trust a lot of them to write clean CSS at all. With Tailwind and Tailwind design tokens, the army of outsource developers are encouraged to work with the design tokens (as opposed to yolo'ing 3px !important everywhere).

There’s a new wave of thought in design called “design tokens” where you have a set of predefined values that are considered valid as part of the design, e.g. a website can only have spacing of 4px, 8px, 16px, etc.

One component having mr-4 and another having mr-3 is chill if that was the designer’s intention. If not, then it should be picked up during design review and easily fixed (since you end up really only having to pick from like a few values).

I love React and would recommend it as the primary frontend library. However, I would suggest avoiding the Material UI component library entirely (as I believe it’s both difficult to customise and over-engineered) and just write SASS to start off.

If you really like how Angular 1 worked (writing templates instead of JS to represent DOM) then Vue is a great choice.

I thought the same thing until you start to think in terms of “constraint-based components”, which are more easily done in CSS-in-JS. Styling is done by passing properties to a component, e.g. <Heading color=“primary” />, and only the developer building the primitive component needs to worry about styling. You end up being able to rapidly develop interfaces that match the designs.

The Material UI library for React is such a piece of garbage and I actually believe it’s one of the main reasons why so many devs hate React. You can use React without and your happy will be so much happier!!

Angular 9.0 6 years ago

Most popular re-usable component libraries and websites are written in React.

Angular v8.0 7 years ago

The Stack Overflow developer survey showed that React and Angular are neck to neck so there's obviously a lot of people who use it.

However, you can see just how popular React is by number of npm packages that depend on it: https://github.com/facebook/react

Similar to how Singaporean English have dropped a bunch of ending consonants from English, Mandarin dropped a bunch of ending consonants from Middle Chinese. If you recited this in Cantonese (which is a bit more conservative dialect), the words would sound differently!

You've managed to live in different cities for work, e.g. Madison, London, DC! That means you've gained invaluable life experience. I'm pretty jealous of that TBH.