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

Re:Vanilla-todo: A case study on viable techniques for vanil... by wtetzner on Tuesday October 27, 2020 @10:59AM (#24908043)

> These usually end up becoming a custom micro-framework, thereby questioning why you didn't use one of the established and tested libraries/frameworks in the first place.

Often a custom micro-framework better suits the needs of a particular project.

I've written micro-frameworks for specific projects intentionally, because they did a few things that the established frameworks either didn't do, or it was very difficult to get them to do.

An additional benefit was that using the micro frameworks ended up being simpler, and the startup time was much, much faster.

Whether or not you use an existing framework depends on how much effort it is to write and test a custom framework vs the amount of effort you'd need to put in to use an existing framework.

The ones I've written have been pretty quick to develop, and were also intended to be used for a few different projects that had similar needs.

Edit: Just for clarification, the micro frameworks I've written are server-side, if that makes any difference.

[ Parent | on HN ]

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 ]

Re:Vanilla-todo: A case study on viable techniques for vanil... by chpmrc on Wednesday October 28, 2020 @09:16AM (#24918346)

I'm sure there are exceptions (yours might be one) but this:

> I've written micro-frameworks for specific projects intentionally, because they did a few things that the established frameworks either didn't do, or it was very difficult to get them to do.

Is a false statement in most projects. I'd even argue in all projects except those that have a very strict limit on time or memory usage (or a legal one).

Can you share an example?

[ Parent | on HN ]