16 ms·
Hard to get past the wall of misinformation: > What we don't need when using Ferro > HTML > Javascript DOM finders (like jQuery, Zepto, ...) > Javascript libr
by ricardobeat 9y ago
Hard to get past the wall of misinformation:
> What we don't need when using Ferro
> HTML
> Javascript DOM finders (like jQuery, Zepto, ...)
> Javascript libraries/frameworks that extend html (like Ember, Angular, JSX, Vue, Stimulus)
> Shadow DOM Javascript frameworks (like React)
jQuery and Zepto are not “DOM finders”, they are cross-browser compatibility layers (that include querySelector).
“Frameworks that extend HTML” definitely encompasses Ferro itself.
React uses a virtual DOM. “Shadow DOM” is unrelated and part of the web components proposal.
- MrBra 9y agoWhatever they are, they suck. Actually what sucks is not them specifically, but the reason because they exist. Ferro makes the whole process more natural, at least.
- ricardobeat 9y agoIt’s easy (and meaningless) to criticise while not fully understanding what they do. From an architecture standpoint, this is very similar to building a tree of Backbone views + a few abstractions. Writing OO code instead of a markup language (JSX/HTML) has few intrinsic benefits besides “feels familiar to me”. And it goes head on against the resurgence of functional programming, reactive UI and declarative code. You need much more than “they suck” if you want to profess that your system is better. Not to say this isn’t worth exploring, but the bold and dismissive claims detract a lot from the project’s idea.
- MrBra 9y ago> if you want to profess that your system is better. Not sure if you thought I am the project creator or if you were just generally speaking. Anyway, if you wanted to know more about the rationale behind this project, you could address author's comment here: https://news.ycombinator.com/item?id=16571142 https://news.ycombinator.com/item?id=16571142