When you write JavaScript, you can only optimize it..as JavaScript. It still needs to be parsed, compiled, and optimized as JavaScript.
When you write templates, you get more room for optimization. Glimmer engine compiles templates to binary bytecodes to bypass JavaScript parsing. Vue3 inlines component fragments as part of the compilation step.
Glimmer compiles to bytecode, but I am not sure how that “bypass[es] JavaScript parsing” as the bytecode is evaluated by a runtime written in JS (which is obviously parsed) and that translates the bytecode into JS calls. Basically one type of parsing has been replaced with another, which is fine though not obviously faster.
Likewise, I don’t see the point with Vue since again vue templates are translated into JS calls.
Or you could just make JS calls, like React does, no runtime translation required.
Not sure how much it's used on ebay.com but from this presentation it seems to imply that it's used extensively on the site and other projects at the company.
Yes, that is correct. The presenter in that video is Patrick Steele-Idem, the original creator of Marko. eBay.com is predominately built using Marko and Lasso https://github.com/lasso-js/lasso
We use a combination of Atomics and BEM in our project.
Atomics offers single level specificity thus providing a strategy to combat the specificity problem that plagues many projects.
They are single purpose and infinitely composable, which complements very well with component oriented architecture that's popular today.
They are localized to single DOM node. When combined with its single purpose nature offers fewer surprises when making changes to your style sheet. For example, when you add a margin 15 Atomics to a DOM node, it is very hard to accidentally add another margin 15 somewhere else. Versus if you add a label class, it is much easier to accidentally add another label class and cause unintended consequences.
this, pretty much. it's as declarative and surprise-free as you can get in CSS and it works super well when abstracted into components.
I know it isn't the easiest to read and it seems counterintuitive at first, but in practice you can easily encapsulate long chains of inline classes into helper classes thus giving most projects a sort of sane middle ground.
That's the thing. All claims of Alibaba's adoption of Vue comes from the author himself. I think it's reasonable to have doubt. I'm sure they use it. But to claim that they heavily invest in it may be exaggerated.
Yes, he has openly said he is funded through patreon. Now that the framework is super popular, he may have other sources of income, but it's not built by/for/in Alibaba afaik.
Vue is used by huge Chinese companies, and tons of Chinese startups. It's also adopted by Laravel, which is very popular in PHP land. It's not going anywhere soon.
That is the word on the street, but I have yet to see publicly visible evidence of it. You can inspect Facebook to see React is there. You can inspect Walmart to see React is there. You can inspect LinkedIn to find Ember there. I have yet to see flagship product of huge companies built on Angular or Vue. Is Alibaba.com built with Vue?
It definitely is not because not only are there other contributors but Alibaba and Monterail have also made meaningful contributions (the former also developing an analog to React-Native but with Vue).
Exactly. Also, the supply of nurses is highly constrained in the Bay Area due to a very small number of people able to graduate. There's actually a lottery to enter a registered nurse program and last time I checked the odds were less than 30% to win the ticket. Besides that, hospitals lose state subsidies if their nurse/patient ratio drops below a certain threshold. It's really apples-to-oranges.
Not to mention "useful". Imagine nurses going on strike. Now compare that to lawyers, programmers or investment bankers going on strike ... no one cares.
Not to mention an airline. The recent British Airways debacle was caused by a technical problem, but if the IT workers had gone on strike, similar problems could have resulted.
With the ability to pause large updates in the middle without committing them to UI, doing some higher priority updates, and then "rebasing" lower priority updates on top of them and continuing the work. So it's a bit more sophisticated.
Yea, it does. We are using requestIdleCallback to do the work "while we can", and then yield the control back. Again, this won't be a part of React 16, but it's part of the bigger picture we are moving towards.
When you write templates, you get more room for optimization. Glimmer engine compiles templates to binary bytecodes to bypass JavaScript parsing. Vue3 inlines component fragments as part of the compilation step.