[algorithm_dk]

Why not cut out the middle man and just apply the css directly Well one could extend this and argue that there's not need for frontend frameworks as you can manipulate the dom directly. Two way data binding is awesome.

I have no idea about the lazy loading. And yeah, it's "kind of image processing".

[tomelders]

No. It makes sense to use a library that implements a VDOM and efficient Dom Diffing because that's hard to implement yourself.

And there is no need for front end frameworks at all. They should be avoided entirely.

And two way data binding is for fools.

[algorithm_dk]

Well, if you think that, why are you arguing over a submission about a component for one of those frameworks? You think it's useless just because you don't use something like Vue?

I'm not sure if you're trolling or not at this point.

[tomelders]

You don’t have to use Vue as a framework. You can opt just to use the view layer as a library.

[mockingbirdy]

Vue implements a vdom, but never mind.

This comment is so subjective and unsubstantiated that it hurts the reputation of HN of having high quality comments.

> And two way data binding is for fools.

Pretty sure that this is against the HN guidelines. Please read them [1].

[1]: https://news.ycombinator.com/newsguidelines.html

[tomelders]

I wasn't saying "don't use Vue", I was saying there are good reasons to use a view layer library, and I used "VDOM" as a relevant example specifically because Vue implements one.

And two way data bindings are the best way to make a code base inscrutable. I'll put it another way. Wise developers avoid two way data bindings.