Webcomponents-blog-examples Alternatives
Similar projects and alternatives to webcomponents-blog-examples
-
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
Filestash
🦄 A modern web client for SFTP, S3, FTP, WebDAV, Git, Minio, LDAP, CalDAV, CardDAV, Mysql, Backblaze, ...
-
htm
Hyperscript Tagged Markup: JSX alternative using standard tagged templates, with compiler support.
-
-
select2
Select2 is a jQuery based replacement for select boxes. It supports searching, remote data sets, and infinite scrolling of results.
-
marimo
A reactive notebook for Python — run reproducible experiments, execute as a script, deploy as an app, and version with git.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
cami.js
Cami.js is a simple yet powerful toolkit for interactive islands in web applications. No build step required.
-
-
webcomponents-blog-examples reviews and mentions
-
HTML Web Components
> This feature of web components encourages a design of composability.
I am not a React, Vue (and friends dev) at all. Heck, I haven't done front-end or full stack for a long time now.
However, taking React as an example, where does it not encourage composability?
I like Web Components. I even spent the last couple of weeks playing only with the vanilla APIs (no Lit, etc.) just to see what is like:
https://lpedrosa.github.io/blog/web-components-part-3/
https://github.com/lpedrosa/webcomponents-blog-examples
Like many other people have pointed out in this post, it is great that you can leverage the platform. All the things you will learn e.g. DOM APIs, native elements and events, etc., are things you can carry over to React and Vue.
However, I believe articles like this fail to acknowledge the contribution React and friends brought to developer experience.
Building complex desktop like UIs was no longer impossible to maintain. You can easily make components and compose them, customise them, etc.
The general complaint is more around "you don't need Next.js" to build a news/marketing/blog website. The pendulum is swinging, especially with things like HTMX gaining traction.
IMO, people do it because:
- It's easier to hire developers that know the framework du jour
- Custom Elements are very flexible, so it's hard to enforce a particular style
- There aren't enough examples of people using vanilla Web Components (and I mean vanilla, not Lit and friends), so why use a web component framework when I can use a react based one?
Write more about how we can combine things like Custom Elements and "traditional" server side templating.
Write more about how a native element reacts to changes to its attributes or how it communicates user interaction and how that helps building a good custom element.
Or how building a good custom element is similar to building a good React component, and where it differs.
Antagonising existing knowledge or even the status quo, is not constructive and leads to poor discussions e.g. Web Components is a failed technology or articles like OP
Stats
lpedrosa/webcomponents-blog-examples is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of webcomponents-blog-examples is JavaScript.
Popular Comparisons
Sponsored