Couldn’t agree more: the attitude I’ve developed as I’ve progressed through seeing many web and native projects from conception to completion is that adding a n

Couldn’t agree more: the attitude I’ve developed as I’ve progressed through seeing many web and native projects from conception to completion is that adding a new tool or dependency is not as cheap as it first seems - each new tool compounds complexity, makes it harder for others to contribute and is a source of future fragility to the project I suspect the web’s low barrier to entry (which is a wonderful thing) means a large proportion of developers are relatively junior and the prevailing voices encouraging these development patterns reflect this The browser stack is incredible and you can make great things and have a wonderful experience building them but I would avoid listening to popular takes on how to do it - you’ll have a better time working from first principles and just using what makes sense to you given your experience I’m curious to hear other options on this but over time when reviewing a library or tool I’ve come to learn different signals: a library or tool with a website with serious design effort put into it has become to me a signal to be seriously sceptical of value - doubly so if it features the phrase “blazing fast”. And a tool presented with html 1.0 almost zero CSS, Fabrice Bellard-style [0], that’s the good stuff worth paying attention to [0] https://bellard.org/ https://bellard.org/