RT @seldo: The official Republican policy platform is “nothing, but we support the president” and 6 of the 12 keynote speakers at the RNC…

RT @Timodc: Don’t generally see a presidential appointee explicitly endorse overthrowing democracy in favor of tyranny. https://t.co/OpeFrB…

RT @HoarseWisperer: Melanie basically turned the White House Rose Garden into the back entrance to a Sheraton conference center. https://t.…

@justinfagnani I’m not suggesting you do. I believe firmly there is no one true library/framework for all use cases, each have their own PoVs, that that’s healthy, that they should be chosen based on how they align with/your needs, & everyone should choose the comexity they’re willing to take

@justinfagnani @bitworking CSS modules aren’t a browser thing yet, though, and I’m really not interested in runtime Sass/doing Sass like things (like loops and it’s) if it’s JS based because of how important it is that CSS doesn’t contribute to style blocking

@justinfagnani I totally get it! And I agree! But at some point, for me at least, JS purity means less to me than everyone I’m working with being productive while still providing great performance and UX

@justinfagnani Guess my point is if you come at templating JS first, having it all be pure JS feels natural, but coming at it HTML/CSS first, something that feels more like HTML and CSS feels more natural. Many JRs and designers I work with are the later (and really do am I to sing extent)

@justinfagnani {%for item in items} <li>{{item}}</li>{% endfor } IMO is easier to grok than html${items.forEach(item => html<li>${item}</li>)}, especially when the stuff in loops gets more complicated and has more interpolation inside.

@justinfagnani Was looking at official docs.

As for a templating DSL, I disagree. I find purpose-built tempting DSLs are easier to understand that trying to manipulate JS+string concatenation, esp w/Lit where everything needs to be wrapped in html functions inside interpolation

@justinfagnani @bitworking Yup! I know. But integrating that with Sass isn’t straight forward, and writing CSS in a JS string is more difficult (tooling/conceptually/for non-JS heavy people) than a style tag or a separate file. Lots of it is death by a thousand papercuts.

@justinfagnani Yup, had this set up. Worked fine for HTML, but not well for CSS

@justinfagnani That’s what I was doing, but having everything in one file is not the same as the SFC paradigm. instagram.com/p/CEPUqYqJbl2/?igshid=1pgyuzs7xhmj3 does it, but it’s Webpack only.

@bitworking @justinfagnani Yeah, Shadow DOM is def a big part of the style problem. Sharing styles, having a baseline shared set of styles, all made more difficult with SD.

RT @everestpipkin: every few years i email neopets support asking if they can help me log into my childhood account and (unsurprisingly, ti…

@justinfagnani One last thing here: I don’t dislike lit-element. I’ve built WCs by hand and think the DX over that is fantastic, and if it was just me coding, I’d probably have stuck it out. But because it’s not just me and skill levels vary, the parts that were a drag became blockers

@justinfagnani There are also some small things, like me preferring Rollup & most community tools I saw were for Webpack, syntax highlighting, prettier, & Emmet support across the various layers (esp CSS), & needing to understand WC quirks (esp w/style) to use (higher barrier to entry for JRs)

@justinfagnani I much prefer the single file component/template DSL model. This is a pattern I’ve seen with React, BTW, where SFC is easier to grok immediately and easier to contribute to for people who aren’t JS devs; feels less intimidating, more familiar to just HTML/CSS 2/2

@justinfagnani The two biggest DX issues I had were needing to wrap instantiation of the WC in a helper so it doesn’t accidently get declared multiple times w/async routes, and personally I dislike tagged templates/classes for components; I find them cumbersome to work with. 1/2

Thinking about it, I think my tl;dr here is I still haven’t found something for client side rendering I like better than Svelte.

Had a cause to play with lit-element recently. Got stuff working, but DX was a real drag. Spent an hour trying to refactor to Svelte, wound up with better DX, smaller output, easier to maintain code.

RT @elvin_not_11: I’m sorry why is WAP trendy again I thought we were done with it ten years ago

RT @davenewworld_2: First I laughed, then I cried

RT @googledevs: All the latest news, product updates, insights, and success stories from Chrome OS are now in one place — and available off…

RT @jaffathecake: Phases of coding:

1️⃣ My code looks like something from a “beginners’ JavaScript” book, because that’s all I know. 2️⃣ I…

RT @davatron5000: Welp. If a portal to hell opens up, it’s @tigt_'s fault.

But if the sacred timeline is restored, that was me. I did that…