I mean there are many more reasons. I just don’t care for how Angular looks. But my comments were more about thick clients and the state of web components.
Web components are a standard. That is true. I am 100 percent on board with standards. But we are not ready for them. And the standard we ended up with is much worse than the standard we were suppose to get (thanks Safari).
Nothing I have seen has shown the output as smaller than Svelte. One of the reasons we ruled it out was because of browser support, and output size. But I may be miss remembering.
Either way, I will jump on web components, when it makes sense for the work that I do, and if the adoption curve gets better by the community.
In general, building them without a framework does not appeal to me. Having them, even if they are standard, does not appeal to me for numerous reasons. And using a framework to improve the developer experience, cool. But then I should be using something that builds something I actually want. Hence Svelte.
I am not hating on Stencil. It’s fine. I just don’t think I want this thick client web we make every site out of. And the current standard of web components does little to mitigate that, if we put css and html in JS.
Web Components still require polyfills. The argument that these big companies ship them is fine, if you have the same user base as those companies and can alienate the same set of browser users.
I mean, if they work for you, and your happy with the framework. Congrats. I don’t need to keep going against every point you want to try and dismiss. It’s simple. Moving CSS and HTML into JS is thick client still. Might be lighter weight than a virtual dom, but it has ramifications. I have to support a wider range of users than you, and hence can’t use the features without polyfills.
So like I said before, I don’t feel we are ready for mass adoptions. Most websites can’t abandon IE11 or Edge. And I won’t use a collection of polyfills just so I can develop with a framework. Why punish the user. They don’t care that your using web components. They just want the site to be fast and work. So use the technology that does that the best. For me, that is Svelte or just native HTML, CSS and JS.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I mean there are many more reasons. I just don’t care for how Angular looks. But my comments were more about thick clients and the state of web components.
Web components are a standard. That is true. I am 100 percent on board with standards. But we are not ready for them. And the standard we ended up with is much worse than the standard we were suppose to get (thanks Safari).
Nothing I have seen has shown the output as smaller than Svelte. One of the reasons we ruled it out was because of browser support, and output size. But I may be miss remembering.
Either way, I will jump on web components, when it makes sense for the work that I do, and if the adoption curve gets better by the community.
In general, building them without a framework does not appeal to me. Having them, even if they are standard, does not appeal to me for numerous reasons. And using a framework to improve the developer experience, cool. But then I should be using something that builds something I actually want. Hence Svelte.
I am not hating on Stencil. It’s fine. I just don’t think I want this thick client web we make every site out of. And the current standard of web components does little to mitigate that, if we put css and html in JS.
Why do you say that? I definitely think we're ready for them. Apple, Amazon, and Google are all shipping them to prod.
Open the article I posted earlier and check for yourself.
Stencil is the opposite of Thick UI. 0 framework, 0 esoteric syntax as in Svelte's case, just pure web-based development with a small vdom.
pianomanfrazier.com/post/comparing...
This is just one example. But yeah, it’s larger.
Web Components still require polyfills. The argument that these big companies ship them is fine, if you have the same user base as those companies and can alienate the same set of browser users.
I still have to support IE 11 for example. caniuse.com/#search=Web%20components
I mean, if they work for you, and your happy with the framework. Congrats. I don’t need to keep going against every point you want to try and dismiss. It’s simple. Moving CSS and HTML into JS is thick client still. Might be lighter weight than a virtual dom, but it has ramifications. I have to support a wider range of users than you, and hence can’t use the features without polyfills.
So like I said before, I don’t feel we are ready for mass adoptions. Most websites can’t abandon IE11 or Edge. And I won’t use a collection of polyfills just so I can develop with a framework. Why punish the user. They don’t care that your using web components. They just want the site to be fast and work. So use the technology that does that the best. For me, that is Svelte or just native HTML, CSS and JS.