Pauan
Pauan
Here are some relevant (very old) discussions from Elm that I found: https://groups.google.com/d/msg/elm-discuss/w2Rmim4IUn4/pVOZlvZGTqoJ https://groups.google.com/d/msg/elm-discuss/w2Rmim4IUn4/IydCXb1tDc4J https://groups.google.com/d/msg/elm-discuss/w2Rmim4IUn4/EgWWQ2XR1SQJ https://groups.google.com/d/msg/elm-discuss/Okh03gltc2c/zAUHcdCWCwAJ https://groups.google.com/d/msg/elm-discuss/xq6iKNACsxw/Sq_UMcJ6xpcJ Keep in mind the above posts are generally discussing the *old* Signal system,...
> @OddCoincidence Since Stream is a trait in rust, couldn't these performance concerns / behavioral differences be handled by a particular Stream implementation? Unfortunately, they cannot. The actual methods are...
> @fitzgen In the meantime, either the futures-signals crate temporarily ports to the old, stable futures, or we delay movement here until the new futures are stable. I'm *really* not...
@fitzgen It's not feasible to use `connectedCallback` and `disconnectedCallback` to manage Rust lifetimes, because they aren't actually tied to the lifecycle of the DOM node, and both callbacks can be...
> @fitzgen I still think a delayed (and cancellable!) destruction is what we want here, because of the superior UX. Custom elements are supposed to "just" be another element, and...
Also, as for encapsulation, custom elements can actually have custom methods, which the consumer can then access: ```js class Foo extends HTMLElement { myMethod() { ... } } customElements.define("my-foo", Foo);...
@fitzgen Ah, okay, I had (incorrectly) assumed there would be a 1:1 relationship between the Rust struct and the custom element. If you instead make it N:1 then yeah, it...
As for attributes, (at least in HTML) those are primarily used for static pre-initialized things. For dynamic things, users instead use setters/methods like `foo.min = 5`. The same goes for...
@olanod That still requires JS glue to create the function object (and change the prototype). Secondly, as far as I know, [it's not possible to use ES5 classes for custom...
@aturon I agree. There are npm packages that work on Node only, there are npm packages that work in the browser only, and there are npm packages that work on...