Building a Front End Framework; Reactivity, Composability with No Dependencies

Re:Building a Front End Framework; Reactivity, Composability... by bitL on Sunday May 14, 2023 @12:47PM (#35939281)

Not always, some can hit the sweet spot of being simple in all phases of development and quick to learn. They are super rare though and their lessons are forgotten; industry often standardizes on inferior things with better marketing.

[ Parent | on HN ]

Re:Building a Front End Framework; Reactivity, Composability... by karpierz on Sunday May 14, 2023 @01:08PM (#35939430)

What are some examples?

[ Parent | on HN ]

Re:Building a Front End Framework; Reactivity, Composability... by ipaddr on Sunday May 14, 2023 @03:42PM (#35940771)

jQuery

[ Parent | on HN ]

Re:Building a Front End Framework; Reactivity, Composability... by klysm on Monday May 15, 2023 @11:40PM (#35957506)

I’d argue it’s evident large jQuery apps are a pain in the ass to maintain

[ Parent | on HN ]

Re:Building a Front End Framework; Reactivity, Composability... by arcanemachiner on Sunday May 14, 2023 @04:14PM (#35941014)

I think Alpine.JS hits this spot pretty well.

https://alpinejs.dev/

[ Parent | on HN ]

Re:Building a Front End Framework; Reactivity, Composability... by balder1991 on Sunday May 14, 2023 @04:23PM (#35941087)

[deleted]

[ Parent | on HN ]

Re:Building a Front End Framework; Reactivity, Composability... by balder1991 on Sunday May 14, 2023 @04:24PM (#35941094)

> industry often standardizes on inferior things with better marketing.

It standardizes to what’s cheaper on their eyes, sometimes in a very short-sided way, but also companies that work for profit never know if a project will still be running in the next quarter, right? It makes me think that open source and for profit companies should have very different considerations when it comes to choosing frameworks or technologies for their solutions. I should probably gather more info on that and expand it into a blog article.

[ Parent | on HN ]