Community-protocols Alternatives

community-protocols reviews and mentions

• What We Need Instead of "Web Components"
  8 projects | news.ycombinator.com | 22 Dec 2023

  > except that "reactivity" does not meet the bar of developers collectively having landed on a solution to a common problem

  Now that everyone seems to be in love with signals, there is work going on in the web components community group to prepare a spec for a signal (or observable, not sure what they are trying to call it) primitive [0]. It seems that they are getting ready to bring it to TC39 as a proposal.

  (In the meantime, the Observable primitive from rxjs been given a go-ahead for browser implementation. There is a proposal ready [1], and I think I heard that it may already be in Chrome behind a flag [2].

  So yeah; it's gonna be fun. Especially if both groups call their primitive Observable :-)

  0 - https://github.com/webcomponents-cg/community-protocols/issu...

  1 - https://github.com/WICG/observable

  2 - https://nitter.net/BenLesh/status/1737174784406933599

• Show HN: Hyphen – custom element base class for good ergonomics
  2 projects | news.ycombinator.com | 5 Nov 2023

  The custom element spec definitely only deals with the mechanics of when are where to run your component's lifecycle code - it says nothing about data. So your choices are basically property accessors, which are interoperable, but require prop-drilling for global-ish data, or something proprietary like a state management library.

  The Web Components Community Group (WCCG) is offering something of a third way with the community protocols: https://github.com/webcomponents-cg/community-protocols

  The Context protocol provides tree-scoped ambient data in an interoperable way. It's implemented by Lit and FAST (I believe). It doesn't replace a data store, but it's often used to provide data stores to components, and at least reduce some coupling.

• Events are the shit
  2 projects | dev.to | 26 Jul 2023

  Did you know events can also carry promises? A great showcase of this pattern is the Pending Task Protocol by the Web Components Community Group. Now, "Pending Task Protocol" sounds very fancy, but really, it's just an event that carries a promise.

• Nx Console gets Lit
  7 projects | dev.to | 30 Jun 2023

  If you’re coming from the Angular world, you probably appreciate the great dependency injection (DI) mechanism they have. You can centrally define some services and reuse them across your app, without thinking about passing on props from component to component - the DI system takes care of it. Lit provides something similar via the [@lit-labs/context](https://lit.dev/docs/data/context/) package. It’s based on the Context Community Protocol and similar to React’s context API.

• Back to the Front-end: Exploring the Future of the Umbraco UI (Part 9 - Context API)
  2 projects | dev.to | 21 Oct 2022

  Fundamentally it is an event based mechanism to access state or "context" from ancestores of a component node. Based on the Web Components Context Protocol RFC which in turn is inspired by React's Context Api, the key purpose is to solve the problem of prop drilling.

• 🕎 8 Days of Web Components Tips
  1 project | dev.to | 5 Dec 2021
• JavaScript vs JavaScript: Round 2. Fight!
  1 project | /r/javascript | 17 Sep 2021

  The conversation led to the creation of https://github.com/webcomponents-cg/community-protocols. So there is some effort to standardize at least on convention for these higher-order considerations, but working through this and how opinionated it is made me recognize even more that this has a lot of similarities to a different group building a different framework. Tricky balance.

• We Use Web Components at GitHub
  11 projects | news.ycombinator.com | 4 May 2021

  I’m pretty actively following a lot of the web components community so I thought I would jump in here with some hopefully helpful information. Depending on what you mean by SEO it’s worth noting that for a while now Google and I believe Bing and a few others haven’t had any kind of requirement to pre-render content. You can just serve standard web components or any kind of SPA style front end and it will get indexed just fine, no penalties and no real issues unless you’re doing something particularly strange.

  However, one of the more exciting projects in the web components space (lit.dev) now also supports proper SSR as well which is a very new thing in the world of web components. They are trying to build it in such a way that any other library can take advantage of through a common interface.

  In fact there are some kind of early stage talks happening over here https://github.com/webcomponents/community-protocols where a bunch of companies like Google, Adobe, ING and others are trying to develop some open protocols on a whole bunch of topics to improve interoperability between various libraries so that no one has to buy in 100% to any one setup.

• A note from our sponsor - WorkOS
  workos.com | 28 Apr 2024

  The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →