The value of frameworks is moving up the stack. Time to shed the "my component model is a special snowflake" bloat.
-
-
and I'm really glad we're moving to leaf nodes and away from <my-ajax> and <my-app> which just don't work.
-
another concern: WCs do a lot of standalone, non-coordinated work. At a client, I saw WCs that were making XHRs 1/
-
and sleep(250) *per component*. Possible to coordinate, but hard when isolation is the value prop. 2/2
-
TLDR I don't think anyone is "against" the tech per se; we are tired of being bludgeoned despite very real concerns.
-
there are some parallels with promises, but promises were a 1-year process with a ton of discussion from FWs and devs
-
let's get on that train and I bet the results will be good :-D
End of conversation
New conversation -
-
-
I think custom props and at-apply are solid but at-apply has no implementation progress yet so yeah not very usable right now :/
-
at-apply has no clear spec, that's a first problem. A second problem is that we need list-valued properties for it to work.
-
w/o something in the ballpark of at-apply, we can't even get off the ground on theming. Focus on theming is needed
-
Not entirely true. You can achieve the same thing without at-apply if you ask a preprocessor for help.
-
right. You can add stuff on top but then ppl looking at the spec go

-
especially since the argument is that we standardize as a community around the spec to reduce "special snowflake"!
-
you can literally use at-apply and have a preprocessor make it work for u; i'd call that an ok polyfill while we get there
-
maybe what we need is tracked process towards goals rather than techs. "can we theme yet?" "can we self-host yet?"
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.