all of the things you listed are included in the software. and they all serve the same thing. to maintain the software. you should focus on the purpose as much as you focus on the process.
I totally agree with this comment. just such a person was the manager of the team I was on. and it wasn't really possible to argue. The only thing he understands from arguing is that he is right in the end. Imagine this happening even in the smallest of arguments.
tailwind is a library I don't like in many ways, but the criticisms in this post are pretty ridiculous. tailwind is not a library offered with the motto of component driven as the author mentioned. and instead of bloated packages like radix ui I think it's a more sensible solution. at least it gives a chance to follow a more optimal path. I think it is impossible to find an optimal way with the libraries it recommends. you should use everything just as the library intended.
> tailwind is not a library offered with the motto of component driven as the author mentioned.
I thought Tailwind shined the most when used within components (and why it's become so popular with React).. making components and not CSS the nexus of abstraction.
> and instead of bloated packages like radix ui I think it's a more sensible solution. ... I think it is impossible to find an optimal way with the libraries it recommends.
The author recommends ThemeUI, Rebass, Stitches and/or Radix for design systems. They might add undue bundle size, to various degrees.
But a recent and very powerful (close to as optimal as possible?) alternative is Tamagui which takes inspiration from all of those. All for the cost of some 20-27 kB, apparently with a clear path to come below 8 kB in the future: https://tamagui.dev/blog/version-one#bundle-size-reduction
It's an interesting idea to write the app based on the tests instead of writing the test by the app. I don't think it will be very healthy for the overall application, but it's worth a try. Testing with real dependencies without using mock seems better overall, but this brings with it quite a few problems.
Enterprise software is the software that mostly lies and bullshit today. Companies spend a lot of money because at the end of the day, it's working. Who cares how it works.
godaddy and namecheap. If you are using these two sites in some way and paying money, what you need to do as soon as possible is to transfer all your domains to another site and delete your account. As long as you keep using these idiots they will continue to grow more.
The maintenance cost is a debt that must be paid by all means. and microservices may be the cleanest solution if there are teams that develop businesses completely independent of each other.
for most libraries, I think people in core teams cause it. eg react is destroying the potential of hooks more and more with each release. and it's weird that no one of them said, "what are we doing right now, does this stuff really have to be this complicated", but I guess that's exactly what open source development culture is today. we know best and you should use it.
