- #99
- #98
- #97
- #96
- #95
- #94
- #93
- #92
- #91
- #90
- #89
- #88
- #87
- #86
- #85
- #84
- #83
- #82
- #81
- #80
- #79
- #78
- #77
- #76
- #75
- #74
- #73
- #72
- #71
- #70
- #69
- #68
- #67
- #66
- #65
- #64
- #63
- #62
Future of the Web - Native Web Components
I have known for a long time that browsers began to introduce Web Components APIs and standards, but I never had the opportunity to use this technology in practice. Over time, I found that the application scope of Web Components is becoming broader, and I can also see that major framework packages are successively supporting the use of Web Components, which catched my interest. Simply put, in the face of the current complex frontend demands such as:
- Declarative and concise efficient template systems
- Responsive state and corresponding cross-component communication
- Server-side rendering of Web Components is still impossible 😅, and it will not replace existing solutions, but we can expect more implementations of web components to align with the browser’s native APIs.
I researched a bit and wrote an article: Future of the Web - Native Web Components
- #61
- #60
- #59
- #58
- #57
- #56
- #55
- #54
- #53
- #52
- #51
- #50
- #49
- #48
- #47
- #46
- #45
- #44
- #43
- #42
- #41
- #40
- #39
- #38
- #37
- #36
- #35
- #34
- #33
- #32
- #31
- #30
- #29
- #28
- #27
- #26
- #25
- #24
- #23
- #22
- #21
- #20
- #19
- #18
- #17
- #16
- #15
- #14
- #13
- #12
- #11
- #10
- #9
- #8
- #7
- #6
- #5
- #4
- #3
- #2
- #1