3 ms·
> That's an additional cost you pay every time you onboard someone who will deal with your frontend. Huh, but if you have an "we made it ourselves" framework,
by netsharc 7y ago
> That's an additional cost you pay every time you onboard someone who will deal with your frontend.
Huh, but if you have an "we made it ourselves" framework, won't that cost still be there too?
Whereas nowadays employers can just demand experience with jQuery or Angular, because they became standards. Maybe if Tailwind got popular enough, employers can save costs by just looking for devs with experience in them.
- gambler 7y ago>Huh, but if you have an "we made it ourselves" framework, won't that cost still be there too? In many real-life scenarios it's not a matter of learning a 3d party library or an in-house product. You often have to learn some in-house product regardless and every 3d party library is an extra. It's not nearly as cut-and-dry as many people make it out to be. There are many, many specific questions that have to be asked when choosing whether to write or buy.