Re: [css-houdini-drafts] [css-paint-api] Use JS export instead of registerPaint

I agree with Tab and Surma, an interesting idea, but let's not.

1) the whole point of Houdini is to *not* add more magic to the platform. Especially not adding declarative behavior to imperative code. This is imperative code for a reason.
2) this overloads the concept of exporting from a module. What happens when there's a use for loading the same module elsewhere? There would then be a need to export things other than painters. Would we then need a new type of export?
3) what about when we want to add new behaviors or classes to custom painters? Which is which?

We'd be giving up a lot of extensibility and future-proofing to save literally one line of code.

-- 
GitHub Notification of comment by plinss
Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/564#issuecomment-359266565 using your GitHub account

Received on Sunday, 21 January 2018 17:51:10 UTC