lightblade

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.

> Standard / Official way of doing things

If you like that, why not go with Ember?

I would imagine this works in your terminal too.

Is eBay.com built with Marko?

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.

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.

I like to see some evidence of this claim. Certainly Alibaba.com is not built with Vue.

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?

That's also why taking on Vue is a huge risk. The project has a high bus factor. If the main author burnt out and quit, the project is dead.

Nurse is licensed though. That's instant credibility.

Interesting...

Since requestIdleCallback leaves the scheduling out of your hand, how do you ensure nodes are still updated when you need it? Like tests?