Frameworks and libraries should not be limited by ideology. The primary objective should be to utilize whatever is necessary to achieve the task at hand. And no more!
When creating websites, the focus should not be on competing to use the fewest (or most) number of tools, but rather on effectively serving users and ensuring their satisfaction.
*User experience should be the guiding principle.*
What concerns me about this article is their simplistic view that using a minimalist stack is solely a matter of choice, without acknowledging the nuances involved. It comes across as arrogant.
Furthermore, their demonstration of "building a website without frameworks and numerous libraries" is based on their own website, which is nothing more than a static landing page with links to blog posts.
Could anyone realistically build an Uber or an Airbnb using the same approach, even if they wanted to?
When creating websites, the focus should not be on competing to use the fewest (or most) number of tools, but rather on effectively serving users and ensuring their satisfaction.
*User experience should be the guiding principle.*
What concerns me about this article is their simplistic view that using a minimalist stack is solely a matter of choice, without acknowledging the nuances involved. It comes across as arrogant.
Furthermore, their demonstration of "building a website without frameworks and numerous libraries" is based on their own website, which is nothing more than a static landing page with links to blog posts.
Could anyone realistically build an Uber or an Airbnb using the same approach, even if they wanted to?