News for hackers. Stuff that matters.

A comment on Vanilla-todo: A case study on viable techniques for vanilla web development. Parent comment

Re:Vanilla-todo: A case study on viable techniques for vanil... by notJim on Tuesday October 27, 2020 @03:48PM (#24911050)
> Often a custom micro-framework better suits the needs of a particular project.

Fitting the needs of a particular project is frequently a local optimum however. Often, it's much more optimal to focus on the needs of a whole team or even whole company. You can hire people who already know React/Vue/whatever, but there is no one in the world who knows your micro-framework.

[ Parent | on HN ]
Re:Vanilla-todo: A case study on viable techniques for vanil... by CmdrKrool on Tuesday October 27, 2020 @04:04PM (#24911205)
But due to its micro-size, it won't take long to learn.
[ Parent | on HN ]
Re:Vanilla-todo: A case study on viable techniques for vanil... by notJim on Tuesday October 27, 2020 @05:44PM (#24912284)
Micro-frameworks have a nasty habit of outgrowing the description, IME.
[ Parent | on HN ]
Re:Vanilla-todo: A case study on viable techniques for vanil... by randall on Wednesday October 28, 2020 @10:45AM (#24919294)
It's always "tear it down" or "build it up" at the end of the day. Which one takes more effort is the right one to optimize for with your particular use case.

Rails vs Sinatra is a great example.

[ Parent | on HN ]