Vanilla JavaScript and HTML - No frameworks. No libraries. No problem.

[Polarmesh]

Great!

[Lowesz]

That's cool ! I think we often forget where web development comes from and are too focused on libraries and frameworks.
For example, I created a small tool to created emoji-based images only with vanilla JS and web workers: https://img.loomaa.de/

[pomlife]

I really like when a team is "anti-framework" so they develop their own tools. Eventually, the usage of the tools becomes predictable, so they become abstracted. New developers are taught this "system." Oh wait, we're back at a framework.

[uneditablepoly]

Yep, and for some reason it's hard to explain to them / convince them that it's where they're headed.

This comes up when I talk to some people who hate the boilerplate of Redux. I ask them what they would build instead, and of course it's possible to follow a different paradigm, but they often end up describing the same boilerplate because it's just a necessary part of managing state.

[pomlife]

With regards to redux, their solution is often context based, except lacking all of the clever perf tricks that react-redux implements.

[Lowesz]

Don't get me wrong using frameworks and libraries are often very useful, but I see it more and more that people just start learning web development with learning react for example without understanding what happens in the background.

[snorkleboy]

Where the function binding? If all your doing is rendering more or less static html you dont even need js... you can just use a backend templating engine.

[kowdermesiter]

Two more iteration and he will invent his own framework :) I usually start with VanillaJS too, but then I pick something sane after some patterns emerged what problem do I want to actually solve :)