ooh cool! Which bench did you use? - Snabdom doesn't operate on DOM nodes tho -> framework lock-in :(
-
-
Pretty used to virtual doms now, but dealing w/ direct dom nodes for data viz & animation would be nice
2 replies 0 retweets 0 likes -
yeah, exactly! Could also start moving towards universal widgets using https://github.com/shama/on-load
1 reply 0 retweets 3 likes -
Replying to @yoshuawuyts @_joshburgess and
would love for frontend to be in a place where frameworks are just taste; widgets being fully portable
2 replies 0 retweets 5 likes -
Replying to @yoshuawuyts @andrestaltz
very cool +1. would love to read critique of https://github.com/rijs/fullstack/blob/master/README.md … + for components: https://github.com/rijs/docs/blob/master/components.md …
1 reply 0 retweets 0 likes -
component as just fn works v well in node, doesn't need a framework!: fn.call(<el>, data)https://github.com/pemrouz/vanilla
1 reply 0 retweets 1 like -
Replying to @pemrouz
yeah, quick scan of what you're saying makes sense. Sheetify is my answer to shadow CSS btw https://github.com/stackcss/sheetify …, seems close
1 reply 0 retweets 2 likes -
Replying to @yoshuawuyts
+1 for :host. precss does same, s/hash/tagname (WCs ftw). shied away from coupling with browserify tho, bundling anti-pattern.
1 reply 0 retweets 1 like
I find it easier to combine using JS; can always extract and optimize later using https://github.com/stackcss/css-extract … and custom chain
-
-
Replying to @yoshuawuyts
I actually meant bundling altogether is anti-pattern
(over-fetches). also, simple vs easy https://www.infoq.com/presentations/Simple-Made-Easy …1 reply 0 retweets 0 likes -
Replying to @pemrouz
oh I definitely agree; network roundtrips are more expensive and HTTP2 isn't everywhere yet. If an app is 10kb then it's easy
1 reply 0 retweets 0 likes - 8 more replies
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.