This is great news for the OSS community. More importantly the news that GraphQL changing licenses is very welcoming: details here Not much more that i can say to be honest, things like this are simply good news.

This follows typical CSS structures. Ideally you should place all of the critical CSS in the child. This child should then be responsible for its defualt structure and style. The parent may or may not choose to change that components CSS. It depends on the context. For example: A button component has its default styling, this will be things like size, colour ect. I use this button component in my 'page' component. However in this case I was it positioned fixed, so my parent component will do this as this is styling in in the context of this components layout structure. Hope that helps

We will be making a public road map of things happening in Vue, to make it easier for you to keep track. Vue 3 is going to have little API changes - the main difference is it will only target modern "evergreen" browsers (i.e. IE11 & below are out). What are the benefits? Reactivity system will use ES2015 Proxies. This will get rid of most if not all of the caveats in the current reactivity system, and should improve performance as well. Internal code size reductions: there is lots of code dealing with compatibility. All if this logic can be dumped. v2/v3 will be maintained in parallel with feature parity until the older browsers completely phase out. It will mainly be a choice of what browsers you support.

Although i don't recommend overwriting the body, you can do something like this. https://jsfiddle.net/1u1h4e1k/1/ You could also get the innerHTML of the body to replace the body as is.

Reversed order: 3) Thank you, we have more logo's on the way for the supporting ecosystem. 2) With 12 lines of code you can make Vue functional: https://t.co/shq8jeCSk0 1) No, Vue is being used by large enterprise companies for large projects. So by that factor, it works. Like React, Angular and others libraries i can't see any issues with scaling. With large project the main factor is keeping code constistant and clean. Vue is known for it's abilitity to be simple and lean, so that in itself massively helps scale Vue applications.

To me also it matters more about those using the tool, and people use Vue this is what will keep the ecosystem running. There are more and more companies using Vue, including some very big names. Who have vested interest in supporting the ecosystem. So there is no worries of Vue dying out, as we will continue to support and make it better.

I think currently the OSS community is maturing across the board, there are many great devs out there that have done a fantastic job at promoting the value of OSS. It can however be difficult, and lots of our time is unpaid and completely voluntary. So the main thing i can say is be nice, there is nothing more frustrating than being had a go at. Building a friendly community and being friendly in that community, is key in my opinion.

This is a nice idea, we will look into it :)

I think discord is great, I am a late comer to using discord. But with my brief experience it looks to me that it's doing better at it's job compared to that of gitter.im

I believe this to be true, it certainly evolved with the learnings from other frameworks/libraries. As do many other frameworks, the great thing about OSS is that we can learn from each other to make the web a better platform to develop on.