rictic

Web true believer. Web Components are great.

working @ google

[rictic @rictic]

@qntm Calder did an incredible job, it added a lot to my experience.

[rictic @rictic]

@lastmjs Eyeballing this at the halfway point, I think most don't hold up.

[5] is the only clear yes to me. [7] is making very solid progress, and in many circles is true. [1] is doing decently well by % pageview. I'm not in a position to evaluate the smart contract details.

[rictic @rictic]

@sakesun @justinfagnani If a framework component is rewritten to a new framework, you gotta update anywhere that uses it. If a web component is rewritten to use a new library, users don't even notice.

[rictic @rictic]

@sakesun @justinfagnani Difference is in interoperability. If you want to render a React component, you gotta import React. If you want to render a Lit component, you can just document.createElement.

[rictic @rictic]

@littledan My concern is a world where there's less of a JS ecosystem and more a swarm of ecosystems which can't share code between one another.

[rictic @rictic]

@littledan This is something that tool makers have not, historically, been great about handling. It's unfortunately common for tools to do proprietary things with standard syntax. If we move more of the language to tooling, won't libraries even more tightly couple to their toolchain?

[rictic @rictic]

@VictorTaelin For fuzzing, it's probably the case that libraries that do random generation and simplification are better, but intuitively it's such a rich space to explore that I'm persisting, hoping to stumble upon other neat applications.

[rictic @rictic]

@VictorTaelin I've mostly used it to find compiler bugs. I've got a working implementation of FEAT in JS that I intend to hook up into my language enumeration library, but I've been putting it off because I want to dive into the fairness improvements in the other paper: https://t.co/KQpySPFaGT

[rictic @rictic]

@VictorTaelin Really cool application of enumeration btw!

Enumeration's potential has itched my brain since reading GEB. The fact that you can just generate all proofs given a set of axioms, or all sentences given a grammar, or all programs given a syntax is tantalizing!

[Mesop @mesop_dev]

https://t.co/J7pKGNnjpi now has experimental support for Web Components! 🎉 Build custom components in JavaScript for greater flexibility and control 💪

Learn more: https://t.co/bM0e0DJe7s

Thanks @justinfagnani @rictic for helping us with our design (and building Lit)!

#Mesop #WebComponents #OpenSource

[rictic @rictic]

@DasSurma Nice! Tree maps are also really good for this kind of visualization, where there's strict containment without repetition.

[rictic @rictic]

@RogersKonnor @43081j Thanks!

IMO, whether we have trailing /> for void elements in source is a matter of taste, HTML5 parsers ignore it so its semantics are fine.

Critical thing is ensuring that non-void elements aren't written with />. IMO prettier should rewrite them to add a closing tag in HTML

[rictic @rictic]

@dettofernet @cubosh This is so cool. Easy to play with it and get different effects. Thanks for sharing this!

[rictic @rictic]

@43081j Nice, I'll have to take a look at that. For a number of those things there's non-debug APIs, but they're often clunky and not guaranteed. e.g. to get enum name you can grab it off the enum object. It's clunky, but it works:

console.log(ts.SyntaxKind[node.kind])

[rictic @rictic]

@justinfagnani @mraleph @PaulHMason @dart_lang Expanding on that, the two key features that make this powerful:

- the TemplateStringsArray object is unique per template literal, allowing efficient caching
- the TemplateStringsArray object is guaranteed to contain only developer authored content, same level of trust as source

[rictic @rictic]

@justinfagnani That's awful. Do you have your own modem? I've seen improvement from a better cable modem, though starting from 20Mbps is… not a good sign