Coding is as much a matter of personal growth as it is of logic and control-flow. I keep patience, curiosity, & exuberance in the same toolbox as vim and git.
*Opinions posted are my own*
Polycasts with rob dodson were awesome in their day
There are web component meetups regularly in amsterdam I believe
Vaadin is huuuuge in wc development and advocacy
github uses custom elements
That's what I came up with just off my fingertips. But also, when was the last time you attended a querySelectorConf?
so I'd like to suggest that the reason you don't see more is because you're not looking hard enough ;)
To be fair, my oft-repeated complaint in the Polymer Community Slack is that not enough resources are being directed to advocacy and community building. Lately I've been hearing subterranean rumblings that the situation on that front might improve.
I think the point was about "niche" not existance as such. Although there might be a ton of resources out there, I too believe it is not - let's say - well marketed.
On the other hand, I see this fruitful discussion as an opportunity for me, to take a look at what exactly WC are - if that was intended: mission accomplished 😄
I have a dark fuzzy image of it which eventually needs some details.
But anyway: the point of not having a querySelector conf is, that I suspect it being common shared knowledge in contrast to not so common knowledge about WC.
There are plenty of resources about WebComponents. Nearly none of them are about WebComponents though. They are about Polymer. Or Stencil. Or lit-html. Or...
There's a Polymer summit. I don't think there's a Web Components conference.
It's probably the first time in the history of web standards that the new "use the platform" and the new "use the APIs" are rarely if ever mentioned in any of the resources dedicated to them.
People keep mentioning jQuery. However, as the platform develops, there's less and less need for jQuery (querySelector, fetch, etc.). The platform developed to include WebComponents, and they somehow don't reduce the need for libraries. Instead, they all but require libraries to be even remotely usable.
And that is specifically because of a new trend in web standards about which I have mixed feelings.
Specifically, more low level APIs intended to be consumed less by web client developers directly and more by web tool/framework developers.
The idea is that web standards will be able to move faster and satisfy real (vs imagined) needs better if there is more dialogue with "userland" solutions. I get the impression they don't want to spend a lot of time on API usability only to find there are major problems with or no value in the essential features. (For example, almost a decade was arguably wasted on XML as a way to extend HTML, while multiple frameworks found their own ways to do it and thereby also uncovered a dozen OTHER needs in the platform.)
So there's definitely SOME inaccuracy to the framing of using the platform being about not using libraries at all. But honestly I think this argument usually involves people talking past each other, not with each other.
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.
That's what I came up with just off my fingertips. But also, when was the last time you attended a
querySelectorConf?so I'd like to suggest that the reason you don't see more is because you're not looking hard enough ;)
To be fair, my oft-repeated complaint in the Polymer Community Slack is that not enough resources are being directed to advocacy and community building. Lately I've been hearing subterranean rumblings that the situation on that front might improve.
I think the point was about "niche" not existance as such. Although there might be a ton of resources out there, I too believe it is not - let's say - well marketed.
On the other hand, I see this fruitful discussion as an opportunity for me, to take a look at what exactly WC are - if that was intended: mission accomplished 😄
I have a dark fuzzy image of it which eventually needs some details.
But anyway: the point of not having a querySelector conf is, that I suspect it being common shared knowledge in contrast to not so common knowledge about WC.
There are plenty of resources about WebComponents. Nearly none of them are about WebComponents though. They are about Polymer. Or Stencil. Or lit-html. Or...
There's a Polymer summit. I don't think there's a Web Components conference.
It's probably the first time in the history of web standards that the new "use the platform" and the new "use the APIs" are rarely if ever mentioned in any of the resources dedicated to them.
People keep mentioning jQuery. However, as the platform develops, there's less and less need for jQuery (querySelector, fetch, etc.). The platform developed to include WebComponents, and they somehow don't reduce the need for libraries. Instead, they all but require libraries to be even remotely usable.
And that is specifically because of a new trend in web standards about which I have mixed feelings.
Specifically, more low level APIs intended to be consumed less by web client developers directly and more by web tool/framework developers.
The idea is that web standards will be able to move faster and satisfy real (vs imagined) needs better if there is more dialogue with "userland" solutions. I get the impression they don't want to spend a lot of time on API usability only to find there are major problems with or no value in the essential features. (For example, almost a decade was arguably wasted on XML as a way to extend HTML, while multiple frameworks found their own ways to do it and thereby also uncovered a dozen OTHER needs in the platform.)
So there's definitely SOME inaccuracy to the framing of using the platform being about not using libraries at all. But honestly I think this argument usually involves people talking past each other, not with each other.